Re: [Talk-us] New United States Bicycle Routes!

2018-10-27 Thread OSM Volunteer stevea
Only a couple of minor errors, it's good we double-check one another:  KYTC 
spreadsheet Lines 18/19/20 are a loop that excluded Sand Cave and Cathedral 
Domes in Mammoth Caves National Park, I fixed it so this portion of the route 
is now included in USBR 23.  In Franklin, Spreadsheet line 54 advises 
continuing straight onto KY-73E West Cedar Street (you had a southerly jog onto 
South Main Street, then a quick right onto West Madison Street).  You almost 
had this right, but again, because of some wonky names (and very few ref=* 
tags, both CR  for county-designated roads and KY YYY being frequently 
missing for KYTC-designated roads) I can see how it was easy to miss these 
couple of turns.  I'm pretty sure I have correct this as well, though 
Kentucky's existing TIGER data compared to how KYTC (and locals) "now" name 
these roads indicates a SIGNIFICANT drift in names and ref=* numbering (where 
they even exist at all) in the last 11 years.

If there one single US state which quickly rises (imo) to Priority 1, needing 
IMMEDIATE attention to fix its TIGER data, it is Kentucky.  I revise my 
characterization of these data from yesterday's "fair to poor" to simply "poor."

I probably made similar errors on my entry of USBR 21 in Kentucky, including a 
road/rail-undercrossing I'm still not sure truly exists!

If you are reading this and live/work in Knox County, Warren County and/or the 
City of Franklin in Kentucky, OSM sure could use a "triple-check" of these 
data, or even a comprehensive effort at statewide TIGER Review with state- and 
county-level road naming/numbering authorities.  Thank you in advance!

SteveA
California

> On Oct 27, 2018, at 2:30 PM, OSM Volunteer stevea  
> wrote:
> 
> Thanks, Greg, I'm now "double-check reviewing" USBR 23 in Kentucky.  Thanks 
> for your reciprocity on 21 (when/as you get your 'net back, of course).
> 
> SteveA
> California
> 
>> On Oct 27, 2018, at 11:38 AM, Greg Morgan  wrote:
>> 
>> I will be happy to review your implementation of the route. A second pass is 
>> always good for these turn by turn routes. It will have to wait until later 
>> in the day. I have an internet outage right now. 
> 


___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] New United States Bicycle Routes!

2018-10-27 Thread OSM Volunteer stevea
Thanks, Greg, I'm now "double-check reviewing" USBR 23 in Kentucky.  Thanks for 
your reciprocity on 21 (when/as you get your 'net back, of course).

SteveA
California

> On Oct 27, 2018, at 11:38 AM, Greg Morgan  wrote:
> 
> I will be happy to review your implementation of the route. A second pass is 
> always good for these turn by turn routes. It will have to wait until later 
> in the day. I have an internet outage right now. 

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] New United States Bicycle Routes!

2018-10-27 Thread Greg Morgan
I will be happy to review your implementation of the route. A second pass
is always good for these turn by turn routes. It will have to wait until
later in the day. I have an internet outage right now.

I found Kentucky surprising when I have gone to visit. I am used to the
open road of the western states. Barrow pits on either side of the road are
used to build the road bed. In Kentucky it is very common to have a
gigantic tree at the edge of the road...well the minor roads. As I recall
all the roads leading into Lexington form spokes to a hub. These roads were
the horse trails to the tobacco markets. The roads in Kentucky have a very
different feel.

I will check both routes to the latest version of tiger data. I am not sure
that will help. As far as I know, the city, county, and states feed their
data to the census. If the data isn't that good to begin with or there has
been rapid changes, then you are going to run into the issues that you
describe. I have had to search for key roads in a number of states to
complete various USBRs. Kentucky also feels different because the counties
are the driving governments as I recall. If counties do not have thousands
and thousands of dollars for ESRI software to maintain the data, then you
will have these issues.

I also found some areas of poverty remarkable. The anti-importers want to
write studies that the Tiger import killed the community when in fact the
real issue is that we do not have the same density of mappers as some
locations in Europe. In the case of Kentucky parts of it are so rural that
a person is lucky to have phone service. Adding information to OSM is a
leisure class activity of time and resources.  I remember fields and fields
of tabacco crops years ago. The same areas have no cash crops.

I am not alarmed at the condition of Tiger data in Kentucky especially when
you consider parts of the state.


On Fri, Oct 26, 2018, 3:31 PM OSM Volunteer stevea <
stevea...@softworkers.com> wrote:

> 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 <
> stevea...@softworkers.com> 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


[Talk-us] weeklyOSM #431 2018-10-16-2018-10-22

2018-10-27 Thread weeklyteam
The weekly round-up of OSM news, issue # 431,
is now available online in English, giving as always a summary of all things 
happening in the openstreetmap world:

http://www.weeklyosm.eu/en/archives/10846/

Enjoy!

weeklyOSM? 
who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us