Clinched Highway Mapping

rickmastfan67 · Joined: 14 Jul 2008 Posts: 2031 Location: Pittsburgh, PA

Should the '147' label be US30_E instead? I just looked in StreetView and there is no exit number posted for the interchange.

Meanwhile, the '148' point does have an exit number posted, but it's the true '147' point. Sure, that exit number is not posted @ the gore point, but there is at least proof of it in the field @ Exit #149. http://goo.gl/maps/LN3Wb & http://goo.gl/maps/05eRT

So, what to do here? For starters, there shouldn't be a '148' label in any way shape or form. If you want to keep the current '147' as is Tim, then the '148' should become '147A' because the I-70 147MM is posted right at that intersection. http://goo.gl/maps/USV3J

rickmastfan67 · Joined: 14 Jul 2008 Posts: 2031 Location: Pittsburgh, PA

Ok, the following changes would need to be made (based off Sept '14 StreetView).

I-70:
148 -> 147 or 147A
147 -> US30_E (or leave as is if the '147A' option above is chosen)

US-30:
I-70(148) -> I-70_E or I-70(147) or I-70(147A)
I-70(147) -> I-70_W (or left as-is if the 'I-70(147A)' option is chosen above)

The US-30 fixes above would prevent any list files from being broken (if the I-70(147) option isn't chosen), however I-70's entries would be broken because of the exit #'s being corrected (unless the '147A' option is chosen).

So, does anybody have a problem with the changes outlined above? These changes would mean breaking some people's list files unfortunately. That's something that can't be avoided after double checking the current StreetView in this area (Sept '14). Would like some opinions before I submit.

yakra · Joined: 30 Jul 2008 Posts: 2600 Location: Area Code 207

I prefer US30_E & 147 for I-70.

For US30 could go either I-70_E I-70_W or I-70(148) I-70_W.
I think the former Looks Nicer; I might wanna go with this.
The latter might be supported by a strict reading of the manual, FWIW. I can't be arsed to read it ATM.

My philosophy:
In my mind, breaking-breaking a list file happens when a line can no longer be parsed, and instead produces an error in the log.
Outside of that, I see two categories of changing labels that alter how a .list file is parsed:
• Moving a point label is acceptable, and in some cases unavoidable. It'll change someone's maps & stats a tiny bit, but the .list file still works. Write an updates entry; life goes on.
• The Greater Evil happens when a label in use at a route's terminus would be moved, thereby changing someone's 100% clinch into something less. These cases, I do put more of a priority on avoiding. That's why, for TX I-37, I fudged Exit 1A to Exit 1, and left 1A as a hidden label for the southern terminus at US181.