usaga: Georgia State Highways

[kjslaughter]

Thanks for the work on Georgia over the holidays!  I'm checking the updates and updating my route log.  Everything looks correct to me.  I can help double check the concurrency end points after they are updated.  I know in Georgia keeping all that straight with all the US highways is a bitch.

[ntallyn]

GA 73 Byp (Statesboro) and GA 135 Truck (Hazlehurst) are both missing from the Highway Browser.

Not sure where GA73 Bypass went off to. I saw that it was done, but now it is missing. I'll take a look at both of these over the holidays (with the concurrency checks and data errors).

Turns out I messed up on my notes on this one. I could find no posted signage for GA73 Bypass. Approaching the 301/301Byp split, I found no signs on GMSV (mostly from summer 2019) from the north or the south. Nor did I see any on the bypass itself, or approaching it from US80.

I'm leaving this one out for now.

[ntallyn]

...GA 135 Truck (Hazlehurst) are both missing from the Highway Browser.

Fix made locally. Will be pushed later this week.

[ntallyn]

Thanks for the work on Georgia over the holidays!  I'm checking the updates and updating my route log.  Everything looks correct to me.  I can help double check the concurrency end points after they are updated.  I know in Georgia keeping all that straight with all the US highways is a bitch.

It's an easy time to work on the routes. I'm off all week from the regular job (holidays, not vacation), and the wife (nurse) works 4 out of the next 5. Any assistance/comments are appreciated.

Apart from the GA135Trk route mentioned below and a datacheck error on GA7, everything in the HB is updated with my most recent. After I go through the remaining datacheck errors, I'll start working on the concurrencies. First batch will be state routes only, I'll update the US routes on the second pass.

Nick

[kjslaughter]

GA 73 Byp (Statesboro) and GA 135 Truck (Hazlehurst) are both missing from the Highway Browser.

Not sure where GA73 Bypass went off to. I saw that it was done, but now it is missing. I'll take a look at both of these over the holidays (with the concurrency checks and data errors).

Turns out I messed up on my notes on this one. I could find no posted signage for GA73 Bypass. Approaching the 301/301Byp split, I found no signs on GMSV (mostly from summer 2019) from the north or the south. Nor did I see any on the bypass itself, or approaching it from US80.

I'm leaving this one out for now.

GA 73 Byp must exist as long as US 301 Byp exists as every US highway has a state overlay. :-)  Did some research and GA 73 Byp is on the current GA DOT map of Bulloch County, so I think it should be added.

http://www.dot.ga.gov/DriveSmart/MapsData/Documents/CountyMaps/Bulloch.pdf

[neroute2]

TM has a policy of not including unsigned routes, unless the system is maintained by certain people. In this specific case, I think that's silly because anyone clinching Georgia will drive it anyway as part of usaush.

[CharlotteAllisonCDTG]

Also, the Statesboro city map (http://www.dot.ga.gov/DriveSmart/MapsData/Documents/CityMaps/Statesboro_BullochCounty.pdf) shows GA 73 Byp on US 301 Byp.

On a side note, I had no idea that GA 73 Byp was no longer signed in the city.

[ntallyn]

...GA 135 Truck (Hazlehurst) are both missing from the Highway Browser.

Fix made locally. Will be pushed later this week.

Pull request submitted. Also cleared datacheck errors on GA routes.

Still need to work on concurrency checks. Any suggestions on an easy way to do those? Or just go through them one at a time?

[ntallyn]

The above has been merged and a couple more datacheck errors were fixed locally (including the newly introduced DUPLICATE LABEL on US221).

[michih]

Still need to work on concurrency checks. Any suggestions on an easy way to do those? Or just go through them one at a time?

We have some tools and logs for it: http://travelmapping.net/devel/tools.php

You might open http://courses.teresco.org/metal/hdx/
Go to option 1 on the left and enter Geo, select the US state, not the Asian country.
Press enter.
Wait, the graph is automatically loaded after about 15s (the usaga graph, it's faster with smaller graphs but takes longer with larger graphs, sometimes minutes).
Press "Done" on the left to close the AV table.
Deselect "Show Data Tables" to close the table to the right.
You see a map of Georgia with yellow dots all over Georgia now.
Deselect "Show Markers".
You see a map of Georgia with funny colors now
Select "Show Markers" again, it was just to show you what happened
Zoom in where you wanna check concurrencies. Top left or directly to US routes or whatever.
I recommend GA1 / US27 south of Chattanooga because concurrency is actually broken here (and many times more to the south)
The funny colors are created by lines. blue line = one route, green = two concurrent routes, magenta = 3 etc.
When there is a green line (2 routes concurrent) but interrupted by a dark blue line at visible or hidden wps, it's a sign that concurrencies are broken (dark blue because two standard blue lines are overlapping).
All "non-standard-colors" like the dark blue are possible broken concurrencies.
Check GA1/GA100/US27 south of Cedartown. It should be magenta but it is a mix of green and blue due to the broken concurrency
Just east of Cedartown is a mix of magenta and blue, just 3 routes are concurrent but it should be 4
Click on the lines or markers to get info about the route name and wp labels. It's sometimes difficult to click all routes when they are mostly overlapped.

Extended expert mode (for a second run or regions with less broken concurrencies):

Load HDX as described before.
Open http://travelmapping.net/devel/tools.php in another browser TAB or window.
Select NMP files filtered by region (individual files)
Select the ga.nmp file and download it - not esp-ga.nmp
Open a 2nd instance of HDX
Go to option 3 on the left and select the downloaded ga.nmp file
You can see about 30...40 colored dots on the map now. These are near-miss-points (NMPs). Points very close together.
The points are intentionally off to brake concurrencies (yellow) which are usually marked FP (they will apear green later).
The red points must be checked. These are most likely broken concurrencies or intersecting routes where the wps do not match.
Not matching wps means, that when you are in HB, the other route does not appear as "intersecting route", you cannot directly jump to the other route in HB. This should be fixed to, if the wp is really off by accident. It's possible that the wps are apart by intent though.

Since you only see the points but not the whole network graph, you might need to go to the other HDX instance to get the whole picture. To figure out which routes should intersect, what's going on there etc. For instance, it's possible that the routes are only broken on a very short segment you don't see (or missed) with the "option 1 view style".

Graphs and NMP files are updated with every site update (twice per year the graph generation is suspended when Jim needs it for his students. He notifies the suspension on the forum).

Just ask if you are not sure about details

[ntallyn]

Still need to work on concurrency checks. Any You might open http://courses.teresco.org/metal/hdx/
Go to option 1 on the left and enter Geo, select the US state, not the Asian country.
Press enter.
Wait, the graph is automatically loaded after about 15s (the usaga graph, it's faster with smaller graphs but takes longer with larger graphs, sometimes minutes).
Press "Done" on the left to close the AV table.
Deselect "Show Data Tables" to close the table to the right.
You see a map of Georgia with yellow dots all over Georgia now.
Deselect "Show Markers".
You see a map of Georgia with funny colors now
Select "Show Markers" again, it was just to show you what happened
Zoom in where you wanna check concurrencies. Top left or directly to US routes or whatever.
I recommend GA1 / US27 south of Chattanooga because concurrency is actually broken here (and many times more to the south)
The funny colors are created by lines. blue line = one route, green = two concurrent routes, magenta = 3 etc.
When there is a green line (2 routes concurrent) but interrupted by a dark blue line at visible or hidden wps, it's a sign that concurrencies are broken (dark blue because two standard blue lines are overlapping).
All "non-standard-colors" like the dark blue are possible broken concurrencies.
Check GA1/GA100/US27 south of Cedartown. It should be magenta but it is a mix of green and blue due to the broken concurrency
Just east of Cedartown is a mix of magenta and blue, just 3 routes are concurrent but it should be 4
Click on the lines or markers to get info about the route name and wp labels. It's sometimes difficult to click all routes when they are mostly overlapped.

Excellent overview. I was going to start investigating the HDX today, but this will probably shorten the learning curve quite a bit.

Thanks, Michael!

[Jim]

Wow, that overview of how to use HDX should get its own page in the manual.  Thanks for posting.

[michih]

Wow, that overview of how to use HDX should get its own page in the manual.  Thanks for posting.

yes, I thought the same. Maybe more kind of "best practise" than manual (first). I have it on my list..... After roudj and gbnb.....

Manual: step-by-step to introduce a new highway system
Manual: Peer review procedures

Can you assign the issues to me?

[ntallyn]

Wow, that overview of how to use HDX should get its own page in the manual.  Thanks for posting.

I was thinking the same thing. Just got a chance to check it out, and the instructions make it so easy.

[yakra]

Wait, the graph is automatically loaded after about 15s (the usaga graph, it's faster with smaller graphs but takes longer with larger graphs, sometimes minutes).

My aging computer takes a bit longer to render the graphs, and then pan/zoom around, primarily due to the number of point markers that need to be drawn.
One thing that I find helps:
I first open up the District of Columbia graph, then deselect "Show Markers".
Then I open up whatever graph I'm actually interested in. It renders a lot faster without the markers being drawn at first.
I pan/zoom to the location I want to examine (which goes faster with just the polylines onscreen), and then reselect "Show Markers".

The points are intentionally off to brake concurrencies (yellow)

These look intentional, and often are, but sometimes are not. Best to still look these over too of course, and fix or mark FP as appropriate.