20 Ave (Didsbury) should have a WP to remove ambiguity. (A turn is required in order to remain on AB 582).
Not all turns on a route are worthy of a waypoint. See for example
NS NS322 NanAve OchSt via Thistle St. IMO there's not terribly much ambiguity to resolve here. If I were to add a point here, it would be because Didsbury itself is a sorta-large community that draws some traffic & travelers on its own.
Aw what the hey. I've added points for less in Massachusetts. And Nebraska. And Alberta.
My notes on the 600s:
AB604 -adjust co-ordinates of WP3 "AB2A" (Adjusted on AB2aWet too.)
AB608 - change WP0 AB36/AB53 --> "AB36/53"AB608Ami -this route is unsigned. Delete? (Point renamed on AB884.)
AB610 -extend to AB17AB619 -change WP1 AB130 --> "RR130"AB660 -change WP3 AB472 --> "RR472"AB663Lak -this route is unsigned. Delete?AB677 -change WP3 50Ave --> "50St"AB684 -check location of WP9 "LanSt" (Another case of imperfect coords in the shapefiles. Adjusted.)
AB616 -change WP10 RR12 --> "AB778_S"
AB661 -change WP4 TR630 -->"AB769_N"
Labels chosen because the concurrent route doesn't leave the multiplex here; it just quietly begins/ends, with no junction as such. I chose the intersecting road name instead.
AB616 -consider splitting @ AB 2A (not co-signed)
AB663 -consider splitting route @ AB 63 (not co-signed)
AB677 -consider splitting route @ AB 2 (not co-signed)
AB695 -consider splitting route @ AB 35 (not co-signed)
These are cases of our "implied concurrency" or "implied multiplex" practice on TM. Even if a route is not signed, or not designated, on a short hop along another route, the connection is plotted within a single file anyway. This helps with continuity, not having too many distinct routes in the HB, etc.
AB619 -change WP15 AB/SK --> "AB17/SK17" and check the co-ordinates
AB641 -change WP4 AB/SK --> "AB17/SK17"
At route endpoints, regional boundary labels take precedence over exit numbers or intersecting routes.
The coordinates came from the shapefiles, and line up with Mapbox Satellite & ESRI WorldImagery.
AB628
-change WP4 ParEdm --> "231St" and check the co-ordinates
These coords came from QGIS, as a result of my "truncate to the municipal boundary" policy I decided on upthread. The boundary was just a tiny tiny bit west of the road junction. The point is shown on the municipal boundary in ESRI WorldTopoMap.
AB663 -add two WPs @ Railway Ave and 1 St (Colinton)
Another one like
NS NS322 NanAve OchSt via Thistle St. No need to plot out every turn, especially in small communities like this. Having the point at Main & Railway might be arguably more useful though.
Moved, as it results in slightly better shaping.AB686 -convert SP11 to WP (this is the location of the future extension of AB 686 shown on the Progress Chart)
I couldn't find any road name to name this point after, so I left it hidden. With no GMSV in the area, I was also at a loss for finding any signage for a nearby or distant placename.
https://github.com/TravelMapping/HighwayData/pull/2077