User Discussions > How To?

A route follows a one-way pair, each half of which also has its own number

(1/2) > >>

neroute2:
http://travelmapping.net/hb/?r=mexnl.mex040
Zoom into Monterrey and note the long section with no points. Here 40 eastbound follows the south side of the river and 40 westbound follows the north side. Usually I'd just put a point in the middle of the river for each junction. The problem is that Monterrey has its own system of numbered routes, which I've drafted (but not yet pushed to devel status yet). Eastbound Federal 40 is also Monterrey 20, and westbound Federal 40 is also Monterrey 22. There's no way to have one line for Federal 40 and separate lines for Monterrey 20 and 22 while making them overlap.

Are there any existing cases that are anything like this?

michih:
I've not checked our rules on that but I'd draft MEX40 concurrent to M20 eastbound (because that's the waypoint order of MEX40) and draft a MEX40 (Monterrey) route concurrent to M22 westbound.

Jim:
Forgetting for the moment the restrictions of our current TM implementation related to concurrency detection...

- A traveler who lists 20 should also get credit through concurrency detection for overlapping 40.
- A traveler who lists 22 should also get credit through concurrency detection for overlapping 40.
- A traveler who lists 40 should not get credit through concurrency detection for 20 or 22, since we can't know which one they meant.

yakra:

--- Quote from: Jim on March 19, 2020, 09:07:05 am ---- A traveler who lists 40 should not get credit through concurrency detection for 20 or 22, since we can't know which one they meant.

--- End quote ---
This traveler will at least still have the option of adding 20 or 22 manually.
I'm not gonna look at this too closely; I just woke up & kinda can't parse it. I don't envy neroute2 :P

Not sure if either of these would help, how related they really are, but:
http://travelmapping.net/hb/?r=tx.us087&lat=35.210809&lon=-101.832147&zoom=14
http://travelmapping.net/hb/?r=ma.us006&lat=41.722339&lon=-71.152568&zoom=15

Jim:
I'm thinking a wrinkle here from the data processing and stats points of view are that a traveler who lists either 20 or 22 should get credit for that segment of 40, but if they list both, should only get credit for 40 once, not twice.

There's probably not a good solution without changes to the data processing/stats/maps infrastructure.

Navigation

[0] Message Index

[#] Next page

Go to full version