Recent Posts

Pages: 1 [2] 3 4 ... 10
11
In-progress Highway Systems & Work / Re: yakra's collaborator thread
« Last post by yakra on Yesterday at 11:30:36 pm »
grep-o-roonie
inna United States stylee

1. Potential malformed city suffixes, including directional
grep '^[A-Z][A-Z][0-9]\{1,3\}[A-Z][a-z][a-z]_[NEWS]' */*/*.wpt | grep -v '[A-Z][A-Z][0-9]\{1,3\}Alt_[NEWS]\|[A-Z][A-Z][0-9]\{1,3\}Bus_[NEWS]\|[A-Z][A-Z][0-9]\{1,3\}Byp_[NEWS]\|[A-Z][A-Z][0-9]\{1,3\}Trk_[NEWS]\|[A-Z][A-Z][0-9]\{1,3\}His_[NEWS]\|[A-Z][A-Z][0-9]\{1,3\}Spr_[NEWS]\|[A-Z][A-Z][0-9]\{1,3\}Con_[NEWS]'

2. Potential malformed city suffixes, more complete list
grep '^[A-Z][A-Z][0-9]\{1,3\}[A-Z][a-z][a-z]' */*/*.wpt | grep -v '[A-Z][A-Z][0-9]\{1,3\}Alt\|[A-Z][A-Z][0-9]\{1,3\}Bus\|[A-Z][A-Z][0-9]\{1,3\}Byp\|[A-Z][A-Z][0-9]\{1,3\}Trk\|[A-Z][A-Z][0-9]\{1,3\}His\|[A-Z][A-Z][0-9]\{1,3\}Spr\|[A-Z][A-Z][0-9]\{1,3\}Con'

3. "Good Alabama"
grep _ AL/*/*.wpt | grep -v '_[NEWS] '

4. "Bad Maine"
grep 'US[0-9]\{1,3\}Alt.\+ ' ME/*/*.wpt | grep -v 'US[0-9]\{1,3\}Alt_[NEWS] '

5. 4-character LONG_UNDERSCORE datacheck
grep -i '_[A-Z]\{3\}[abcdfghijklmopqrtuvxyz] ' */*/*.wpt

6. Old highway designation labels that may have a current visible name
grep '^Old..[0-9]' */*/*.wpt
This one will have a lot of false positives.
12
Updates to Highway Data / Re: MT US 310: north end
« Last post by yakra on Yesterday at 10:34:55 pm »
Sounds reasonable.
13
In-progress Highway Systems & Work / Re: yakra's collaborator thread
« Last post by yakra on Yesterday at 08:59:32 pm »
Operation Directional Prefix

Code: [Select]
Region Results Command
-----------------------------------------------------------------------------------------------------------------------------------
CT 34 grep -v '^NY/CT\|^CT/NY' CT/*/*.wpt | grep '[NEWS][A-Z]\|[NS][EW][A-Z]'
KS 12 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' KS/*/*.wpt | grep -v '[NS][EW][0-9]\|[NEWS]Rd'
MA 19 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' MA/*/*.wpt | grep -v NY/MA
ME 136 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' ME/*/*.wpt | grep -v NH/ME
NE 40 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' NE/*/*.wpt | grep -v 'NE[0-9]\+[A-Z]\?[ _/]\|NE/[A-Z][A-Z] \|[A-Z][A-Z]/NE '
NH 57 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' NH/*/*.wpt | grep -v 'NH[0-9]\|NH/[A-Z][A-Z] '
NJ 45 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' NJ/*/*.wpt | grep -v 'NJ[0-9]\|NJ/[A-Z][A-Z] \|[A-Z][A-Z]/NJ \|NJTpk '
NY 192 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' NY/*/*.wpt | grep -v 'NY[0-9]\|NY/[A-Z][A-Z] \|[A-Z][A-Z]/NY '
OK 8 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' OK/*/*.wpt | grep -v 'NM/OK'
RI 9 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' RI/*/*.wpt
TX 27 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' TX/*/*.wpt | grep -v 'NM/TX\|[WE]End\|NASA\|[0-9]\{4\} '
AB 2 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' AB/*/*.wpt | grep -v 'SK[0-9]\{1,3\} \|SK/AB \|NT/AB '
MB 19 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' MB/*/*.wpt | grep -v '[NS]./MB '
NB 30 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' NB/*/*.wpt | grep -v 'NB[0-9]\|N./[A-Z][A-Z] '
NS 44 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' NS/*/*.wpt | grep -v 'NS[0-9]\|NB/NS'
PE 2 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' PE/*/*.wpt | grep -v NB/PE
NL 2 grep '^[NEWS][A-Z]\|^[NS][EW][A-Z]' NL/*/*.wpt | grep -v 'NL[0-9]'
14
Other Discussion / Re: Distinguish more between traveled and non-traveled routes
« Last post by oscar on Yesterday at 08:14:19 pm »
Perhaps there could be a "drawing style" drop-down menu with a few options:
-Full (as it is now)
-Full Inverse (michih's idea, everything but with inverted opacity)
-Clinched Only (clinched segments as now, no unclinched segments)
-Unclinched Only (no clinched segments, unclinched segments more opaque than in Full but not as opaque as clinched segments in Full or Clinched Only)
I support this.

Same here. I especially like the fourth option, which would help me find unclinched segments in a sea of clinched routes.
15
Perhaps there could be a "drawing style" drop-down menu with a few options:
-Full (as it is now)
-Full Inverse (michih's idea, everything but with inverted opacity)
-Clinched Only (clinched segments as now, no unclinched segments)
-Unclinched Only (no clinched segments, unclinched segments more opaque than in Full but not as opaque as clinched segments in Full or Clinched Only)
I support this.
16
Updates to Highway Data / Re: MT US 310: north end
« Last post by the_spui_ninja on Yesterday at 05:38:56 pm »
If no one else has a problem with this, I'll go ahead and make the change. It seems pretty reasonable.
17
US 41 and SR 3: GA3ConMan -> GA3ConMar
US 41 and SR 3: requesting a point at http://www.openstreetmap.org/?lat=33.88871&lon=-84.47428 for WinRidPkwy
SR 120: requesting a point at http://www.openstreetmap.org/?lat=33.969417&lon=-84.489090 for ELakePkwy (I turned off onto Robinson Road, but that name is ambiguous since it returns to SR 120)
18
Starting with SC 34:

SC 34:
1.  CamAve should be CouFarmRd (County Farm Rd).
2.  EddRd should be EddyRd.
3.  BucPlaRd should be for Scurry Church Rd (ScuChuRd).
4.  +X003 could be replaced easily with a visible point at Glenn St (GleSt) (minus .08 miles in mileage).
5.  I would add a point at Jackson Creek Rd (JacCreRd) as the route is close to leaving tolerance just east of here.
6.  +X004(US321) should be replaced with a visible point at Moultrie St (MouSt).  (also affects US 321)
7.  I did not see shields indicating to use US21Con to get to US 21 SB and vice versa to SC 34 WB from US 21 NB.
8.  The SmaRd point needs to be recentered.
9.  +X006 could easily be replaced with a visible point at Gettys Rd (GetRd).
10.  US521/601Trk should be US521Trk/601Trk.  (could affect US 1 and US 601, I doubt it would affect the truck routes.)
11.  US521/601_N should be US521/601.  (US521/601_N should be US521/601 on US 1 as well.  US601/1_S should be US1/601 on US 521.  I would change US1_N to US1/521 on US 601 even though the former is technically correct.)
12.  EYorSt should just be YorkSt.
13.  AntSt should be AntRd (Antioch Rd).
14.  JohPonRd should be JohPondRd.
15.  SC 151 seems to be posted up to US401Con.  (I may relook at this at SC 151, but it would save a few minutes to check this out now.)
16.  The US52Bus point needs to be synced with US 52 BUS (Darlington).
17.  SocHilRd should be SocHillRd.
18.  I would add a point at Arcadia Rd (ArcRd) (shown as River Rd on the SCDOT Street Finder) due to the 9.35 miles between GeoRd and SC38.
19.  HooRd should be HoodRd.
20.  +X009 should be replaced with a visible point at Pelt Rd (verified via SCDOT Street Finder).
21.  The 9thAve point could be easily removed (losing .07 miles of mileage).  You could also replace it with a point at MLK, Jr.  Blvd.
 
SC 34 TRUCK (Camden):
1.  YorkSt should be YorkSt_E.  (affects US 1 TRUCK (East Camden) and US 521 TRUCK (East Camden)
2.  All 3 truck routes need to be synced with US 521 at the southern end.  That label on US 521 should be changed from US1/521Trk to US1Trk/521Trk.
3.  US 1 TRUCK (East Camden) is posted on US 521 NB at the southern end of US 521 TRUCK (Camden).

SC 34 TRUCK (Darlington):
1.  US52Bus_S should be US52_S. (I would have thought that it would have been US52_E, but US 52 seems to be posted N-S here.)
2.  SChaRd should be ChaRd_S.
3.  A point should be added at Pocket Rd (PocRd).  (see "TO I-95 shield" near the intersection)

SC 35:
1.  The I-77 point needs to be synced with it.

SC 37:
1.  The US278 point at its southern end needs to be relocated.  This seems to be due to an intersection alignment.  (will also affect US 278)
2.  SpaMosRd should be SpaMossRd.
20
Updates to Highway Data / Re: OR point labels
« Last post by si404 on Yesterday at 03:16:43 pm »
If US101 and US6 were there, that would be US6/101, so no confusion there as I see it.
True. It's never sat right with me to have such labelling though - what if it was US1/6 with the 6 route being a state route?

Bickendan, like me, seems to prefer making any lettered prefix explicit, hence why I was reminding him of that option.
Pages: 1 [2] 3 4 ... 10