# Mapping problem - a potential solution - a journal

**URL:** <https://discourse.flucoma.org/t/mapping-problem-a-potential-solution-a-journal/932>\
**Category:** New Ideas\
**Created:** [July 16, 2021, 10:45am UTC](https://discourse.flucoma.org/t/mapping-problem-a-potential-solution-a-journal/932 "2021-07-16T10:45:01Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)\
**Post date:** [July 16, 2021, 8:08pm UTC](https://discourse.flucoma.org/t/mapping-problem-a-potential-solution-a-journal/932/4 "2021-07-16T20:08:34Z")

</div>

In @tremblap’s original example, it was using something like pitch confidence to determine what the actual matching criteria for a given source/target was. So if the pitch confidence was high, you would then weigh the pitch value highly and carry on, whereas if the pitch confidence was low, you can ignore pitch altogether in your query.

Given the overall fluid context, this requires a “fork” of each dataset with and without pitch (and/or other variations/massagings). This works well for this kind of binary forking, but beyond that, it gets [a little bit more problematic](https://discourse.flucoma.org/t/a-fluid-datasetfilter-object-for-conditional-querying/598).

---

_[View the full topic](https://discourse.flucoma.org/t/mapping-problem-a-potential-solution-a-journal/932)._