NM NM1113 missing?

[tckma]

Is usanm missing NM NM1113?

https://en.wikipedia.org/wiki/New_Mexico_State_Road_1113

[oscar]

It's in the Highway Browser.

https://travelmapping.net/hb/showroute.php?units=miles&u=oscar&r=nm.nm1113

There's also a waypoint for NM 1113 on NM 9, about 0.1 mile west of the NM 113 waypoint (so you have to zoom in a bit in the HB to see the two separate waypoints).

How did you try to look it up? Might be a bug in our recently developed "findroute" or "showroute" functions, thought both worked for me to track down and show NM 1113.

[tckma]

Just from the table of NM state routes.  Scrolled all the way to the end and noticed NM NM6563, thought “that’s an oddly high number.”  Looked it up on Wikipedia and saw NM NM5001 and NM NM1113 as other four digit state routes.  The table has NM NM653 (or something) and the next (last) one is NM NM6563.

[si404]

NM1113 is in the table between NM111 and NM112.

[oscar]

NM1113 is in the table between NM111 and NM112.

Specifically, the table at https://travelmapping.net/hb/index.php?units=miles&u=oscar&sys=usanm&rg=null

The newer Findroute table has NM1113 in the correct order, between NM615 and NM6563:

https://travelmapping.net/hb/findroute.php?units=miles&u=oscar&

However, Findroute is much slower, since it first loads all 62,000+ routes in the TM database, before it will let you narrow your search such as by system or region.

As for other four-digit state routes in NM, the former NM 2001 is both decommissioned and unsigned. I checked it out just for fun, the last time I was in Alamogordo.

Also, NM 5001 is unsigned, having been absorbed into US 64 (the former US 64 routing through downtown Farmington is now US 64 Business).

That business route was harder for me to look up in Findroute, since the dropdown menu to search by region is not in alphabetical order, even within the regions in the United States.

[yakra]

Worth padding usanm to four digits, as done with usaky, usala, usatxl, usatxs, and maybe more?
Or alternately, how about fixing hb/index.php to keep routes in CSV order?

[oscar]

Worth padding usanm to four digits, as done with usaky, usala, usatxl, usatxs, and maybe more?
Or alternately, how about fixing hb/index.php to keep routes in CSV order?

Zero-padding usanm is not worth the hassle, for its two four-digit routes. We didn't zero-pad usahi, which also has a few four-digit routes along with two- and three-digit routes (the way Hawaii clusters its routes, all the route numbers with the same first digit are on the same island, so CSV order is less important).

Putting hb/index.php in CSV order would be better. Or maybe fixing Findroute to let users filter by region, system, etc. before it loads every route in the TM database, which creates delays that for me makes Findroute unusable. That fix might also allow us to decommission hb/index.php.

[rickmastfan67]

Worth padding usanm to four digits, as done with usaky, usala, usatxl, usatxs, and maybe more?
Or alternately, how about fixing hb/index.php to keep routes in CSV order?

Zero-padding usanm is not worth the hassle, for its two four-digit routes. We didn't zero-pad usahi, which also has a few four-digit routes along with two- and three-digit routes (the way Hawaii clusters its routes, all the route numbers with the same first digit are on the same island, so CSV order is less important).

We didn't pad usafl either, even though it had FL-9336.

[yakra]

FWIW, some shell scripting can reduce the hassle of the conversion process to near zero.
More hassle might be invalidating whatever HB links are kicking around the forum.