Re: [Talk-us] New United States Bicycle Routes!
Yes, It's the Kentucky Transportation Cabinet. Apparently all state "departments" are officially called "cabinets." Took me at least 2 years to get used to KYTC instead of KYDOT. Kerry -Original Message- From: OSM Volunteer stevea Sent: Friday, October 26, 2018 7:01 PM To: Kerry Irons ; Greg Morgan ; talk-us Subject: Re: [Talk-us] New United States Bicycle Routes! Sorry, I should use the abbreviation of KYTC as Kerry does, not KDOT. SteveA ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] New United States Bicycle Routes!
Sorry, I should use the abbreviation of KYTC as Kerry does, not KDOT. SteveA ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] New United States Bicycle Routes!
"Having little confidence that KDOT got it right, either" is exactly why I didn't change the names: let the locals (cities, counties, local residents/citizens) hash this out as well as KDOT, if KDOT wants to get involved. For whatever reason, I've only seen these serious differences of this magnitude in the state of Kentucky, lest the greater-in-US OSM community suddenly panic that TIGER needs a major boost in fixing. (I mean, let's STAY busy cleaning up TIGER, but let's not panic that it is especially bad). OK, TIGER data are "only fair to poor" in Kentucky. I will say that. I'm not laying blame or pointing fingers, simply observing that entering route data from a state DOT was frequently perplexing given the need to match highway infrastructure of current TIGER data there. SteveA California > On Oct 26, 2018, at 3:48 PM, Kerry Irons wrote: > > We had the same experience in creating a RideWithGPS map and route log for > USBR 21 in KY. There are even places where a given road has two different > spellings; you can tell it's the same road but the name spelling apparently > is not agreed by the locals. You learn to live with it. While you would > think that the KYTC names would be definitive, I have little confidence that > that is true. > > > Kerry ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] New United States Bicycle Routes!
We had the same experience in creating a RideWithGPS map and route log for USBR
21 in KY. There are even places where a given road has two different
spellings; you can tell it's the same road but the name spelling apparently is
not agreed by the locals. You learn to live with it. While you would think
that the KYTC names would be definitive, I have little confidence that that is
true.
Kerry
-Original Message-
From: OSM Volunteer stevea
Sent: Friday, October 26, 2018 6:31 PM
To: talk-us
Cc: Greg Morgan ; Kerry Irons
Subject: Re: [Talk-us] New United States Bicycle Routes!
I have completed a first draft of USBR 21 in Kentucky. This was actually quite
difficult as the TIGER name tags frequently do not match what highway names on
the application from Kentucky's DOT says. I did not change these, I'll leave
that for "locals," but there is a great deal of work to do to change highway
names in OSM in Kentucky, as it appears that counties, cities and KDOT change
names (and segment breaks that make them up) quite a lot in the last 11 years
since TIGER data were entered.
As our wiki says and as is good practice in OSM, Greg's 23 and my 21 data entry
deserve a "double-check review" by another OSM volunteer, and while these are
"green" in our wiki, they are a "light green" until this is completed. Greg,
if you email me off list and agree to double-check 21, I'll do the same to 23.
Others are welcome, of course; email one or both of us if you are interested in
helping.
SteveA
California
> On Oct 26, 2018, at 10:51 AM, OSM Volunteer stevea
> wrote:
>
> Wow, Greg, you are quick. Thank you!
>
> Additionally, (a major reason I'm including Kerry in this missive), I removed
> from OSM segments of Kentucky's USBR 23 which overlapped with ACA's
> Transamerica Trail (TA) "Mammoth Cave Loop." (Now largely superseded by 76
> and 23). These were between Highland Springs ("mid-state") and further north
> to Tanner, where 23 now connects to 76 at a T-intersection. There are many
> reasons why OSM has been deprecating ACA routes in OSM: these are
> proprietary and likely don't belong in OSM first place, and we document in
> our wiki that "over time, these tend to be replaced by USBRs" (among other
> reasons, like that they can get old and drift from updates that ACA can make
> or already has made). Indeed, once again (as in the case of the northern
> segment of 76 in Kentucky replacing Mammoth Caves Loop earlier when 76 was
> approved in Kentucky), this segment of 23 100% overlaps with this ACA route,
> so yet another significant ACA route segment now deleted from OSM (as it is
> USBR now).
>
> Thanks again for your work to enter this, and keep up the great entry I'm
> guessing you are doing with USBR 21.
>
> Steve
>
>> On Oct 26, 2018, at 6:18 AM, Greg Morgan wrote:
>>
>> Kentucky USBR 23 is done.
>> https://www.openstreetmap.org/relation/8843677#map=10/37.4960/-85.4712
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] New United States Bicycle Routes!
I have completed a first draft of USBR 21 in Kentucky. This was actually quite
difficult as the TIGER name tags frequently do not match what highway names on
the application from Kentucky's DOT says. I did not change these, I'll leave
that for "locals," but there is a great deal of work to do to change highway
names in OSM in Kentucky, as it appears that counties, cities and KDOT change
names (and segment breaks that make them up) quite a lot in the last 11 years
since TIGER data were entered.
As our wiki says and as is good practice in OSM, Greg's 23 and my 21 data entry
deserve a "double-check review" by another OSM volunteer, and while these are
"green" in our wiki, they are a "light green" until this is completed. Greg,
if you email me off list and agree to double-check 21, I'll do the same to 23.
Others are welcome, of course; email one or both of us if you are interested in
helping.
SteveA
California
> On Oct 26, 2018, at 10:51 AM, OSM Volunteer stevea
> wrote:
>
> Wow, Greg, you are quick. Thank you!
>
> Additionally, (a major reason I'm including Kerry in this missive), I removed
> from OSM segments of Kentucky's USBR 23 which overlapped with ACA's
> Transamerica Trail (TA) "Mammoth Cave Loop." (Now largely superseded by 76
> and 23). These were between Highland Springs ("mid-state") and further north
> to Tanner, where 23 now connects to 76 at a T-intersection. There are many
> reasons why OSM has been deprecating ACA routes in OSM: these are
> proprietary and likely don't belong in OSM first place, and we document in
> our wiki that "over time, these tend to be replaced by USBRs" (among other
> reasons, like that they can get old and drift from updates that ACA can make
> or already has made). Indeed, once again (as in the case of the northern
> segment of 76 in Kentucky replacing Mammoth Caves Loop earlier when 76 was
> approved in Kentucky), this segment of 23 100% overlaps with this ACA route,
> so yet another significant ACA route segment now deleted from OSM (as it is
> USBR now).
>
> Thanks again for your work to enter this, and keep up the great entry I'm
> guessing you are doing with USBR 21.
>
> Steve
>
>> On Oct 26, 2018, at 6:18 AM, Greg Morgan wrote:
>>
>> Kentucky USBR 23 is done.
>> https://www.openstreetmap.org/relation/8843677#map=10/37.4960/-85.4712
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] New United States Bicycle Routes!
Kentucky USBR 23 is done. https://www.openstreetmap.org/relation/8843677#map=10/37.4960/-85.4712 On Wed, Oct 24, 2018 at 12:30 PM OSM Volunteer stevea < stevea...@softworkers.com> wrote: > AASHTO has completed it's "Autumn 2018 round" of national route numbering > approvals (almost) and there are new USBRs for OSM to map. > > One is already completed (thank you, user:micahcochran!): USBR 15 was > extended from Georgia into Florida to connect to Florida's existing USBR 90. > > In Kentucky, route data for USBR 21 (Georgia also has 21) and USBR 23 > (connecting to Tennessee's 23) are also available. While our WikiProject > (see https://wiki.osm.org/wiki/WikiProject_U.S._Bicycle_Route_System ) > has route data for both of these — PDF maps and turn-by-turn spreadsheets — > the route is not quite yet approved. I have been told by a knowledgable > source that "the AASHTO bureaucrat in charge of preparing the vote didn't > put the (Kentucky) applications in front of the committee. As a result, > the applications were sent to the committee for an email vote, which is not > yet concluded." That's OK. > > So, as is our usual (established for at least the last five years) > process, we can take the sometimes substantial time and effort it takes to > enter these while we wait for this "email vote approval" to complete, while > the route is tagged state=proposed in the meantime. Kentucky's 21 and 23 > are each "seeded" in one southern county, properly tagged, they simply need > completion. If AASHTO's email vote approves these, we remove the > state=proposed tag, whether the route is fully entered into OSM or not. > Let's enter it sooner rather than later! Details on how to do so and links > to route data in the cloud are found at the WikiProject link above. Step > right up, please! > > Thank you for making OSM (and its companion renderer OpenCycleMap, as well > as other great bicycle routing tools) one of the most comprehensive bicycle > routing platforms in the world. Like "E pluribus, unum" in the USA, "Ex > data, multum" in OSM: "From data, much." (Yes, I did just make that up!) > > SteveA > California > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
