Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on March 10, 2024, 08:21:18 pm
-
https://www.aaroads.com/forum/index.php?topic=24933.msg2912853#msg2912853
Well it is in the 2022 HLR so I presume we have enough to put it in Travel Mapping as much as I do not want us to.
https://roads.maryland.gov/OPPEN/2022%20Garrett.pdf (see page 16)
-
another reason to have unsigned routes in TM, especially if they appear on maps. People who want to clinch them all regardless of posting status get jerked around when they suddenly become posted...
-
My main incentive to head all the way to Oakland just to clinch MD 219 would be to check signage along MD 36 for MD 935.
In other potentially posted MD Route news, I have already clinched MD 114 (Watkins Mill Rd, goes from MD 117 to MD 355 crossing I-270 at Exit 12) so if/when that becomes signed I am good there.
-
another reason to have unsigned routes in TM, especially if they appear on maps. People who want to clinch them all regardless of posting status get jerked around when they suddenly become posted...
The hard thing with unsigned routes is that you eventually get into stuff like the NY reference routes. I could see a case for "if the system is otherwise signed and the route is clearly part of said system", but then you get into things like Maryland's habit of assigning route numbers to random pieces of concrete on old alignments.
-
There should be some discretion on the part of the maintainer. Maryland chooses to number some of its abandoned alignments and frontages with the same numbering system as its normal state highways. Virginia does this with frontages and stubs designed to preserve property access that was taken away by a primary route's reconstruction. Virginia considers these routes primary routes and posts 3/4 of them, but they have a separate numbering convention (F-routes) from their state route numbering. So Virginia's F-routes can be easily ignored in TM until someone were to decide the whole system should be included.
But Maryland definitely has unposted routes that are real roads, often of independent utility, sometimes on maps, and are subject to posting at any time, like the recent MD 219 and MD 368/MD 568 which went decades without posting then suddenly were fully posted one day.
And of course we should be including state routes that are posted but somehow deemed insufficiently posted (NJ and VA definitely have these).
-
Maryland has way too many examples of "oh this half a block of a dead end street is MD 782F" (I made that number up, specifics are beside the point) for any sane person to attempt to clinch all the unsigned stuff. This came up in prior discussion about future inclusion of at least some unsigned routes.
Anyway, adding MD 219 since it's signed. Anyone else ever submitted an update from 36,000 feet in the air? Because I'm taking advantage of the wifi on my flight home from my grand European road trip to do that (among other things, including spending over 2 hours updating my own list file). :P
And if anyone is curious yes, logging into Noreaster and running datacheck does work from up here, with the most noticeable difference being a lot more lag than normal before it prompts for password. Datacheck itself runs as fast as on the ground.
https://github.com/TravelMapping/HighwayData/pull/7273
-
MD 219 is written as MD 218 in the updates entry. Anyway, I am glad I went to clinch this today.
Thankfully MD 935 is back is being signed the way it was before the detour.
-
Check the updates entry again. It's not appearing on the updates page.
-
Check the updates entry again. It's not appearing on the updates page.
Because the line was listed as '2023' instead of '2024'.
-
Check the updates entry again. It's not appearing on the updates page.
https://github.com/TravelMapping/HighwayData/pull/7278