Travel Mapping

Highway Data Discussion => In-progress Highway Systems & Work => Completed Highway Systems Threads => Topic started by: si404 on April 10, 2017, 04:53:08 am

Title: Montana Secondary State Highways
Post by: si404 on April 10, 2017, 04:53:08 am
This system is ready for review
Title: Re: Montana Secondary State Highways
Post by: mapcat on April 10, 2017, 12:32:15 pm
I'm still willing to do this set once I'm done with BC. Are you and Oscar finished editing the rest of the BC routes I hadn't checked yet, including removing the excessive named waypoints? I saw that you or he had trimmed some of the unneeded shaping points and he had added some points to take care of some V_D errors, but I hadn't noticed whether some of the points at unnecessary intersections had been culled.
Title: Re: Montana Secondary State Highways
Post by: Duke87 on May 10, 2017, 09:45:43 pm
Some comments to start with. One general note, I do know that some of Montana's SR's are unsigned. Need to make sure these are not included in the finished product.

SR 201: point "CanSt should be "DawAve" (street name is Dawson Avenue)
SR 202: looks OK
SR 203: point "RaiLn" should be "RatLn" (street name is Rathbun Lane), point "LonRd" should be "LogRd" (street name is Logan Road)
SR 204: looks OK
SR 205: looks OK
SR 206: point "TavLn" should be "TabLn" (street name is Taber Lane)
SR 291: looks OK
SR 363: looks OK
Title: Re: Montana Secondary State Highways
Post by: mapcat on May 13, 2017, 10:19:25 pm
These all appear to be unsigned (nothing showing up at logical places in GMSV, StreetSide, and CorcoHighways imagery), and IMO can be safely deleted:

217
222
225
231
292
334
342
353
356
364
396
398
413
420
471
472
564

A few others may be unsigned, but imagery was poor or absent, so I can't be sure:

283 (Corco says it's unsigned)
478
572
Title: Re: Montana Secondary State Highways
Post by: Duke87 on May 20, 2017, 12:10:44 pm
SR 207: looks OK
SR 208: looks OK
SR 209: looks OK
SR 210: consider making point "TurRd" simply "Tur" (for Turah). The street it is at does not appear to have a signed name. Also consider adding a couple shaping points towards the east end to keep it on the correct side of I-90.
SR 211: rename point "SR353" to "MoiValRd" since SR 353 has been removed from system.
SR 212: rename point "SR353" to "MoiValRd" since SR 353 has been removed from system.
SR 213: point "CenAve" could stand to be relocated slightly to the southwest (Mapnik does not show the correct geometry of this intersection). Point "GleCutRd" is not located at an intersection, maybe convert this to a shaping point? Point "RadBaseLn" should be "RadBaseRd".
SR 214: looks OK
SR 215: point "NapRd" should be "NepRd" (street name is Nepstad Rd).
SR 218: point "ChiSchRd" should be named "ChrSchRd" and should be located at the intersection 2 miles to the west (your point is at an intersection with an unnamed dirt road that Mapnik is spuriously also calling "Christenson School Road"). Rename point "SR225" to "BooTrl" since SR 225 has been removed from system.
SR 219: looks OK
SR 220: looks OK
SR 221: looks OK
Title: Re: Montana Secondary State Highways
Post by: Duke87 on May 23, 2017, 08:58:07 pm
General question here: I'm noting a lot of cases where words associated with geographic features are using a standard abbreviation for that feature rather than the first three letters of the word - e.g. Vly for "Valley", Crk for "Creek", and "Mtn" for "Mountain". Should I be flagging these as errors to correct or are they fine as is? They are flagged in several of the following.

SR 223: rename point "SR564" to "BraRd" since SR 564 has been removed from system. Point "S100" is located at an unnamed dirt road. Maybe make this a shaping point?
SR 224: Truncate to point 1200S. This is the intersection that matches the official road log length of 18.95 mi from US 2.
SR 226: point "SR459" needs to be renamed "55thAve" since there is no SR 459 in the system (nor should there be). Point "FisRd" needs to be relocated about 400 ft north, the geometry of this intersection in Mapnik is incorrect. Point "RedButRd" should be "RedButLn". South end of route should be about 350 ft further down road (where pavement ends).
SR 227: looks OK
SR 228: point "HarAve" should be "CliSt" (Cligan St).
SR 229: looks OK
SR 232: matter of nomenclature - should all the points of the form "20N" etc. be "Rd20N"? "Road" does appear to be part of the proper name.
SR 233: Same issue as SR 232. Also, point "WilCreRd" should be "475N" (or "Rd475N")
SR 234: point "SucCrkRd" should be "SucCreRd". Point "13St" should be "13thSt".
SR 235: point "EVlyCenSpr" should be "EValCenSpr".
SR 236: point "SaltCrkRd" should be "SaltCreRd". Point "MtnViewRd" should be "MouViewRd"
SR 237: point "WolCrkRd" should be "WolCreRd"
SR 238: point "JesRd" needs to be relocated about 600 ft SE. The road appears to have been straightened in this area, Mapnik is outdated and shows the old curvier path. Point "McDonCrkRd" should be "McdCreRd".
Title: Re: Montana Secondary State Highways
Post by: oscar on May 23, 2017, 09:44:18 pm
General question here: I'm noting a lot of cases where words associated with geographic features are using a standard abbreviation for that feature rather than the first three letters of the word - e.g. Vly for "Valley", Crk for "Creek", and "Mtn" for "Mountain". Should I be flagging these as errors to correct or are they fine as is?

I use Crk and Mtn a lot, in the jurisdictions I manage, and the CHM "rulebook" explicitly allows them. (Crk comes in handy sometimes to distinguish Creek from Crescent.) I'm not sure about Vly, which I don't use, or Cyn (for Canyon, and where I grew up there's lots of canyons and road signs using the Cyn abbreviation) which I like but seems disfavored.

Especially with Crk and Mtn, so long as they used consistently in a jurisdiction instead of Cre and Mou, it's up to the responsible team member.
Title: Re: Montana Secondary State Highways
Post by: compdude787 on May 24, 2017, 05:49:07 pm
Crk, Mtn, Vly, and Cyn are pretty common abbreviations, so I don't see any issue with them being used.
Title: Re: Montana Secondary State Highways
Post by: si404 on June 01, 2017, 06:49:50 am
Points like 1200S are consistent with the labels I inherited in the state, and also consistent with neighbouring states. I haven't changed them (nor Cyn and Vly), though am willing to be convinced to do so.

I've made the other changes.
Title: Re: Montana Secondary State Highways
Post by: Duke87 on June 20, 2017, 08:49:38 pm
If there's precedent for the use of "Mtn", "Crk", etc. and some general consensus that this is acceptable then I'm fine with it. I won't flag any more instances of these.

SR 239: Extend 0.202 mi S of SR 541 JCT (road log and signage confirms this). "6St_E" → "6thSt_E".
SR 240: OK
SR 241: relocate "VioRd" ~450' NE
SR 243: "CouPittRd" → "CouPitRd"
SR 244: "MainSt_W" → "MainSt_E"
SR 245: OK
SR 246: OK
SR 247: OK
SR 248: OK
SR 249: OK
SR 250: "BerRd" → "Rd2048"
SR 251: OK
SR 252: OK
SR 253: OK
SR 254: OK
SR 255: Coord mismatch at intersection with US 2
SR 257: OK
SR 258: OK
SR 259: OK
Title: Re: Montana Secondary State Highways
Post by: Duke87 on July 20, 2017, 09:41:08 pm
SR 260: truncate to BobRd (per road log)
SR 261: truncate to I-94 (per road log). MT 7 will also have to be adjusted ("SR261" → "2ndAve").
SR 263: truncate to US 93 (per road log). I-90BLMis and US93BusMis will also have to be adjusted ("SR263" → "MulRd")
SR 269: "BlaRd" → "BlaLn", "PosLn" → "PopLn"
SR 271: OK
SR 273: OK
SR 276: OK
SR 277: OK
SR 278: OK
SR 279: "SR231" → "GreMeaDr", "BriRd" → "BirRd", "PonDr" → hidden shaping point (no intersection here)
SR 280: OK
SR 282: OK
SR 284: OK
SR 285: OK
SR 286: OK
SR 287: OK
SR 288: OK
SR 290: OK
Title: Re: Montana Secondary State Highways
Post by: the_spui_ninja on July 20, 2017, 10:34:17 pm
SR 261: truncate to I-94 (per road log). MT 7 will also have to be adjusted ("SR261" → "2ndAve").
I remember some time back (here (https://github.com/TravelMapping/HighwayData/issues/155)) the nonexistent business loop in Wibaux was removed; is that section not part of 7 just not a state highway then?
Title: Re: Montana Secondary State Highways
Post by: yakra on July 21, 2017, 03:21:41 am
Never used "Vly" or "Cyn" personally, but these are USPS standard abbreviations (https://pe.usps.com/text/pub28/28apc_002.htm), as are "Crk" and "Mtn". ISTR there being some discussion in the CHM days about this, with Crk and Mtn being OKed on these grounds.
Title: Re: Montana Secondary State Highways
Post by: Duke87 on July 23, 2017, 02:31:38 pm
SR 261: truncate to I-94 (per road log). MT 7 will also have to be adjusted ("SR261" → "2ndAve").
I remember some time back (here (https://github.com/TravelMapping/HighwayData/issues/155)) the nonexistent business loop in Wibaux was removed; is that section not part of 7 just not a state highway then?

It is a state highway, MDT's road log has it as route P-97 (P is for primary). It does not, however, have a signed route number, so there is nothing for us to map it as.

Also note that the internal numbers in the road log do not necessarily align with signed numbers - for example, MT 7 is in the log as route P-27.
Title: Re: Montana Secondary State Highways
Post by: the_spui_ninja on July 27, 2017, 12:30:45 am
SR 261: truncate to I-94 (per road log). MT 7 will also have to be adjusted ("SR261" → "2ndAve").
I remember some time back (here (https://github.com/TravelMapping/HighwayData/issues/155)) the nonexistent business loop in Wibaux was removed; is that section not part of 7 just not a state highway then?

It is a state highway, MDT's road log has it as route P-97 (P is for primary). It does not, however, have a signed route number, so there is nothing for us to map it as.

Also note that the internal numbers in the road log do not necessarily align with signed numbers - for example, MT 7 is in the log as route P-27.
Gotcha.
Title: Re: Montana Secondary State Highways
Post by: Duke87 on August 26, 2017, 10:51:30 pm
SR 294: OK
SR 295: not signed, delete
SR 297: "23E116Nc" → "UppNihRd", "23E116Nd" → "HedRd", "191N19E_E" → "BerRd" (also point needs to be recentered), "191N19Ef" → "LucRd", "191N19Ed" → "ProRd", "191N19Ec" → "NielCrkRd", "JudGiftRd" → "JudGapRd"
SR 298: OK
SR 300: Truncate to CouRd (per road log)
SR 302: OK
SR 306: OK
SR 308: "BreRd_W" → "BroRd_W", "BreRd_E" → "BroRd_E"
SR 310: OK
SR 311: OK
SR 313: "CenAve" → "I-90Bus/47". Truncate to the cattle guard just past CR40A - this appears to be a maintenance changeover point and is the correct 38.588 miles from the beginning, matching the road log.
SR 314: OK
SR 317: OK
SR 320: extend north to Main St (per road log)
Title: Re: Montana Secondary State Highways
Post by: Duke87 on September 02, 2017, 10:27:48 pm
SR 323: "FinButRd" → "FinButTrl"
SR 324: relocate point "HenRidRd" ~500' NE. OSM does not show this intersection correctly, HERE does.
SR 325: not signed, delete
SR 326: OK
SR 327: "BaiR" → "BaiRd", "CinSt_S" → "CliSt_S"
SR 328: "ExeRd" → "ExieRd"
SR 330: incorrect routing. Should follow Cascade Hound Creek Rd and Millegan Rd (HERE shows the correct routing).
SR 331: OK
SR 332: OK
SR 335: OK
SR 336: "SR413" → "CarRd_W"
SR 338: OK
SR 340: OK
SR 341: truncate to what HERE labels "17009 Rd". This is the correct 21.93 miles from the beginning, matching the road log.
SR 343: "GreHillSch" → "GreHillSchRd", "SR17" → "StrRd"
SR 344: OK
SR 345: "NexPerDr" → "NezPerDr". Truncate to StuRd_E (per road log)
SR 346: OK
SR 347: OK
SR 348: OK
SR 350: truncate to Lobo Rd (per road log)
Title: Re: Montana Secondary State Highways
Post by: Duke87 on October 07, 2017, 12:21:16 pm
Now that I have a primary working computer again, back at this

SR 352: "CampTufR" → "CampTufRd"
SR 354: OK
SR 357: "BarGluRd" → "BarGulRd". Extend to Warm Springs Creek Rd (per road log) - this is shown as "National Forest Development Road 163" on OSM, HERE shows the name mentioned in the road log.
SR 358: OK
SR 359: OK
SR 360: truncate to Camas Creek Rd. This is the correct 18.217 miles from the beginning, matching the road log.
SR 363: OK
SR 365: "PimmRd" → "PMMRd", "SR225" → "BooTrl"
SR 366: "NicR" → "NicRd", "SR225" → "BooTrl_S", truncate to SR 223 (per road log)
SR 370: wrong road is mapped - should be on Bell Crossing, not Victor Crossing
SR 373: extend east to Summerdale Rd (per road log)
SR 374: extend north to 1st Ave in Outlook (per road log)
SR 375: does not officially exist per 2013 road log. GMSV shows signage in place at south end as of Jul 2012, no more recent imagery available. Decomissioned, perhaps?
SR379: "SR225" → "BooTrl"
Title: Re: Montana Secondary State Highways
Post by: Duke87 on October 15, 2017, 08:28:43 pm
SR 381: OK
SR 382: OK
SR 384: "MT47" →  "I-90BL"; points "IronSprRd", "SarRd", "HopeRd", and "BeaCrkRd" need recentering
SR 386: OK
SR 387: OK
SR 391: truncate to the cattle guard at 45.266555, -105.645275. This is the correct 16.513 miles from the beginning, matching the road log.
SR 393: OK
SR 396: add back in, this route is signed at the junction with SR 241 (per GMSV)
SR 399: OK
SR 400: truncate to Straw Rd. This is the correct 12.335 miles from the beginning, matching the road log.
SR 401: OK
SR 405: OK
SR 408: points "2ndRd/8thLn" and "3rdLn_S" need recentering
SR 409: "HighSchRd" → "HillSchRd", extend north to Canadian border
Title: Re: Montana Secondary State Highways
Post by: Duke87 on October 24, 2017, 09:28:12 pm
SR 411: OK
SR 412: OK
SR 416: "I-94" → "I-90", "SR 418" → "PryRd", point "BenRd" needs recentering
SR 417: OK
SR 418: not signed, delete
SR 419: points "GroCrkRd" and "RosRd" need recentering, "HarLn" → "LitRocCrkRd", "NyeRd_S" → "NyeRd_W"
SR 421: points "HeaRidRd" and "SkiRd" need recentering, "StiEstR" → "StiEstRd"
SR 422: OK
SR 424: "MerRd_N" → "MerRd, truncate to this point (per road log). Add point at US 93 Alt/Kalispell Bypass.
SR 426: relocate point "CleLn" to western branch of the small loop here - the eastern branch is abandoned/impassable.
SR 427: OK
SR 430: OK
SR 431: OK
SR 432: "SR366" → "TibDamRd"
SR 434: truncate to MT 200 (per road log)
SR 435: "SR434" → "FlatCrkRd", "OldElkCrkR" → "OldElkCrkRd"
SR 437: OK
SR 438: "Bay" → "BayRd"
Title: Re: Montana Secondary State Highways
Post by: yakra on October 26, 2017, 03:59:24 am
LitRocCrkRd is not valid. (http://cmap.m-plex.com/tools/manual_wayptlabels.php)
LitRocRd would be one of several acceptable options; field (https://www.google.com/maps/@45.4337241,-109.7677198,3a,20.4y,319.26h,85.58t/data=!3m6!1e1!3m4!1s2e49mS3A9MkYeIU38IK1HQ!2e0!7i13312!8i6656) signage suggests this may be best.

OldElkCrkRd is similarly not valid
Title: Re: Montana Secondary State Highways
Post by: Duke87 on November 19, 2017, 01:46:24 pm
SR 441: needs a shaping point between FaiRd_W and FaiRd_E. Route follows Fairmont Rd as OSM shows.
SR 444: point "HorRd" needs recentering
SR 446: OK
SR 447: point "RosEstDr" needs to be moved and renamed (there is no intersection here, or any intersection with a road of this name)
SR 448: "Rd80_S" → "80S" (matching format of other similarly named points)
SR 449: truncate to 160N (this matches the 16.59 miles from US2 shown in road log)
SR 451: coord mismatch with WY 345 at state line'
SR 453: OK
SR 457: OK
SR 462: OK
SR 463: OK
SR 464: OK
SR 466: OK
SR 467: "MT200_W" → "MT200", "MT200_E" → "MT200S"
SR 470: OK
Title: Re: Montana Secondary State Highways
Post by: Duke87 on November 25, 2017, 02:40:41 pm
SR 471: add back in, this route is signed at the junction with SR 200 (per GMSV)
SR 473: "ChiRd" → "LloCrkRd", "BarnDrawR" → "BarnDrawRd"
SR 474: OK
SR 480: OK
SR 482: OK
SR 484: OK
SR 486: "RaiSt" → "RaiSt_W", "GlaNP" → "FlaNF"
SR 487: OK
SR 489: extend to end of pavement at 46.570930, -105.652450 (per road log)
SR 493: OK
SR 494: OK
SR 500: "ToWenKimRd" and "MelRd" → hidden shaping points (there is no intersection at either point)
Title: Re: Montana Secondary State Highways
Post by: Duke87 on December 10, 2017, 04:59:17 am
SR 503: OK
SR 504: OK
SR 507: "5St" → "5thSt"
SR 508: OK
SR 509: not signed, delete
SR 511: OK
SR 512: OK
SR 513: extend down Lower Willow Creek Rd to junction at 46.559778, -113.346540. This is the correct 9.663 miles from beginning (per road log)
SR 516: OK
SR 517: OK
SR 518: OK
SR 522: OK
SR 528: truncate to PraElkRd, this is the western end of the route (per road log). Points "HigRd" and "MenRd" need recentering.
SR 529: OK
Title: Re: Montana Secondary State Highways
Post by: oscar on December 10, 2017, 07:18:10 am
Hasn't SR 511 been truncated to end short of the border, since that border crossing (Big Beaver/Whitetail) has been permanently closed since 2013 (https://en.wikipedia.org/wiki/List_of_Canada%E2%80%93United_States_border_crossings#Closed_land_ports_of_entry)? Google Maps, Bing Map, and their satellite views show the truncation of SR 511 and its counterpart SK 34, and that SR 511 is barricaded about 0.1 mile south of the border, just south of the former border station.

I mention this only because while doing some county-snagging on the Canadian side, I saw signs at the SK 18/SK 34 junction, indicating that the border had been closed south of there and SK 34 no longer reached the border.
Title: Re: Montana Secondary State Highways
Post by: Duke87 on December 13, 2017, 11:41:58 pm
Hasn't SR 511 been truncated to end short of the border, since that border crossing (Big Beaver/Whitetail) has been permanently closed since 2013 (https://en.wikipedia.org/wiki/List_of_Canada%E2%80%93United_States_border_crossings#Closed_land_ports_of_entry)? Google Maps, Bing Map, and their satellite views show the truncation of SR 511 and its counterpart SK 34, and that SR 511 is barricaded about 0.1 mile south of the border, just south of the former border station.

The most recent Road log from MDT is from 2013 and explicitly lists the end of SR 511 as "Montana/Canadian Line". Unless someone can produce some documentation to the contrary, it does not appear the road has been officially truncated.

Indeed, I don't see why it logically would be, since it is still physically there, and I doubt the difference of a few hundred feet behind a barricade matters to anyone at MDT enough for them to actively take the effort to revise their records.

For our purposes, I'd say just leave the endpoint alone. Someone could have driven through the crossing before it closed, and someone trying to clinch the road now can still get close enough to the endpoint to call it good by most people's standards. And if someone is compulsive enough to be bothered by not being able to drive the last teensy portion, they're probably also compulsive enough to care that it's officially still part of the route even if we were to circumcise it in our mapping.


Also, while I'm posting anyway, here's part of an update:
SR 531: OK
SR 532: OK
SR 534: "SunBlv" → "SunBlvd"
SR 537: extend to Snake Creek Rd. This is the correct 23.126 miles from beginning (per road log)
SR 540: "SR572" → "ChicRd"
SR 541: OK
SR 543: OK
SR 544: Points "GotRd" and "BelcrkRd_S" need recentering
SR 547: extend east by one intersection to Barker Rd. This is the correct 6.477 miles from beginning (per road log)
Title: Re: Montana Secondary State Highways
Post by: Duke87 on December 20, 2017, 07:56:58 pm
SR 548: How to handle new Kalispell bypass? 2013 road log predates this bypass opening, original routing is no longer continuous because of its construction. State GIS map shows bypass and shows 548 still on old road that now dead ends. "SR292" → "WhiStaRd"
SR 551: OK
SR 552: OK
SR 556: OK
SR 559: OK
SR 565: OK
SR 566: OK
SR 567: "SandPipeCrkRd" → "SidePipeRd"
SR 568: not signed, delete
SR 569: points "DryCrkRd", "BeaPondTrl", and "AlpLodeTrl" need recentering. "BeaPondTrl" → "WesTrl"
SR 571: OK
SR 573: points "TenMileRd" and "DagRd" need recentering


This concludes the peer review.
Title: Re: Montana Secondary State Highways
Post by: oscar on December 21, 2017, 12:35:31 pm
One more: North ends of SR 233 and SR 241, at the Canadian border, look like they should be recentered. There are Saskatchewan primary highways on the other side of the border, and when I start working on cansk I want to pilfer the SR 233 and SR 241 coordinates for the south ends of those SK routes.

No need to bother with SR 511, unless you're going to truncate it short of the border. While SK 34 appears to end at the border, you can no longer legally cross the now-barricaded border there. So I'll set SK 34's south end to be different from MT 511's north end, to keep the HB from identifying a false intersection.
Title: Re: Montana Secondary State Highways
Post by: julmac on December 29, 2017, 09:09:42 pm
Hasn't SR 511 been truncated to end short of the border, since that border crossing (Big Beaver/Whitetail) has been permanently closed since 2013 (https://en.wikipedia.org/wiki/List_of_Canada%E2%80%93United_States_border_crossings#Closed_land_ports_of_entry)? Google Maps, Bing Map, and their satellite views show the truncation of SR 511 and its counterpart SK 34, and that SR 511 is barricaded about 0.1 mile south of the border, just south of the former border station.

The most recent Road log from MDT is from 2013 and explicitly lists the end of SR 511 as "Montana/Canadian Line". Unless someone can produce some documentation to the contrary, it does not appear the road has been officially truncated.

Indeed, I don't see why it logically would be, since it is still physically there, and I doubt the difference of a few hundred feet behind a barricade matters to anyone at MDT enough for them to actively take the effort to revise their records.

For our purposes, I'd say just leave the endpoint alone. Someone could have driven through the crossing before it closed, and someone trying to clinch the road now can still get close enough to the endpoint to call it good by most people's standards. And if someone is compulsive enough to be bothered by not being able to drive the last teensy portion, they're probably also compulsive enough to care that it's officially still part of the route even if we were to circumcise it in our mapping.

A similar situation to US 75. Fortunately, I've driven SK 34 / MT 511, but clinching US 75 will be awkward. It's a shame this crossing closed; it's the most scenic of the three options (SK 6 / MT 16, SK 34 / MT 511, and SK 36 / MT 13), but not unsurprising since it connects not much to nothing. It was nicely featured on an episode of "Extreme Frontiers" before it closed.
Title: Re: Montana Secondary State Highways
Post by: oscar on December 30, 2017, 12:55:45 am
A similar situation to US 75. Fortunately, I've driven SK 34 / MT 511, but clinching US 75 will be awkward.

TM shows US 75 stopping about 0.1 mile short of the border, at the exit from the old U.S. customs area. However, last I was there (2013?), I was able to drive from US 75 through the old customs area to the barricade at the border before turning back. Border monuments confirmed that I reached -- or maybe drove a few feet past -- the border. 

GMSV suggests that the pavement on the Manitoba side of the border is intact. But to get there via Provincial Road 200, you'd have to blow past an "authorized vehicles only" sign, as well as a road closure sign at the exit from the old Canadian customs area.
Title: Re: Montana Secondary State Highways
Post by: si404 on January 02, 2018, 12:26:33 pm
I've made the changes listed above. Any other changes needed or are we go for activation?
Title: Re: Montana Secondary State Highways
Post by: Duke87 on January 09, 2018, 09:29:25 pm
Looks like all clear to me.
Title: Re: Montana Secondary State Highways
Post by: oscar on January 10, 2018, 12:18:23 am
My few comments have been addressed, so we're good to go as far as I'm concerned.
Title: Re: Montana Secondary State Highways
Post by: si404 on January 10, 2018, 05:53:16 am
Activated (just before the crash)
Title: Re: Montana Secondary State Highways
Post by: oscar on January 11, 2018, 06:40:47 pm
Just one belated tweak -- should the north end of SR 511 be relabeled from MT/SK to *MT/SK, to reflect the permanent closure of that border crossing? I've done that with my local-copy draft route file for SK 34, which connected to SR 511 before the crossing was closed.