Author Topic: Oregon fixes, 1-200  (Read 222 times)

0 Members and 1 Guest are viewing this topic.

Offline Bickendan

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 274
  • Last Login:Today at 04:52:26 am
Oregon fixes, 1-200
« on: April 27, 2019, 08:23:01 am »
Select Named Freeways set:
Delta Highway -> (Lane County) CR 1740
Add Lane County CR 1850 E 30th Ave?
Add Lane County CR 1994 Bob Straub Pkwy?
Add NE Airport Way (PDX - I-205)?
·Hunch says no to CR 1850 and 1994, but maybe on Airport Way.

Interstate set: No changes needed as its completely reliant on exit numbers.
Auxiliary Interstate set: Not applicable
US set:
·US 20
Newport-Corvallis Hwy, Corvallis-Albany Hwy, Santiam Hwy, McKenzie-Bend Hwy, Central Oregon Hwy
--OR451 -> ORH451, pending verification that route is signed.

·US 26
Sunset Hwy, Mt Hood Hwy, Warm Springs Hwy, Madras-Prineville Hwy, Ochoco Hwy, John Day Hwy
--OR173 -> ORH173, pending verification that route is signed.
--OR361 -> ORH361, pending verification that route is signed.

·US 97
Sherman Hwy, The Dalles-California Hwy
--OR422 -> ORH422, pending verification that route is signed.
--OR361_S -> ORH361_S, pending verification that route is signed.
--OR361_N -> ORH361_N, pending verification that route is signed.

·US 101
Oregon Coast Hwy
--OR255 -> ORH255, pending verification that route is signed. (OR255 requires heavy modification as is)
--OR251 -> ORH251, pending verification that route is signed.
--OR250 -> ORH250, pending verification that route is signed.
--OR540 -> ORH240, pending verification that route is signed.
--OR104S -> ORH485, pending verification that route is signed.

·US 199
Redwood Hwy
--OR260 -> ORH 260, pending verification that route is signed.

Oregon Routes set:
·OR 8
--Add major names to .csv? If so:
SW Gales Creek Rd, Pacific Ave, Tualatin Valley Hwy, SW Canyon Rd
--SW234th Ave -> SE Century Blvd. Preserve old tag because Hillsboro switched the street name.
--SWCorPassRd -> SE CorPassRd. Preserve old tag because Hillsboro switched the cardinal prefix.
--OR141 -> SWHallBlvd. Preserve old tag if not merged with Watson Ave couplet.
(Arguably, the Watson Ave and Hall Blvd points should be rolled into one because they're a one-way couplet. List break if so.)
---Note: Even if '141' were still used, it'd have to be ORH141; 141 not signed, no evidence of it being north of Progress anyway.
--ORP217 -> OR217. Yeah, I'm just gonna break a .list or 9 with this fix. I don't want to preserve an outright error.
--CanLn -> SWCanLn for prefix use consistency (Forest Grove tags don't use prefixes).

·OR 10
SW Farmington Rd, SW Beaverton-Hillsdale Hwy
--Add cardinal prefixes to all non-numbered streets?
--WatAve/OR141: See OR 8 above.
--LomAVe -> (SW)LomAve

·OR 18
Salmon River Hwy
--OR18S -> ORH39Y, pending verification that 18S is not signed. Preserve tag and blame ODOT.

·OR 18S
Three Mile Lane
--Verify if Route is signed. If not, convert to ORH 39Y and pull from main set.

·OR 22
Three Rivers Hwy, Willamina-Salem Hwy, North Santiam Hwy
--25(OR18) -> OR18(25). Inconsistent with every other overlap tag in Oregon.
--JosSt -> 6 (if exit number posted; should be); CR854 (if exit number not posted).
--FerRidRd -> CR82
--OldMehRd -> CR31_W
--FirGroLn -> CR3417/3418 or outright remove point.
--KinLn -> Outright remove.
--Add point CR31
--FerRd -> CR31_E
--NForkRd -> CR84
--PionRd -> Outright remove.
--NiaForRd -> NiaRd
--FR2266 -> Outright remove.
--BigMeaRd -> Remove.

·OR 34
Alsea Hwy, Corvallis-Lebanon Hwy
--OldOR34 -> ORH210. Preserve tag.

·OR 36
Mapleton-Junction City Hwy
--OR200_S -> ORH200_S or TerHwy_S. ODOT's trying to offload OR 200 onto Lane County and has never been signed, probably never will be. Preserve point.
--OR200_N -> ORH200_N or TerHwy_N. ODOT's trying to offload OR 200 onto Lane County and has never been signed, probably never will be. Preserve point.

·OR 42
Coos Bay-Roseburg Hwy
--OR542 -> ORH542, pending verification that route is signed.

·OR 52
Payette Spur
--Add BoatLanRd point at Boat Landing Rd.

·OR 58
Willamette Hwy
--OR429 -> ORH429, pending verification that route is signed.

·OR 66
Green Springs Hwy
--OR273 -> ORH273, pending verification that route is signed.

·OR 82
Wallowa Lake Hwy
--OR350/351 -> ORH350/351, pending verification that routes are signed.

·OR 86
Baker-Copperfield Hwy
--Truncate route from OR 7 to I-84?
--OR86S -> ORH481, pending verification that route is signed.
--OR414 -> ORH414, pending verification that route is signed.

·OR 86S
Halfway Spur
--Verify if Route is signed. If not, convert to ORH 481 and pull from main set.
--OR413/414 -> ORH413/414, pending verification that routes are signed.

·OR 99
Pacific Hwy West, Goshen-Divide Hwy, Drain-Yoncalla Hwy, Oakland-Shady Hwy, Dillard Hwy, Rogue River Hwy, Rogue Valley Hwy
--ODOT's trying to drop portions of OR 99 (Pacific Hwy West) to Eugene, taking Northwest Expressway and Delta Highway in exchange. Considering Drain-Yoncalla Hwy, Oakland-Shady Hwy, and Dillard Hwy aren't ODOT maintained but OR 99 shields are noted from I-5, this is likely a non-issue. 

·OR 99E
Pacific Hwy East, Albany-Junction City Hwy
--'Added' -> CR526. Don't wanna know how I messed that one up; not preserving.
--Add point ConRd at Concord Rd.
--Add point BybBlvd at Bybee Blvd.
--Add point DekSt at Dekum St. Justifying this one: TriMet Line 8 turns on/off MLK Blvd here for Clinch-By-Bus.

·OR 99W
Pacific Hwy West
--The perennieal question on whether OR 99W ends at I-5(294) or does it continue along Barbur Blvd and Intersate Ave remains.
--OR200 -> ORH200 or TerHwy. See note on OR 36.
--RicRd -> OR223, pending verification -- unclear if sign from OR 99W is OR 223 or To OR 223.
--OR51/194 -> OR51/ORH194, pending verification.
--OR153_E -> ORH153_E, pending verification.
--OR153_W -> ORH153_W, pending verification.

·OR 104
Fort Stevens Hwy
--OR104S -> ORH485, pending verification.

·OR 104S
Fort Stevens Spur
--Verify if Route is signed. If not, convert to ORH 485 and pull from main set.

·OR 120
Swift Hwy (N Portland Rd, N Marine Dr)
--Verify if Route is signed. If not, convert to ORH 120 and pull from main set.

·OR 126
Florence-Eugene Hwy, Eugene-Springfield Freeway, McKenzie Hwy, Belknap Springs Hwy, McKenzie Hwy, Ochoco Hwy
--OR200 -> ORH200 or TerHwy. See note on OR 36.
--OR370 -> ORH370 pending verification.

·OR 126 Bus
McKenzie Hwy
--OR222 -> ORH222? 42ndSt? ODOT's trying to dump 222... eh, 'Pending verification'.

·OR 131
Netarts Hwy
--Add point HillSt at Hillsdale St.

·OR 138
Elkton-Sutherlin Hwy, North Umpqua Hwy
--129 -> I-5(129)

·OR 138S
Elkton-Sutherlin Hwy
--OSM shows OR 138S from I-5 to OR 99 in Sutherlin. Needs verification, especially as it also reports OR 18S and 157 in McMinnville, OR 105 and 105S in Warrenton, and OR 155 in Lafayette.
18S is 39Y, and 155 is part of OR 233; 105 is mostly US 101 Bus. 157 outright doesn't exist.

·OR 141
Beaverton-Tualatin Hwy (SW Hall Blvd, SW Durham Rd, SW 72nd Ave, SW Boones Ferry Rd)
--Drop route from main set. It can live in the ORH set if that ever gets made. OR 141 -> ORH 141.

·OR 153, 154, 164, 173, 180, 194, 200
Bellvue-Hopewell Hwy; Lafayette Hwy; Jefferson Hwy; Timberline Hwy; Eddyville-Blodget Hwy; Monmouth Hwy; Territorial Hwy
--Verify if Routes are signed. If not, convert to respective ORH (same as route numbers) and pull from main set.
--OR 180: CreCreLp -> CryCreLp. Made the same mistake with US 20 and forgot to fix it here.
--OR 200: Route and Hwy will eventually be completely deleted.

OR 201-569 forthcoming.
Note: The southernmost portion of OR/H 454 straddles the OR/ID border. An ID OR/ORH454 will be needed on this segment.
« Last Edit: April 27, 2019, 08:34:06 am by Bickendan »

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1604
  • Last Login:Yesterday at 04:02:24 pm
Re: Oregon fixes, 1-200
« Reply #1 on: April 28, 2019, 02:46:05 am »
This might also be checked and fixed: http://travelmapping.net/devel/datacheck.php?rg=OR

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 661
  • Gender: Male
  • Last Login:Today at 05:16:08 am
Re: Oregon fixes, 1-200
« Reply #2 on: April 28, 2019, 04:44:14 am »
·OR 99W
--OR51/194 -> OR51/ORH194, pending verification.

OR51 or stays as is.  We don't add additional route 'network types' into the labels (might even get flagged on the datacheck page, but not sure).  I personally don't like mixing different routes types in labels (without the network types), but it has to be done sometimes.

Offline Bickendan

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 274
  • Last Login:Today at 04:52:26 am
Re: Oregon fixes, 1-200
« Reply #3 on: April 28, 2019, 06:52:05 am »
This might also be checked and fixed: http://travelmapping.net/devel/datacheck.php?rg=OR
Run the hidden junction ones by me so I know what to look for if corrections are needed.
OR 18's +x1(OR233) should be the same as OR 233's +x1(OR18)
OR 19's +x8(OR208) should be the same as OR 208's +x1(OR19)
OR 22's +x1(OR99EBus) should the same as OR 99E Bus Sal's +x1(OR22)

OR 39 is a false positive. I'll need to make that entry on the FP .csv.
OR 99's sharp angles is a FP (transition from Franklin Blvd to I-5 at OR 58).
OR 207's sharp angles will be addressed in the 200-569 block.

·OR 99W
--OR51/194 -> OR51/ORH194, pending verification.

OR51 or stays as is.  We don't add additional route 'network types' into the labels (might even get flagged on the datacheck page, but not sure).  I personally don't like mixing different routes types in labels (without the network types), but it has to be done sometimes.
Blah, I abhor not including the different network types, but I'll leave it as OR51/194. That'll eliminate the need to also fix the OR 51 file. And maybe I'll get lucky and find that 194 finally got posted in the field, rendering the entire point moot.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1604
  • Last Login:Yesterday at 04:02:24 pm
Re: Oregon fixes, 1-200
« Reply #4 on: April 28, 2019, 07:39:03 am »
·OR 99W
--OR51/194 -> OR51/ORH194, pending verification.

OR51 or stays as is.  We don't add additional route 'network types' into the labels (might even get flagged on the datacheck page, but not sure).  I personally don't like mixing different routes types in labels (without the network types), but it has to be done sometimes.
Blah, I abhor not including the different network types, but I'll leave it as OR51/194. That'll eliminate the need to also fix the OR 51 file. And maybe I'll get lucky and find that 194 finally got posted in the field, rendering the entire point moot.

I think that it should definitely stay as-is: OR51/194.