Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: noelbotevera on July 14, 2016, 02:18:42 pm
-
The whole secondary system is missing and a couple VA primary numbers are missing. Not sure if these are planned to be added.
-
While we're on it, Antarctica Route 1 (https://en.wikipedia.org/wiki/South_Pole_Traverse) is missing.
(https://upload.wikimedia.org/wikipedia/commons/thumb/0/0a/Antarctica_Route_1.jpg/800px-Antarctica_Route_1.jpg)
-
I do not think you have any clue how many routes would have to be included for the whole secondary system. (many of which are subdivision roads)
(Besides I remember SR 7100 being in the select-numbered state freeway system, wait that is being replaced by VA 286 in usava and in real life.)
-
The whole secondary system is missing and a couple VA primary numbers are missing. Not sure if these are planned to be added.
It's common for state/provincial route sets to start off with primary routes only, if they're signed differently from secondary routes, then maybe later add the secondary routes. As Markkos1992 suggests, we may never add Virginia secondary routes because there are too frigging many of them.
Mapmikey can better explain omissions of primary routes, but we normally exclude unsigned routes or unsigned discontinuous route segments. Also, which ones are missing?
-
The whole secondary system is missing and a couple VA primary numbers are missing. Not sure if these are planned to be added.
...
Mapmikey can better explain omissions of primary routes, but we normally exclude unsigned routes or unsigned discontinuous route segments.
My guess is you're referring to the routes that are in the select numbered freeways system (already active) that will be folded into the Virginia State Highways when they become active.
I agree with oscar that the VA secondary system is likely too large and includes far too many inconsequential routes to be included. I find it amazing that we have managed to get all of Kentucky's oversized system.
-
I can speak a bit to this. Virginia primary routes were omitted if they were not signed. We keep fairly extensive background information on this on VHP (http://www.vahighways.com), and when Mike took over creating the Virginia routes, he was adhering to the earlier CHM policy of leaving unsigned state routes out of the log files.
-
Well, I'm not meaning the WHOLE system, just highways that might be useful for the public/roadgeeks, such as SR 729.
-
Well, I'm not meaning the WHOLE system, just highways that might be useful for the public/roadgeeks, such as SR 729.
You do know that there are more than just 1 'SR 729' in VA, right?
-
just back on the grid after 2 days at my mother's house near Gretna...
The state routes that are not included at this time are by the CHM rules: not posted with an actual route shield. This would include regular routes VA 113, VA 192, VA 213, VA 283 and some VA 4xx routes, plus some of the 3xx facility routes. It also leaves out routes that are posted solely with rectangles, but I am inclined to add these at some point.
It in theory could be worthwhile to add the secondary routes that were once primary route corridors (excluding loops of bypassed segments I would be thinking of SR 729 north of Culpeper, SR 711 (old VA 44), the lengthy SR 738 (old VA 51), routes like those that were decommissioned wholesale).
Technically F-series routes are in the primary system but most of these are not worth inclusion as most don't connect to anything else.
There are likely over 100,000 designated and posted secondary routes in Virginia so, yeah, that ain't happening.
-
Well, I'm not meaning the WHOLE system, just highways that might be useful for the public/roadgeeks, such as SR 729.
You do know that there are more than just 1 'SR 729' in VA, right?
I'll be honest, no. I only know the one north of Culpeper. It kind of surprises me that there's route duplication between secondaries.
-
Well, I'm not meaning the WHOLE system, just highways that might be useful for the public/roadgeeks, such as SR 729.
You do know that there are more than just 1 'SR 729' in VA, right?
I'll be honest, no. I only know the one north of Culpeper. It kind of surprises me that there's route duplication between secondaries.
There is tons of duplicate numbers in the secondary system in VA. Each county could, and possibly might have a SR 600 in them. So, you see why those routes will never make it to this site. You could even consider VA's secondary system more like County Routes in the way there can be duplicate numbers.
-
Well, I'm not meaning the WHOLE system, just highways that might be useful for the public/roadgeeks, such as SR 729.
You do know that there are more than just 1 'SR 729' in VA, right?
I'll be honest, no. I only know the one north of Culpeper. It kind of surprises me that there's route duplication between secondaries.
There is tons of duplicate numbers in the secondary system in VA. Each county could, and possibly might have a SR 600 in them. So, you see why those routes will never make it to this site. You could even consider VA's secondary system more like County Routes in the way there can be duplicate numbers.
So for example, if one day we decided to add in SR 620(Braddock Road) east of US 29, it would have to be referenced as SR 620(Fairfax County) as there may be 92 other SR 620s. (VA has 92 counties with SRs, the independent cities along with Henrico and Arlington counties (plus some towns) do not have them as they maintain their own roads.)
-
Well, I'm not meaning the WHOLE system, just highways that might be useful for the public/roadgeeks, such as SR 729.
You do know that there are more than just 1 'SR 729' in VA, right?
I'll be honest, no. I only know the one north of Culpeper. It kind of surprises me that there's route duplication between secondaries.
There is tons of duplicate numbers in the secondary system in VA. Each county could, and possibly might have a SR 600 in them. So, you see why those routes will never make it to this site. You could even consider VA's secondary system more like County Routes in the way there can be duplicate numbers.
Hmm, I understand.
--------------------------------------------------------------------------------------------------------------------------------------------------
But I'm not sure how to fill the gap between secondary routes. My last trip involved traveling SR 729 north of Culpeper, but I don't know how I would write that in my .list file.
-
But I'm not sure how to fill the gap between secondary routes. My last trip involved traveling SR 729 north of Culpeper, but I don't know how I would write that in my .list file.
If you travel roads that are not part of the TM data, you simply don't include entries for them.
-
Also, you're welcome to put anything you want in your list file if you wanted to track some roads we don't have. They'll generate error messages in your log file, but cause no harm otherwise. I try to put in entries for any roads I travel that I think are likely to be added to the system some day, so I don't have to try to remember where I traveled if and when those routes are added.
-
Also, you're welcome to put anything you want in your list file if you wanted to track some roads we don't have. They'll generate error messages in your log file, but cause no harm otherwise. I try to put in entries for any roads I travel that I think are likely to be added to the system some day, so I don't have to try to remember where I traveled if and when those routes are added.
I do the same but don't like any error. I comment these routes:
https://github.com/TravelMapping/UserData/blob/master/list_files/michih.list
AUT E552 DEU/AUT 65(A8)
AUT E651 B99_N B99_S
#AUT B1 A1(9) B221
#AUT B20 B116 S6
Line 1+2 are from an active system, line 3+4 are from a potential future system.
-
But I'm not sure how to fill the gap between secondary routes. My last trip involved traveling SR 729 north of Culpeper, but I don't know how I would write that in my .list file.
Without even a draft route file to look up for that segment of SR 729, you'd be guessing not only the waypoint names, but also how the route would be file-named to distinguish it from any other SR 729s in Virginia. You might do better to log your non-TM-mappable travels in a separate file from your list file, so you can use whatever format you prefer.
I have such a separate file with draft list file entries and other notes for routes that I expect one day to show up in TM. (But I don't even track Virginia SRs, or county or other local routes in other states.) When it's time to move draft entries into my list file as new systems are added, I often find that I've guessed wrong on how the route or its waypoints will be named or which points are included in the route file, so I need to redo entries anyway.
-
I can speak a bit to this. Virginia primary routes were omitted if they were not signed. We keep fairly extensive background information on this on VHP (http://www.vahighways.com), and when Mike took over creating the Virginia routes, he was adhering to the earlier CHM policy of leaving unsigned state routes out of the log files.
I noticed the other day that VA 37 was missing from this site. Isn't that signed? I was just on it a couple months ago on my way to the Corridor H road meet.
-
Freeway segments of Virginia state routes are in a different subset (select freeways) and will be reconciled with the Virginia state route set when it moves from preview to active...
-
Freeway segments of Virginia state routes are in a different subset (select freeways) and will be reconciled with the Virginia state route set when it moves from preview to active...
Ah okay. I found VA 37 in that subset of select freeways. Thanks!
-
So, can I assume we can mark this as 'solved'?
-
Let Mike do that once he's back from Norway.
-
This is solved as far as I can see. There is no action required based on the entries inthis thread.
Moving to the solved thread...