NM: NM28Can point order

[yakra]

I checked GMSV, and didn't see any signage on TX NM28 or NM NM28Can, ergo no change in signed direction of the route.
I won't make any comments on whether to keep or toss the southernmost chopped sections, but NM28Can should probably have its point order flipped to match the rest, if we keep it.
Point labels would not need to change.
While we're at it, the TX/NM point at the overall southern terminus looks off. TXDOT shapefiles have it here, but I'd be OK with also using OSM data.

[oscar]

I checked GMSV, and didn't see any signage on TX NM28 or NM NM28Can, ergo no change in signed direction of the route.

I saw one NM 28 sign on NM28Can, at the NM 273 junction. No direction banner, though.

I won't make any comments on whether to keep or toss the southernmost chopped sections, but NM28Can should probably have its point order flipped to match the rest, if we keep it.
Point labels would not need to change.
While we're at it, the TX/NM point at the overall southern terminus looks off. TXDOT shapefiles have it here, but I'd be OK with also using OSM data.

I agree with flipping the waypoint order. I would also keep the southernmost chopped sections, since one is signed, and the other (TX NM28) is so short you wouldn't expect a route sign there (the state line isn't marked at the ends, either).

Your suggested southern endpoint for NM NM28Can, from the TXDOT shapefiles, is a better match to the low-precision coordinates I can pluck from NMDOT's Functional Classification map (lat=31.917&lon=-106.620) than the coordinates we have in the HB or can get from OSM. So I'll go with the TXDOT shapefile coordinates, and you can synch your draft TX FM259 route file to those coordinates as well.

Update: https://github.com/TravelMapping/HighwayData/pull/3951

[michih]

The route was traveled by barefoot_driver and rlee.

Code: [Select]

nm nm28can nm273 nm/tx
NM NM28can NM/TX TX/NM
barefoot_driver's stats will be effected. I think we need a update notification if we implement this!

[oscar]

The route was traveled by barefoot_driver and rlee.

Code: [Select]

nm nm28can nm273 nm/tx
NM NM28can NM/TX TX/NM
barefoot_driver's stats will be effected. I think we need a update notification if we implement this!

I think not. No labels were changed, just their order in the route file, which now runs south-north rather than the previous north-south.

[michih]

barefoot_driver has traveled the segment north of NM273: http://travelmapping.net/hb/index.php?u=barefoot_driver&r=nm.nm028can
After your change, barefoot_driver will have traveled the segment east of NM273.

[neroute2]

The text of the labels NM/TX and TX/NM is swapped, along with their positions in the file.

[yakra]

The point labeled NM/TX was and remains at http://www.openstreetmap.org/?lat=31.924047&lon=-106.627572.
The point labeled TX/NM was and remains at FM259. The change is fine. Merged.

[michih]

Sorry for the confusion. My bad

[yakra]

barefoot_driver's stats also threw me off at first, until I noticed the waypoint labels wouldn't need to change.