I may have missed synonyms, but afaik I coined the term "consequential mapping" in the past few years.

Basically, this attempts to describe a situation where features are getting tags and information not because of themselves, but because of something other than themselves. For example, if the right side road is a bus terminus, then creating "cannot turn right except buses" is consequential because the correct information is "the right side road is bus-only". Normal cars may not turn right is a *consequence* of the bus terminus restrictions, hence the name "consequential mapping".

imo, information about a feature should depend on its own nature, and not simply because some other feature exists. Data consumers should look at the data and then deduce by themselves that normal cars cannot turn to the right side because there is a bus terminus. We should not explicitly describe these unless the problem is armchair-undecidable (e.g. turn restrictions, these has to be irl-checked, at least with reference to aerial imagery + reasonable case-by-case deduction).

Upon review, I notice this case is logically equivalent to the "extend motorway" rule, which I personally dislike. This section of Route 2 is getting toll information because it is a consequence that normally this section is only reachable from EHC, and EHC has a toll.

-----------

In this case, because we are talking about EHC toll, I think the toll scope should match the tunnel area scope. Because this section is already outside of the tunnel area, it should not get any toll information at all, and we should treat it as just some normal untolled road.

This goes beyond the initial "two toll sections" concern.