Re: [Tagging] Way access mismatch relation route=bicycle

2018-01-18 Thread Shawn K. Quinn
On 01/17/2018 03:45 PM, OSMDoudou wrote: > (B) > > This issue raises the question whether R50 should be tagged as trunk in > the first place. > > The Wiki page [6] refers to notions like "high performance" and road > signs F9. But the road is limited to 70 km/h and there are no F9 signs > on the

Re: [Tagging] Way access mismatch relation route=bicycle

2018-01-18 Thread Paul Johnson
On Wed, Jan 17, 2018 at 3:45 PM, OSMDoudou < 19b350d2-b1b3-4edb-ad96-288ea1238...@gmx.com> wrote: > Hello, > > > > This is a two-fold question in fact. > > > > (A) > > > > Osmose raises error "Way access mismatch relation route=bicycle" [1] on a > segment of the R50 highway [2] [3]. > > > > I'm gu

Re: [Tagging] Way access mismatch relation route=bicycle

2018-01-18 Thread OSMDoudou
I didn't know about that page. It makes sense. Thx. -Original Message- From: "Volker Schmidt" Sent: ‎18-‎01-‎18 09:39 To: "Tag discussion, strategy and related tools" Subject: Re: [Tagging] Way access mismatch relation route=bicycle I suppose Osmose uses the c

Re: [Tagging] Way access mismatch relation route=bicycle

2018-01-18 Thread Volker Schmidt
I suppose Osmose uses the country specific tables in [1] The table for Belgium states that bicycle=no is implicit for "highway=trunk". Hence the short way in question would need to have the additional tag "bicycle=yes" for bicycle routing to pass along that cycle lane. The road signs out there seem