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

[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 entries and exits of R50, only C19 "No entry for pedestrians" and
> C11 + C9 "No entry for bicycles" + "No entry for mopeds (and mofas)",
> which tend to confirm it's not a trunk.
> 
> I wonder if primary wouldn't be more accurate classification, although
> the Wiki refers to a "highway linking large towns" [7], which is not the
> case here as the highway is a ring around the city not a road between
> cities.
Not sure what the situation is in Belgium, but here in the US a lot of
major city streets get tagged as primary. There are only two local roads
I can think of tagged as trunk in my area: the non-freeway/motorway
section of Texas 249 between Beltway 8 and I-45, and the controlled
access section of Memorial Drive (from Detering to downtown Houston
where it becomes Texas Avenue and Prairie Avenue). There are only a
handful tagged as primary, one of which I upgraded myself even though it
lacks a state/US highway designation (which otherwise seems to be a
requirement by whoever tagged the others).

-- 
Shawn K. Quinn 
http://www.rantroulette.com
http://www.skqrecordquest.com

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

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

[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 guessing it's because the segment is part of relation for a bike route
> but it's tagged as trunk (as the rest of R50), and a trunk would imply a
> restriction for bicycles.
>
>
>
> Although, I see such an implication for motorways [4], I don't see it for
> trunks [5].
>
>
>
> Do you know what causes the access mismatch, because I don't see it from
> the tags ?
>

In such cases, I might be inclined to add bicycle=designated to the ways on
the affected route if they're also a part of a bicycle route.  Kind of a
"really, really" nod to data consumers.
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

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

[OSMDoudou]

I didn't know about that page. It makes sense. Thx.

-Original Message-
From: "Volker Schmidt" <vosc...@gmail.com>
Sent: ‎18-‎01-‎18 09:39
To: "Tag discussion, strategy and related tools" <tagging@openstreetmap.org>
Subject: Re: [Tagging] Way access mismatch relation route=bicycle

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 to be consistent, there are "no-bicycle" sign 
along the ring road, except for this short piece.


Your second point regarding the road classification trunk is a different issue, 
that needs to be discussed with the Belgian community.


[1] https://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions



On 17 January 2018 at 22:45, 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 guessing it's because the segment is part of relation for a bike route but 
it's tagged as trunk (as the rest of R50), and a trunk would imply a 
restriction for bicycles.
 
Although, I see such an implication for motorways [4], I don't see it for 
trunks [5].
 
Do you know what causes the access mismatch, because I don't see it from the 
tags ?
 
(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 entries and 
exits of R50, only C19 "No entry for pedestrians" and C11 + C9 "No entry for 
bicycles" + "No entry for mopeds (and mofas)", which tend to confirm it's not a 
trunk.
 
I wonder if primary wouldn't be more accurate classification, although the Wiki 
refers to a "highway linking large towns" [7], which is not the case here as 
the highway is a ring around the city not a road between cities.
 
What type of road would you qualify the entire R50 ?
 
Thx.
 
[1] http://osmose.openstreetmap.fr/en/error/15216104253
[2] http://www.openstreetmap.org/browse/way/251684307
[3] https://goo.gl/maps/khpwvm8kxQw
[4] https://wiki.openstreetmap.org/wiki/Tag:highway%3Dmotorway
[5] https://wiki.openstreetmap.org/wiki/Trunk
[6] https://wiki.openstreetmap.org/wiki/Road_signs_in_Belgium
[7] https://wiki.openstreetmap.org/wiki/Tag:highway%3Dprimary

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

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

[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 to be consistent, there are "no-bicycle" sign
along the ring road, except for this short piece.

Your second point regarding the road classification trunk is a different
issue, that needs to be discussed with the Belgian community.

[1]
https://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions

On 17 January 2018 at 22:45, 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 guessing it's because the segment is part of relation for a bike route
> but it's tagged as trunk (as the rest of R50), and a trunk would imply a
> restriction for bicycles.
>
>
>
> Although, I see such an implication for motorways [4], I don't see it for
> trunks [5].
>
>
>
> Do you know what causes the access mismatch, because I don't see it from
> the tags ?
>
>
>
> (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
> entries and exits of R50, only C19 "No entry for pedestrians" and C11 + C9
> "No entry for bicycles" + "No entry for mopeds (and mofas)", which tend to
> confirm it's not a trunk.
>
>
>
> I wonder if primary wouldn't be more accurate classification, although the
> Wiki refers to a "highway linking large towns" [7], which is not the case
> here as the highway is a ring around the city not a road between cities.
>
>
>
> What type of road would you qualify the entire R50 ?
>
>
>
> Thx.
>
>
>
> [1] http://osmose.openstreetmap.fr/en/error/15216104253
>
> [2] http://www.openstreetmap.org/browse/way/251684307
>
> [3] https://goo.gl/maps/khpwvm8kxQw
>
> [4] https://wiki.openstreetmap.org/wiki/Tag:highway%3Dmotorway
>
> [5] https://wiki.openstreetmap.org/wiki/Trunk
>
> [6] https://wiki.openstreetmap.org/wiki/Road_signs_in_Belgium
>
> [7] https://wiki.openstreetmap.org/wiki/Tag:highway%3Dprimary
>
> ___
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
>
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging