Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Updates to Highway Data / OK: I-40 updates
« Last post by rickmastfan67 on Yesterday at 11:54:14 pm »
Missing -> 82A (formerly 81)

< ones below would also have to be adjusted/added in US-270's file >
NEW -> 134 (Frisco Rd)
NEW -> 146 (Portland Ave)
147A -> 147 ? (since 147C is 'closed')
'shaping point' -> 151A ??? There's a shaping point here, but it should be a visible point.
154 -> should this be centered on the overpass here?
22
Updates to Highway Data / OK: OK-351 exit number update
« Last post by rickmastfan67 on Yesterday at 11:26:56 pm »
I-40 -> 56
23
Updates to Highway Data / OK: US-69 exit number updates
« Last post by rickmastfan67 on Yesterday at 11:24:38 pm »
CTreeRd -> 82
NEW -> 89 (Village Blvd)
NEW -> 90 (Peaceable Rd/Comanche Ave)
24
Updates to Highway Data / OK: OK-66 point suggestion
« Last post by rickmastfan67 on Yesterday at 11:09:47 pm »
Recommend a point @ West 96th Street South (just below OK-364), due to the offramp there from I-44, which happens to be the missing ramps from the OK-364 interchange.  This point would also need to be added into 'OK US66HisOkl'.

Also, on I-44:
NEW -> 218A (West 96th Street South)
218 -> 218B
25
Solved Highway data updates / Re: OK: L.L. Tisdale Parkway
« Last post by rickmastfan67 on Yesterday at 11:01:02 pm »
Just noticed, but you missed the partial interchange w/ Fairview Street that's above I-244. ;)

Also, the graph connection with the 'GilExpy' route is missing, thus creating a NMP issue.

Code: [Select]
ok.gilexpy TisPkwy (36.201369,-95.999184) NMP ok.lltispkwy GilExpy (36.201416,-95.999013)
ok.lltispkwy GilExpy (36.201416,-95.999013) NMP ok.gilexpy TisPkwy (36.201369,-95.999184)
26
Updates to Highway Data / MO: US 63 Missing Interchange
« Last post by shiggins on Yesterday at 10:35:21 pm »
US 63 is missing a point at the exit for Discovery Parkway on the south side of Columbia.
27
In-progress Highway Systems & Work / Re: usams: Mississippi State Highways
« Last post by rickmastfan67 on Yesterday at 09:59:04 pm »
Quote from: michih on Yesterday at 04:18:14 pm
MS7:
I-55(206) -> 206(55) see https://travelmapping.net/devel/manual/wayptlabels.php#exitconc_num_on_num
I-55(208) -> 208(55)
I-55(211) -> 211(55)

Ummm, I think you have that wrong.  Those labels are actually correct as-is since MS-7 doesn't use exit numbers itself anywhere.
See: https://travelmapping.net/devel/manual/wayptlabels.php#exitconc_num_on_unnum
28
Other Discussion / Re: Mapping 6+ lane freeways
« Last post by webny99 on Yesterday at 09:21:52 pm »
Quote from: webny99 on December 12, 2024, 11:49:31 am
Also for IA I-80, currently only 240-246 are marked as 6lane, but it should be 237-249.. roughly doubling the marked 6-lane stretch near Iowa City.

Just bumping this as I am unsure who takes care of IA or if there is somewhere else to be reporting this.
29
Updates to Highway Data / Re: KY/AR: New I-169 and I-57!
« Last post by TBKS1 on Yesterday at 04:54:05 pm »
Yeah the BGSs won't be replaced for quite a while, this was literally the first I-57 shield that was installed. I counted four of them when I was driving up and down the frontage road between McCain Boulevard (Exit 1) and Exit 6
30
Updates to Highway Data / Re: QC: A-55 exit number updates
« Last post by oscar on Yesterday at 04:41:10 pm »
https://github.com/TravelMapping/HighwayData/pull/8260
Pages: 1 2 [3] 4 5 ... 10