canabs: Alberta Provincial Highways 500-986

[yakra]

Primary data source = GeoBase shapefiles, as with CANAB Alberta Provincial Highways 1-216
I have some files (AB 500-546) on a thumb drive that have been gathering dust, edited between 2013-10-23 and 2014-05-27. Nothing has been uploaded yet; I'm just starting this topic to note that work has indeed begun.
I've been thinking of taking the approach used for the USAKY and GBNA systems, and temporarily breaking this up into four subsystems (CANAB5, CANAB6, CANAB7, and finally CANAB8, which would also include the three AB9xx routes) during development. Once all four subsystems undergo peer review and become ready for activation, they'd be merged into a single system. In the meantime, the individual subsystems could be activated as they become ready. This may or may not actually happen; I'll make the call once the AB5xx routes are drafted.

Don't expect to see much activity here for a while; my priorities at the moment are an ongoing Arkansas cleanup, and moving USANYP toward activation.

[yakra]

AB500 - 599
Canonical Shapefiles: NRN_AB_13_0_ROADSEG

Route Numbers:
500 501 503 504 505 506 507 508 509
510 511 512 513 514 515 519
520 521 522 523 524 525 526 527 528 529
530 531 532 533 534 535 537 539
540 541 542 543 544 545 546 547 549
550 552 555 556
560 561 562 563 564 566 567 569
570 573 574 575 576 577 579
580 581 582 583 584 585 586 587 589
590 591 592 593 594 595 597 598 599

Shaping points temporarily visible for gisplunge:
501: X488812
509: X503070 X901017 X355839 X106558
511: X631769 X978831
524: X411320
541: X274741
547: X896474 X264754 X696998
556: X175143
575: X845516
576: X683233
579: x1 x2 x5 x8 x9
584: X374366 X614237

Indetermini:
560 Check signage @W end on Glenmore Trail. Signed W from 791 -- "ends" where? Call it 201 anyway?
563 Unsigned within Calgary city limits
564 Check signage @W end

Unsigned:
501 "AB2 Trk (Cardston)"
580 N-S spur via RgeRd14 & 10Ave, Carstairs

ToDo / FixMe:
501: needs shaping point(s) near AB4_N
513: extend E
519: add AB843
531: Edit OSM @ E end
534: extend E
542Bro: fix AB873 points
583: extend file (13 vs 14 shapefiles?) / relabel endpoint

Implied multiplexes:
Split 501?

Nota Bene:
586 not included in QGIS project file. Oops.

[yakra]

AB600 - 699
Canonical Shapefiles: NRN_AB_14_0_ROADSEG

Route Numbers:
600 601 602 603 604 605 607 608 609
610 611 613 614 616 617 619
620 621 622 623 624 625 626 627 628 629
630 631 633
640 641 642 643 644 645 646 647
651 652 654 655 656 657 658 659
660 661 663 665 666 667 668 669
670 671 672 674 676 677 679
680 681 682 683 684 685 686 688 689
690 691 692 695 697

Shaping points temporarily visible for gisplunge:
610: x343
620: x1 x5
643: X924624 outside tolerance; treat as normal shaping point
686: 3 4 5 12 14 20

Indetermini:
613: GIS to 45 St; signed from AB2A/13. Highway Connector in Wetaskiwin?
623: Looks legit. Not an indeterminus.
627: No signage E of Edmonton corporate limits @ 215St. Highway Connector?

ToDo / FixMe:
620: delete +x2 & +x4, or +x3; OSM is right about TowRd
661: split @ ferry
663: relabel point on AB55
663: RgeRd174.6? Is a decimal point an allowable character? Choose different point(s) for shaping?
667: recenter point on AB43; edit OSM
679: Edit OSM @ RgeRd155A; AB750
688: gisplunge new/old alignment divergence; fix points on AB2

[yakra]

AB700 - 799
Canonical Shapefiles: NRN_AB_14_0_ROADSEG

Route Numbers:
717 719
721 722 723 724 725 726 727 729
730 731 732 733 734 735 736 737 739
740 741 742 743 744 747 748 749
750 751 752 753 754 756 757 758 759
760 761 762 763 764 765 766 769
770 771 772 774 775 776 777 778 779
780 781 782 783 785 786
791 792 795 797 799

Shaping points temporarily visible for gisplunge:
724: X747655
734: 10 30 33 35 65 68 71
750: X134152 X365680 X773850 X753335 X189652
753: X294553
754: X388838 X705208 X120162 X166501
770: X964841

Indeterminus:
772: Calgary, Highway Connector, yadda yadda

Unsigned or decommissioned:
782

ToDo / FixMe:
724: fix AB43 point labels; check older shapefiles & prov. map
727: fix AB49 points; check older shapefiles & prov. map
730: *OldTwpRd862 -> *OldTR862
734: TwpRd310A, or ForTruRd? ForTruRd.
748: relabel TCHYel/AB16@25St
748: *OldRgeRd152 -> *OldRR152
750: Look for old alignment near +X135172 -- GIS (no), Topo (yes) -- replaced with *OldAB750_Gif

[yakra]

AB800 - 986
Canonical Shapefiles: NRN_AB_14_0_ROADSEG

Route Numbers:
800 801 803 804 805 806 808
810 811 812 813 814 815 816 817
820 821 822 824 825 827 829
830 831 833 834 835 836 837 838 839
840 841 842 843 844 845 846 848 849
850 851 852 853 854 855 856 857 858 859
860 861 862 864 866 867 869
870 872 873 875 876 877 879
880 881 882 883 884 885 886 887 889
892 893 894 895 897 899
901 947 986

Shaping points temporarily visible for gisplunge:
813: 2 8 9 21 26 30
841: X974990
842: X221645 X164443 (all)
858: X485881
875: X885016 X488750
881: 20 21 30 35 44 45 46 48 49 956 57
897: X416691 X998627 X403348 X927011
899: X725479
901: X127401
947: x1
986: 11 23 26 29 32

Indetermini:
814: GIS to "Wetaskiwin No. 10, County of" / "Wetaskiwin"; signed from AB13. Highway Connector in Wetaskiwin?
833: GIS to "Camrose" / "Camrose County"; signed from AB13. Highway Connector in Camrose?
869: GIS to TwpRd442; unsigned N of AB13. Highway Connector in Sedgewick?

ToDo / FixMe:
838Kne = Kneehill County (check placename as listed in shapefiles)
862New = Newell No. 4, County of (check similar "County of" placenames in CSVs)
870 thru 881: recheck GIS 14.0 (drafted using old version)
880: retain draft MT/AB coords to sync with mt.sr409
897: needs shaper(s) both sides of AB641

Implied multiplexes:
Connect 881? (134.80 + 43.73 + 164.81 mi.)

canab:
https://github.com/TravelMapping/HighwayData/pull/1823
55: AB28_S +-> AB28_W
831: fix AB15 points
833: add point to AB13
854: fix AB14 points
866: fix AB55 point label
885: fix AB61 point label
893: reposition TCH16 point
986: recenter AB35 point

Before devel:
All City/Abbrev segments in correct order, 800 series especially
  761/bra/pon/wet -> 761/pon/wet/bra
  838/kne -> kne/838
  843/pic -> pic/843
  862/new -> new/862
  881/har -> har/881
  899/emp -> emp/899
verify that all routes are drafted
831: "Township Road 640.5" per shapefiles; see AB663
855: Decimal Twp/Rge Rds

[yakra]

AB633
http://www.transportation.alberta.ca/projects/edmontonarea_flash.html

New Roadway - Hwy 43 to Hwy 779

PROJECT INFORMATION

Location: Hwy 633 from Hwy 43 to Hwy 779,
14.4 km in total.

Description: A planning study has been
completed to identify the future alignment and
configuration of Highway 633 between Highway
43 and Highway 779. The objectives of the study
are to confirm the feasibility and cost of
constructing Highway 633 on the previously
designated straight-through alignment, review
expected traffic changes in the highway network
with construction of the missing Highway 633
link, and identify future right-of-way
requirements and access points.

A Public Information Session was held on May 5,
2011 at Muir Lake Community Hall. Information
shown at the session is available for download.

Schedule: Planning has been completed.
Construction is outside the three-year program.

Consultant: AMEC Earth & Environmental

For more information, contact:  Roberta
Clifford, P. Eng., Sr. Transportation Engineer,
AMEC Earth & Environmental, ph. 780-377-3692,
roberta.clifford@amec.com

PROJECT DOCUMENTATION
Location Plan
Information Session - Fact Sheet (24MB)
Information Session - Display Boards (1.9MB)
Information Session - Alignment Drawings (8.2MB)

With this as the most recent info on the Alberta Provincial Highway Projects site, I'm more comfortable taking the path I was already considering for AB633; including two sections:
AB633, from AB757 to AB43.
AB633 (St. Albert), from AB779 to AB2.

Here's my original analysis, transferring the text into this post from the AB600 - 699 master post upthread.

Section 1, AB757 to AB43:
  GIS: RTNUMBER1 = 633
  ProChart: Asphaltic Surface Course - Final
  Include.
Section 2, AB43 to Range Road 21:
  GIS: RTNUMBER1 = 633
  ProChart: Graded / Gravelled
  GMSV: No signage pointing east from AB43 in May 2013; no imagery further east.
  Include? Treat as unsigned; wait for updated GMSV or field reports.
Section 3, Range Road 21 to (53.657542°, -114.150049°):
  GIS: RTNUMBER1 = None; L_STNAME_C = "633 Highway"
  ProChart: Proposed Route
  GMSV: No coverage
  Do not include.
Section 4, (53.657542°, -114.150049°) to (53.657541°, -114.137948°):
  355072-2 http://www.openstreetmap.org/?lat=53.657542&lon=-114.150049
  355072-1 +243004-2 http://www.openstreetmap.org/?lat=53.657542&lon=-114.148982
  243004-1 +82103-2 http://www.openstreetmap.org/?lat=53.657541&lon=-114.141671
  82103-1 +15433-2 http://www.openstreetmap.org/?lat=53.657541&lon=-114.141507
  15433-1 http://www.openstreetmap.org/?lat=53.657541&lon=-114.137948
  GIS: RTNUMBER1 = 633
  ProChart: Graded / Gravelled
  GMSV: No coverage
  Include? A Segment of Independent Not-Much-Utility. Assume it's unsigned; wait for updated GMSV or field reports.
Section 5, (53.657541°, -114.137948°) to Range Road 15:
  GIS: RTNUMBER1 = None; L_STNAME_C = "633 Highway"
  ProChart: Proposed Route
  GMSV: No coverage
  Do not include.
Section 6, Range Road 15 to Range Road 14:
  GIS: No road segment here
  Satellite: No road segment here
  ProChart: Proposed Route
  GMSV: No coverage
  Do not include.
Section 7, Range Road 14 to AB779:
  GIS: RTNUMBER1 = 633
  ProChart: Graded / Gravelled
  GMSV: just this in Aug 2009
  Include? Follow Section 2's precedent and wait for definitive evidence of signage to the west.
Section 8, AB779 to St. Albert:
  GIS: RTNUMBER1 = 633
  ProChart: Asphaltic Surface Course - Final
  GMSV: Signed east from AB44. From there...?
  Include.
Section 9, St. Albert limits to AB2:
  GIS: RTNUMBER1 = 633
  ProChart: Multi-lane / Divided
  GMSV: no shields at AB2, RgeRd260, or corporate limits just west of there.
        blade signs = "Sec Rd 633" @ RgeRd260; "Villeneuve Rd" @ RayGibbon Dr & east.
  Highway Connector?
  Initially included; ask @julmac his opinion; now thinking delete.
The southern temp. route / detour that OSM & Google show via RgeRd20, TwpRd541, and RgeRd14 appears apocryphal; I'm unable to confirm it in any official source. (Official sources *do* seem to point to a routing via TwpRd542 -- albeit a proposed & incomplete one.) If it turns out to be signed, I can add it later on.

[yakra]

AB761
No projects listed on the Provincial Highway Projects site.

Section 1, AB54 to AB12:
  GIS: RTNUMBER1 = 761
  ProChart: Asphaltic Surface Course - Final
  GMSV: Well signed
  Include, AB761
Section 2, AB12 to just south of Township Road 413:
  GIS: RTNUMBER1 = 761
  ProChart: Asphaltic Surface Course - Final
  GMSV: signed from AB12; no coverage N of there
  Include, AB761
Section 3, just south of Township Road 413 to (52.594330°, -114.625562°):
  GIS: RTNUMBER1 = 761
  ProChart: Graded / Gravelled
  GMSV: No coverage
  Include, AB761
Section 4, (52.594330°, -114.625562°) to just south of Township Road 423:
  GIS: No road segment here
  ProChart: Proposed Route
  GMSV: No coverage
  Do not include.
Section 5, just south of Township Road 423 to AB53:
  GIS: RTNUMBER1 = 761
  ProChart: Graded / Gravelled
  GMSV: No coverage
  Include, AB761 (Ponoka County)
Section 6, implied concurrency with AB53:
  GIS: RTNUMBER1 = 53; L_STNAME_C = "53 Highway"
  GMSV: No coverage
  Include, AB761 (Ponoka County)
Section 7, AB53 to AB607:
  GIS: RTNUMBER1 = 761
  ProChart: Graded / Gravelled
  GMSV: No coverage
  Include, AB761 (Ponoka County)
Section 8, AB13 to Township Road 465:
  GIS: RTNUMBER1 = 761
  ProChart: Graded / Gravelled
  GMSV: signed from AB13; no coverage N of there
  Include, AB761 (Wetaskiwin No. 10 County)
Section 9, Township Road 465 to (53.032574°, -114.733621°):
  GIS: No road segment here
  ProChart: Proposed Route
  GMSV: No coverage
  Do not include.
Section 10, (53.032574°, -114.733621°) to AB616:
  GIS: RTNUMBER1 = 761
  ProChart: Graded / Gravelled
  GMSV: signed from AB616; no coverage S of there
  Include, AB761 (Brazeau County)

[yakra]

a couple tricky waypoint labeling scenarios / decimal points?
(topic may not be visible to all forum members)

*Old Township Road 862
*Old Range Road 152
Range Road 174.6
Township Road 640.5
Range Road 171.3
Range Road 173.3
Township Road 672.5

[yakra]

*Old Township Road 862 -> *OldTR862
*Old Range Road 152 -> *OldRR152

Stylistically a bit different from the "TwpRd" & "RgeRd" conventions otherwise used, but forward-compatible with a potential province-wide TwpRd -> TR / RgeRd -> RR relabeling, which may or may not end up happening.

I think that makes everything just about ready to hit the HB in devel mode.
I'll put some CSVs together & do whatever else I need, and open a pull request.

convenient link for future reference

[oscar]

FWIW, in Saskatchewan there is an active route with an RR abbreviation for a Range Road. Some of the in-dev cansk routes I've been slowly adding to the HB have RR abbreviations and/or TR for Township Roads.

We probably should have consistent abbreviations for the prairie provinces, though I don't feel strongly about RgeRd vs. RR, or TwpRd vs. TR.

[yakra]

If you've used RR & TR in Saskatchewan, and have not used RgeRd & TwpRd, you can just keep on doing what you have been doing, and I'll have an excuse to do an Alberta-wide relabeling.

With the way section line roads are signed in Manitoba, I prefer to keep the convention I'm using there in place.
If we're able to use a common convention for Alberta & Saskatchewan, I'm all for it.
Can't forget sk.ab017san.wpt.
I believe this would be a carbon copy of sk.sk017san. oscar, you have a say WRT this route.

[yakra]

My current plan is to do a province-wide relabeling, including active systems:
TwpRd -> TR
RgeRd -> RR
Any objections? Oscar, what's your opinion here?

Edit: Done, for active systems. No pull request (yet), but here's a comparison:
https://github.com/TravelMapping/HighwayData/compare/master...yakra:KingRalph

canabs has 323 WPT files, so for that I'll make an adaptation of the program I wrote to help with the TNs -> TN relabeling in Tennessee. <--Done.

[oscar]

Go ahead. But two TwpRd__ and RgeRd___ points on active routes are in use, so only for those routes the old label needs to be kept and hidden:

ab.ab001alak(12): AB1_W AB1_E TWPRD265B
ab.ab043x(2): AB2/43 RGERD63

[yakra]

Yep. Those are done.
The data's already in place; I'll just open a pull request.

[yakra]

Before preview:
https://github.com/TravelMapping/HighwayData/pull/1840

Points in correct order?
511 525 594
622 647 684
742 748
838 838Kne

Endpoints, labels & related
527: TR135A -> FlyEastRd
546: TR194A -> BluWilPP
601: GMSV as shown in Google; extend
608Ami: TR415 -> End
642: fix AB777 labels
663Bea: TR670 -> End
666: RR85 -> End
695: TR1011A -> End
754: NeeDr -> LakDr
769: TR630 -> AB661_W
855: replace TR394 with AB601

AB5xx Twp/Rge labels @uselessplex ends?
Check provincial boundary points near intersecting roads
834Chi: Chipman, or Tofield? Chipman. It does enter, per AltaLIS & NRN shapefiles. Less ambiguous than Tofield.
implied multiplexes
indetermini -- ArcGIS - Alberta County Municipal District Map
http://www.altalis.com/products/property/municipal_boundaries.html

Before active:
833: consider relabeling AB14 based on HDX label
899: consider relabeling AB13_W based on HDX label
NMPs
datacheck