As a way why not but not as en area.
There is same comportment on barrier=bollard with a succession of bollard
crossing a way. You need intersect barrier with highway to perform good
tracking and set access (foot=yes and/or not bicycle=yes) barrier=* are
implicitly no access for all trip type.
On 24/08/18 03:49, Philip Barnes wrote:
On Fri, 2018-08-17 at 07:51 +1000, Warin wrote:
If the thought is to map a group of blocks as an area .. then my vote
is no at least without more information.
It raises the question as to what the level of obstruction is - are
motorcycles bared by this
On Fri, 2018-08-17 at 07:51 +1000, Warin wrote:
> If the thought is to map a group of
> blocks as an area .. then my vote is no at least without more
> information.
>
> It raises the question as to what the level of obstruction is -
> are motorcycles bared by this
hilip Barnes" mailto:p...@trigpoint.me.uk>>
Do: talk@openstreetmap.org <mailto:talk@openstreetmap.org>; "David
Fox" <mailto:davefoxfa...@btinternet.com>>; "Tomasz Wójcik" <mailto:tom...@wp.pl>>
Data: 16.08.2018 10:05:11
Temat: Re: [OSM-talk] B
On 15.08.2018 20:49, Tomasz Wójcik wrote:
> Currently, barrier=block is not allowed to be mapped as an area. As
> blocks can be big enough to map them as areas, I think it should be
> allowed, the same as in barrier=wall or barrier=hedge.
For routing purposes, barriers are usually connected to
uot;Tomasz Wójcik"
Data: 16.08.2018 10:05:11
Temat: Re: [OSM-talk] Barrier=block areas
Hedges can certainly be areas, some can be a few metres thick.
A common mapping scenario is a thick hedge and a stile at each side.
The only way to represent this is to map as an area and map the stiles
as
Hedges can certainly be areas, some can be a few metres thick.
A common mapping scenario is a thick hedge and a stile at each side. The only
way to represent this is to map as an area and map the stiles as nodes
connected to the outline.
Phil (trigpoint)
On 16 August 2018 01:14:49 BST, David
: talk@openstreetmap.org
Onderwerp: Re: [OSM-talk] Barrier=block areas
Being a closed way with area=yes does not mean they aren't connected to the
underlying ways: I don't think router be bothered by this.
Yves
Le 16 août 2018 02:14:49 GMT+02:00, David Fox a
écrit :
Barriers, by definition
Being a closed way with area=yes does not mean they aren't connected to the
underlying ways: I don't think router be bothered by this.
Yves
Le 16 août 2018 02:14:49 GMT+02:00, David Fox a
écrit :
>Barriers, by definition, provide some level of restriction. Without
>attaching them in some form
On 16/08/18 09:33, Martin Koppenhoefer wrote:
barrier=block is intended for barriers, i.e. they block a highway.
Blocks for decorative or recreational purposes arranged at squares or
on the side of streets are not covered by the tag.
-1 for the proposed change.
Blocks are increasing used
Barriers, by definition, provide some level of restriction. Without attaching
them in some form it becomes hard for routers to account for them.
Hedges and walls are linear in nature, not an area.
On 15 August 2018, at 19:51, Tomasz Wójcik wrote:
Currently, barrier=block is not allowed to be
barrier=block is intended for barriers, i.e. they block a highway. Blocks for
decorative or recreational purposes arranged at squares or on the side of
streets are not covered by the tag.
-1 for the proposed change.
Cheers,
Martin___
talk mailing
12 matches
Mail list logo
