Re: [Talk-us] Bicycle infrastructure

[Marc Gemis]

Do you know this
http://mijndev.openstreetmap.nl/~ligfietser/fiets/index.html?map=cycleways
map ? It shows a lot of cycleway tags, including surfaces, cycleway
routes and common mapping mistakes. There is nothing about shoulders,
but I'm pretty sure that you ask to include them (on the Dutch forum),
they will get added.

The website is OverPass driven

regards

m.

On Wed, Oct 4, 2017 at 8:26 PM, Martijn van Exel  wrote:
> Hi all,
>
> I am holding a bike mapping party for our local OSM group this Thursday. We
> want to complete the bicycle infrastructure of Utah. I designed this
> Overpass query: http://overpass-turbo.eu/s/s99 to extract most of the
> bicycle data. Now I have two questions:
>
> 1) Do you see any improvements I should make to this query / am I missing
> important features?
> 2) How can I best use this result for my bike mapping party?
>
> Any help appreciated! If you're in the area, please stop by:
> https://www.meetup.com/OpenStreetMap-Utah/events/243371717/
>
> If you don't want to click, this is the query at the time of writing:
>
> area[name="Utah"]->.a;
> (
>   node[amenity=bicycle_rental](area.a);
>   node[amenity=bicycle_parking](area.a);
>   way[highway=cycleway](area.a);
>   way[cycleway](area.a);
>   way["cycleway:right"](area.a);
>   way["cycleway:left"](area.a);
>   way[bicycle=yes][highway!=motorway](area.a);
>   way[bicycle=designated](area.a);
> );
> out meta;
>>;
> out skel qt;
>
> Martijn
>
>
> ___
> 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

[Talk-us] Someone copying from other maps

[GeoKitten]

Hello everyone. A few days ago, an OSM user in my ares (Pittsburgh, PA) sent me
a private message in which they admitted to copying from two sources. First
they said they were copying from a map of the CSX intermodal facility in
Pittsburgh:
"The challenging part was the CSX Intermodal facility. I took the PDF from
their public documents on their website and extracted the engineering plan
image, then used the PicLayers plugin to scale and orient that image
accurately, then traced from that. I'm a little proud of that one."

Presumably this map is copyrighted so it's a serious issue.

They also said they were copying from the county address data:

"It's also a lot faster with the address points from the county overlaid
(remangled through osmfilter, pull it out per municipality, and then rewrite
the tags and values into OSM-appropriate format), and with some of the JOSM
alignment tricks."

This is a government dataset that is probably public domain but whose copyright
status hasn't been verified. It might be considered an unauthorized import
though.

I'm not sure how to handle this. First of all, this was via PM so I'm not sure
if I should reveal their identiy. Should I?

Second, I want to clarify that they don't appear malicious, just uninformed
of the rules. They mentioned their copying in a positive context as if they
didn't know it was forbidden. I don't want to be a snitch but I know the OSM
community takes copyright issues very seriously.___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Bicycle infrastructure

[Denis Carriere]

For anyone interested, our local Cycling + OSM community is currently
working on an OSM Bike Ottawa Tagging Guide.

https://github.com/osmottawa/OSM-Bike-Ottawa-Tagging-Guide

It mentions features like sharrows & bicycle shared lanes with in-depth
photos using Mapillary.

For any avid OSM cyclist, we would definitely welcome some feedback using
the GitHub issues.

Happy cycling!

Cheers,


*~~*
*@DenisCarriere*
*GIS Software & Systems Specialist*

On Wed, Oct 4, 2017 at 5:46 PM, OSM Volunteer stevea <
stevea...@softworkers.com> wrote:

> Martijn and this thread's contributors:
>
> Yes to everything!  Thanks for the OT snippet, that's helpful and benefits
> from additional suggestions like sharrows as cycleway=shared_lane,
> cycleway=buffered_lane, and importantly, shoulder and surface data.
>
> While infrastructure is important (critical, in fact), please also include
>
>   relation[route=bicycle](area.a);
>
> in that OT query, if you might.  (Or, perhaps as a separate query with the
> same area[name="Utah"]->.a; enveloping it).  Important things to check on
> in those results would be if the members of such relations contain
> exclusively bicycle infrastructure, and if not, tagging the member elements
> properly so they do.  And, check the relation tags so they are sensible and
> in correct networks (lcn, rcn, ncn).  Please read wiki docs if it isn't
> clear, but note that mountain bike routes (route=mtb, of which I'm sure
> Utah has many) are different than route=bicycle.  Please assure such routes
> are tagged accordingly.
>
> GO Utah bicycling, and find out how taking OSM with you (on your
> smartphone or GPS as a map or route, for example) is awesome!
>
> 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

Re: [Talk-us] Bicycle infrastructure

[Harald Kliems]

On Wed, Oct 4, 2017 at 4:23 PM Richard Fairhurst 
wrote:

> Shoulder information is good, especially on rural roads. A simple
> shoulder=yes/no suffices. https://wiki.openstreetmap.org/wiki/Key:shoulder

Yes to adding shoulder info! You may be talking specifically about
Martijn's query, but I just want to emphasize that surface information for
shoulders IMHO is crucial for biking. In my experience (NY, QC, ON, WI,
IL), an unpaved shoulder is of not much use for biking.

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

Re: [Talk-us] Bicycle infrastructure

[OSM Volunteer stevea]

Martijn and this thread's contributors:

Yes to everything!  Thanks for the OT snippet, that's helpful and benefits from 
additional suggestions like sharrows as cycleway=shared_lane, 
cycleway=buffered_lane, and importantly, shoulder and surface data.

While infrastructure is important (critical, in fact), please also include 

  relation[route=bicycle](area.a);

in that OT query, if you might.  (Or, perhaps as a separate query with the same 
area[name="Utah"]->.a; enveloping it).  Important things to check on in those 
results would be if the members of such relations contain exclusively bicycle 
infrastructure, and if not, tagging the member elements properly so they do.  
And, check the relation tags so they are sensible and in correct networks (lcn, 
rcn, ncn).  Please read wiki docs if it isn't clear, but note that mountain 
bike routes (route=mtb, of which I'm sure Utah has many) are different than 
route=bicycle.  Please assure such routes are tagged accordingly.

GO Utah bicycling, and find out how taking OSM with you (on your smartphone or 
GPS as a map or route, for example) is awesome!

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

Re: [Talk-us] Bicycle infrastructure

[Richard Fairhurst]

Martijn van Exel wrote:
> Do you see any improvements I should make to this query / am I missing
> important features?

Shoulder information is good, especially on rural roads. A simple
shoulder=yes/no suffices. https://wiki.openstreetmap.org/wiki/Key:shoulder

Surface information is good on rural roads too but I might have banged that
drum one or 2,000 times before.

Looking forward to seeing the result - I'll hold off the next cycle.travel
North America update until you're done!

cheers
Richard



--
Sent from: http://gis.19327.n8.nabble.com/USA-f5284732.html

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

Re: [Talk-us] Bicycle infrastructure

[Alan Richards]

There's also a whole bunch of bike related tags here:
https://github.com/osmottawa/OSM-Bike-Ottawa-Tagging-Guide

On Wed, Oct 4, 2017 at 12:10 PM, Spencer Gardner 
wrote:

> You'll probably want to include cycleway=buffered_lane as well. It's
> undocumented but used pretty frequently in some places. PeopleForBikes has
> published a list of OSM tags they use in their Bike Network Analysis tool
> (disclosure: I worked on this project). You can download the list here:
> https://s3.amazonaws.com/pfb-public-documents/OSM.Tags.xlsx
>
> You might also find some other useful resources via the methodology page:
> https://bna.peopleforbikes.org/#/methodology
>
> On Wed, Oct 4, 2017 at 1:38 PM, Mike N  wrote:
>
>> I'm not sure about the syntax, but there's
>>
>>   cycleway=shared_lane   (for sharrows)
>>
>> ___
>> 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
>
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Bicycle infrastructure

[Spencer Gardner]

You'll probably want to include cycleway=buffered_lane as well. It's
undocumented but used pretty frequently in some places. PeopleForBikes has
published a list of OSM tags they use in their Bike Network Analysis tool
(disclosure: I worked on this project). You can download the list here:
https://s3.amazonaws.com/pfb-public-documents/OSM.Tags.xlsx

You might also find some other useful resources via the methodology page:
https://bna.peopleforbikes.org/#/methodology

On Wed, Oct 4, 2017 at 1:38 PM, Mike N  wrote:

> I'm not sure about the syntax, but there's
>
>   cycleway=shared_lane   (for sharrows)
>
> ___
> 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

Re: [Talk-us] Bicycle infrastructure

[Mike N]

I'm not sure about the syntax, but there's

  cycleway=shared_lane   (for sharrows)

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

Re: [Talk-us] Bicycle infrastructure

[Martijn van Exel]

I also exported the data to geojson.io:
http://bl.ocks.org/anonymous/raw/77da9f9103fcbf5c8382a316b7f22ef5/

Martijn

On Wed, Oct 4, 2017 at 12:26 PM, Martijn van Exel  wrote:

> Hi all,
>
> I am holding a bike mapping party for our local OSM group this Thursday.
> We want to complete the bicycle infrastructure of Utah. I designed this
> Overpass query: http://overpass-turbo.eu/s/s99 to extract most of the
> bicycle data. Now I have two questions:
>
> 1) Do you see any improvements I should make to this query / am I missing
> important features?
> 2) How can I best use this result for my bike mapping party?
>
> Any help appreciated! If you're in the area, please stop by:
> https://www.meetup.com/OpenStreetMap-Utah/events/243371717/
>
> If you don't want to click, this is the query at the time of writing:
>
> area[name="Utah"]->.a;
> (
>   node[amenity=bicycle_rental](area.a);
>   node[amenity=bicycle_parking](area.a);
>   way[highway=cycleway](area.a);
>   way[cycleway](area.a);
>   way["cycleway:right"](area.a);
>   way["cycleway:left"](area.a);
>   way[bicycle=yes][highway!=motorway](area.a);
>   way[bicycle=designated](area.a);
> );
> out meta;
> >;
> out skel qt;
>
> Martijn
>
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us