Tom Pfeifer writes:
>
> I stumbled over some maxheight=none tags on motorways, that did not even
> pass under a bridge. I found that this is the most frequent value of
> maxheight (2889 of 41474).
Tom,
thanks for bringing this up. As the author of Maxheight Map ([1], [2]) I'd
like to put some
We collected the list of the brick kilns from Brick kiln association for
Kathmandu Valley and even mapped the kilns from the satellite image as they
are distinct features. We went to the field where the brick kilns are
located, asked the authorized person for the information and permission to
uploa
I don't mind what the text is or what the tag is, but to me there is all
the difference in the world between a bridge which might be any height
(including being dangerously low) and one which definitively had no warning
sign when it was surveyed (and which can therefore be considered to provide
eno
Speaking of "permanent structures", is there a recommended way of tagging a
maxheight that is temporarily lower, such as when scaffolding is erected under
a bridge for painting or repairs?
On October 24, 2014 6:10:48 PM CDT, "Kytömaa Lauri"
wrote:
>Personally, i use maxheight = x + maxheigh
Dear all,
Currently the tag shop=bag (612) is used in parallel to the less used
tag shop=bags (120). I propose to agree on the de facto standard (the
singular).
In order to accomplish that, I have created two proposal pages:
http://wiki.openstreetmap.org/wiki/Proposed_features/Bag_shop
Please le
On Sun, Oct 26, 2014 at 05:12:20PM +0100, Mateusz Konieczny wrote:
> Please, try mapping bays as areas - not as nodes.
>
> It is really rare to see it done this way - but it is doable, see
> http://overpass-turbo.eu/s/5CQ
not practical in most cases. Almost every bay is part of a larger bay
and s
On Sunday 26 October 2014, Mateusz Konieczny wrote:
> > Furthermore the outer edge of a bay, i.e. the edge that is not
> > coastline is usually not well defined and would require an
> > arbitrary cutoff.
>
> Yes, cutoff is unfortunately quite arbitrary. But node placement is
> completely arbitrary
Martin Koppenhoefer wrote on 2014-10-26 20:26:
Am 24.10.2014 um 20:53 schrieb Tom Pfeifer:
I would recommend to add maxheight=unsigned to the English and other wiki
pages, and list maxheight=none as incorrect tagging.
unsigned maxheight is the typical situation in all areas that I've been to.
> Am 24.10.2014 um 20:53 schrieb Tom Pfeifer :
>
> I would recommend to add maxheight=unsigned to the English and other wiki
> pages, and list maxheight=none as incorrect tagging.
unsigned maxheight is the typical situation in all areas that I've been to. In
some (all?) countries there is s
> Doable for sure but an awfully bad idea, mapping bays as areas would
> mean two features for the same object (coastline polygon and bay area).
Coastline polygon and bay area is not the same object. Yes, part of border
is
shared - it is nothing wrong. Also it is possible to use for example
multip
On Sunday 26 October 2014, Mateusz Konieczny wrote:
> Please, try mapping bays as areas - not as nodes.
>
> It is really rare to see it done this way - but it is doable, see
> http://overpass-turbo.eu/s/5CQ
Doable for sure but an awfully bad idea, mapping bays as areas would
mean two features for
Please, try mapping bays as areas - not as nodes.
It is really rare to see it done this way - but it is doable, see
http://overpass-turbo.eu/s/5CQ
Bay mapped as node is hard to process - for example: deciding whatever name
should be
rendered. It is completely impossible to retrieve information wh
12 matches
Mail list logo
