TonyTorrent wrote:Emmons Circle is the horseshoe with both ends connecting to Wolcott Hill Street.
Emmons Circle needs to be split into two segments. No two segments should have the same end points. It causes all sorts of routing problems, and misidentification of the actual route requested on URs, etc. It also causes issues with inability to locate the correct location when starting on that type of road.
This has been well documented in a few different forum discussions, which the Validator author provided links to earlier in this thread.
There may be some confusion between the different types of "same connections". Let me clarify:
- Loop Roads: One Segment. End-nodes A and B connect to themselves. Routing issues identified and fixes exist in many scripts. Covered in Wiki
- Routing to Same Segment: One Segment. I found a strange routing problem when you start and end navigation on the same single segment. I fully documented it in the forums under Same Segment Routing Problems.
- Parallel Segments: Two Segments. Also called Horseshoe Roads. This situation is like two resistors in parallel. The end nodes A of both segments connect together and the end nodes B of both segments connect together. A real example is here. I also posed this question in the forum under "Same Connections" cause routing issues?
34. Same endpoints drivable segmentsWhat is the problem?
Two drivable segments share the same two endpoints: forum referenceHow to fix?
Split the segment. You might also remove one of the segments if they are identical: instructionsSeverity: warning
Countries: any country
This entry is referring to the Parallel Segments/Horseshoe Rd example. The forum reference for 34 actually links to my forum entry that was asking anyone to actually confirm there are problems with this configuration in routing, but there was nothing conclusive. I did point out the other problem with routing to the same segment in that thread, so maybe people got confused what was actually a problem. There were comments this was a known issue with Cartouche, but not necessarily the current WME.
Today I sent a message to the Waze team on that specific issue. I will report back what they say relative to this issue. If anyone has any current routing issues they know about or can find any forum threads showing this is still a problem then let us know and we can add it to the Wiki best practices.
If there are no routing issues that we can still find today I realize this particular warning will help identify segments that lay on top of each other, but these Horseshoe roads are so widespread in suburban neighborhoods I think it will invite unnecessary editing to add a junction. Also if we do leave this in we need to be sure the "remove unnecessary junction nodes" option does suggest removing them. LOL