11
Updates to Highway Data / CO CO121 point request
« Last post by neroute2 on Yesterday at 03:03:29 am »Can I please have a point at 88th Avenue (between 72ndAve and 92ndAve)? Thanks.
If you have any trouble registering for the forum, please email travmap@teresco.org for help. Email systems often block activation emails sent by the forum.
167 -> split into 167/167A. This will allow NM-556 to have a proper location for this interchange. Update the point in NM-556 too.
Rather than splitting the point, into two points only 0.2 mile apart, I would just move I-40(167) to the NM 556 underpass, and rely on 1PPI to have the relocated point cover the entire interchange. This also leaves NM 333 and NM US66HisAlb (per your note on NM 333) unchanged.
https://github.com/TravelMapping/HighwayData/pull/8649
https://github.com/TravelMapping/HighwayData/pull/8650
Other changes to I-40 later, to avoid confusion from my trying to follow two baseball playoff games at once.
I can sorta live with a 1PPI here on I-40, but I still think these still work as separate interchanges. With the one that connects to NM-556, you have 2 directions (originally was only an EB off-ramp, but WB on-ramp added in 1982), but with NM-333 there, you have 3 of the 4 movements.
Ok, so I'll just drop the FL-54Zep file for now till we hear about FL-581's signs coming down. We'll do a separate topic on that when it happens.
Also changed the 'FL54' point in US-301's file to 5thAve instead since there was already another CR54 label for the other Pasco 'CR54' route. Best idea I could come up with at this time.
https://github.com/TravelMapping/HighwayData/pull/8639
Honestly, with FL54Zep going away, I would prefer that the rest of FL 54 become FL 56, but that is in fictional territory.
Haven't we had this conversation before?
https://maps.app.goo.gl/VDaLwFkyVSP2driM8
That one belongs in usaohh, not usaush. Or is it usaoho?