Re: [OSM-talk] Selecting cycleways

2009-08-21 Thread Richard Mann
You could also assume byway and track (tracktype=grade1/grade2, at least)
are available for cyclists (neither would be likely to have bicycle access
specified).

Richard

On Tue, Aug 18, 2009 at 9:05 AM, Tobias Knerr o...@tobias-knerr.de wrote:

 Rahkonen Jukka wrote:
  Cartinus wrote:
  You'd want to exclude cycleway=opposite as well, because that is just
  removing the oneway restriction for bicycles.
 
  But isn't it still kind of a cycleway and thus worth making it visible
  on a cyclemap?

 I forgot cycleway=opposite in my first reply, but it really isn't a
 cycleway. Imo, cycleway is a bad choice of key for this, something
 like oneway:bicycle=no would be much more appropriate.
 Unlike cycleway=opposite_lane and cycleway=opposite_track, there isn't
 any road or section of road specifically intended for bicycles, so it
 isn't more of a cycleway than any ordinary road.

 Of course, a cyclemap should still make sure to visibly indicate whether
 an oneway rule applies to bicycles.

 Tobias Knerr

 ___
 talk mailing list
 talk@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Selecting cycleways

2009-08-21 Thread Mike Harris
In England and Wales, byways that are either Restricted Byways (RBs) or
Byways Open to all Traffic (BOATs) may be used by cyclists as of right -
i.e. not merely 'available'.
 
Mike Harris
 


  _  

From: Richard Mann [mailto:richard.mann.westoxf...@googlemail.com] 
Sent: 21 August 2009 08:16
To: talk@openstreetmap.org
Subject: Re: [OSM-talk] Selecting cycleways


You could also assume byway and track (tracktype=grade1/grade2, at least)
are available for cyclists (neither would be likely to have bicycle access
specified).
 
Richard


On Tue, Aug 18, 2009 at 9:05 AM, Tobias Knerr o...@tobias-knerr.de wrote:


Rahkonen Jukka wrote:

 Cartinus wrote:
 You'd want to exclude cycleway=opposite as well, because that is just
 removing the oneway restriction for bicycles.

 But isn't it still kind of a cycleway and thus worth making it visible
 on a cyclemap?


I forgot cycleway=opposite in my first reply, but it really isn't a
cycleway. Imo, cycleway is a bad choice of key for this, something
like oneway:bicycle=no would be much more appropriate.
Unlike cycleway=opposite_lane and cycleway=opposite_track, there isn't
any road or section of road specifically intended for bicycles, so it
isn't more of a cycleway than any ordinary road.

Of course, a cyclemap should still make sure to visibly indicate whether
an oneway rule applies to bicycles.

Tobias Knerr


___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk



___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Selecting cycleways

2009-08-18 Thread Rahkonen Jukka
Cartinus wrote:

On Monday 17 August 2009 16:17:36 Tobias Knerr wrote:
  OR highway is not null AND cycleway is not null

 You might want check for cycleway=no here, there are a few hundreds
of
 them.

 You'd want to exclude cycleway=opposite as well, because that is just
removing 
 the oneway restriction for bicycles.

But isn't it still kind of a cycleway and thus worth making it visible
on a cyclemap?

 -- 
 m.v.g.,
 Cartinus

-Jukka-

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Selecting cycleways

2009-08-18 Thread Tobias Knerr
Rahkonen Jukka wrote:
 Cartinus wrote:
 You'd want to exclude cycleway=opposite as well, because that is just
 removing the oneway restriction for bicycles.

 But isn't it still kind of a cycleway and thus worth making it visible
 on a cyclemap?

I forgot cycleway=opposite in my first reply, but it really isn't a
cycleway. Imo, cycleway is a bad choice of key for this, something
like oneway:bicycle=no would be much more appropriate.
Unlike cycleway=opposite_lane and cycleway=opposite_track, there isn't
any road or section of road specifically intended for bicycles, so it
isn't more of a cycleway than any ordinary road.

Of course, a cyclemap should still make sure to visibly indicate whether
an oneway rule applies to bicycles.

Tobias Knerr

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


[OSM-talk] Selecting cycleways

2009-08-17 Thread Rahkonen Jukka
I would like to render a map that highlights all the cycleways. Could
the tagging 
specialists on the list check if this query would give me what I want 
and correct if there is something wrong or missing?

WHERE highway=cycleway
OR highway=footway AND 
   (bicycle=yes OR bicycle=designated OR bicycle=permissive)
OR highway=path AND 
   (bicycle=yes OR bicycle=designated OR bicycle=permissive)
OR highway=briddleway AND 
   (bicycle=yes OR bicycle=designated OR bicycle=permissive)
OR highway is not null AND cycleway is not null
#I cannot handle cycleway=opposite_lane or left/right thing in 
#rendering yet so I do not care

Should I add also 'OR bicycle=official'?
(With 'cycleway' I mean something like 'A way that can legally be used
for cycling and that 95% of urban people riding 300-3000 km per year
with a bicycle would say well suitable for riding a 5 km distance to
work wearing jeans and having a briefcase on a rack'). 

-Jukka Rahkonen-

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Selecting cycleways

2009-08-17 Thread Martin Koppenhoefer
2009/8/17 Rahkonen Jukka jukka.rahko...@mmmtike.fi:
 I would like to render a map that highlights all the cycleways. Could
 the tagging
 specialists on the list check if this query would give me what I want
 and correct if there is something wrong or missing?

 WHERE highway=cycleway
 OR highway=footway AND
   (bicycle=yes OR bicycle=designated OR bicycle=permissive)
 OR highway=path AND
   (bicycle=yes OR bicycle=designated OR bicycle=permissive)
 OR highway=briddleway AND
   (bicycle=yes OR bicycle=designated OR bicycle=permissive)
 OR highway is not null AND cycleway is not null
 #I cannot handle cycleway=opposite_lane or left/right thing in
 #rendering yet so I do not care

 Should I add also 'OR bicycle=official'?

yes, if you want all of them I'd recommend to (maybe depends on the
area in which you're mapping).
I'd also have a look at tagwatch searching for cycle to see all the
possible variations.

I'm not a programmer but it seems to me that you're missing same
parenthesis, e.g.
where highway=cycleway
or (highway=footway and (x1 or x2 or x3))
or (path and cycleway)
or ...

cheers,
Martin

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Selecting cycleways

2009-08-17 Thread Tobias Knerr
Martin Koppenhoefer wrote:
 2009/8/17 Rahkonen Jukka jukka.rahko...@mmmtike.fi:
 OR highway=briddleway AND

bridleway, but I guess that's just a typo.

   (bicycle=yes OR bicycle=designated OR bicycle=permissive)
 OR highway is not null AND cycleway is not null

You might want check for cycleway=no here, there are a few hundreds of them.

 I'd also have a look at tagwatch searching for cycle to see all the
 possible variations.

I wouldn't do this. Just correct those variations (aka errors) in the
data if you care about them.

 I'm not a programmer but it seems to me that you're missing same
 parenthesis

Assuming AND binds more strongly than OR, the query seems correct.

Tobias Knerr

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Selecting cycleways

2009-08-17 Thread Rahkonen Jukka

 Tobias Knerr wrote:
 
 Martin Koppenhoefer wrote:
 Rahkonen Jukka wrote:
  OR highway=briddleway AND
 
 bridleway, but I guess that's just a typo.
 
(bicycle=yes OR bicycle=designated OR bicycle=permissive) OR 
  highway is not null AND cycleway is not null
 
 You might want check for cycleway=no here, there are a few 
 hundreds of them.
 
  I'd also have a look at tagwatch searching for cycle to 
 see all the 
  possible variations.
 
 I wouldn't do this. Just correct those variations (aka 
 errors) in the data if you care about them.
 
  I'm not a programmer but it seems to me that you're missing same 
  parenthesis
 
 Assuming AND binds more strongly than OR, the query seems correct.
 
 Tobias Knerr

Thanks to both of you. I did not even try to write totally correct SQL,
I can handle it if I understand what variations I must search for. I
believe I have to simplify the final rendering step by creating an own
column to the database to collect the cycleways or otherwise the
on-demand queries are getting too complicated for my WMS server.

-Jukka-


___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Selecting cycleways

2009-08-17 Thread Martin Koppenhoefer
2009/8/17 Tobias Knerr o...@tobias-knerr.de:
 Martin Koppenhoefer wrote:

 I'd also have a look at tagwatch searching for cycle to see all the
 possible variations.

 I wouldn't do this. Just correct those variations (aka errors) in the
 data if you care about them.

I wasn't referring to typos but to some strange tags like byway and
maybe others, that might be interesting for bicycles as well. If you
find some typos it's good to correct them obviously, not to put them
in the query.

cheers,
Martin

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Selecting cycleways

2009-08-17 Thread Cartinus
On Monday 17 August 2009 16:17:36 Tobias Knerr wrote:
  OR highway is not null AND cycleway is not null

 You might want check for cycleway=no here, there are a few hundreds of
 them.

You'd want to exclude cycleway=opposite as well, because that is just removing 
the oneway restriction for bicycles.

-- 
m.v.g.,
Cartinus

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk