On Wed, May 2, 2012 at 4:53 AM, Pieren pier...@gmail.com wrote:
On Tue, May 1, 2012 at 5:56 PM, Anthony o...@inbox.org wrote:
What about closed ways tagged with barrier=* and some other ambiguous
*=* (e.g. barrier=hedge amenity=marketplace).
No, the tag barrier=* is not ambiguous and is
On Tue, May 1, 2012 at 5:56 PM, Anthony o...@inbox.org wrote:
What about closed ways tagged with barrier=* and some other ambiguous
*=* (e.g. barrier=hedge amenity=marketplace).
No, the tag barrier=* is not ambiguous and is self explanatory (does
not need to check any tag combination).
Btw,
On 4/27/2012 3:25 PM, Nathan Edgars II wrote:
While this is ongoing, Pieren continues to remove area=yes from
railway=platform, which has been on the page since it was created in
2008:
http://wiki.openstreetmap.org/w/index.php?title=Tag:railway%3Dplatformaction=history
And Pieren continues to
On Tue, May 1, 2012 at 10:36 AM, Nathan Edgars II nerou...@gmail.com wrote:
And Pieren continues to add his opinion to the page.
Not only mine. I'm still waiting at least a single example where a
closed way for platforms is not an area (and rendering issue cannot be
fixed by splitting the way
On Tue, May 1, 2012 at 12:04 PM, Martin Koppenhoefer
our data model should not need hacks like split the way to fix
rendering issues.
For me, the hack is to add a 2nd tag when it is not required in most
(if not all) of the closed ways.
Pieren
___
01.05.2012 11:53, Pieren wrote:
Not only mine. I'm still waiting at least a single example where a
closed way for platforms is not an area
How about that one?
http://www.openstreetmap.org/browse/way/48923955
It's a public_transport=platform for busses. There's a building with
ticket shops and
On Tue, May 1, 2012 at 1:55 PM, Tobias Knerr o...@tobias-knerr.de wrote:
01.05.2012 11:53, Pieren wrote:
How about that one?
http://www.openstreetmap.org/browse/way/48923955
If I understand correctly this document
(http://regiowiki.pnp.de/index.php/Zentraler_Omnibusbahnhof_Passau),
it is
On Tue, May 1, 2012 at 7:55 AM, Tobias Knerr o...@tobias-knerr.de wrote:
01.05.2012 11:53, Pieren wrote:
Not only mine. I'm still waiting at least a single example where a
closed way for platforms is not an area
How about that one?
http://www.openstreetmap.org/browse/way/48923955
It's a
On Tue, May 1, 2012 at 6:04 AM, Martin Koppenhoefer
dieterdre...@gmail.com wrote:
2012/5/1 Pieren pier...@gmail.com:
Not only mine. I'm still waiting at least a single example where a
closed way for platforms is not an area (and rendering issue cannot be
fixed by splitting the way for
2012/4/30 Pieren pier...@gmail.com:
I'm always standing in the contributor point of view. It is not the
wiki (or better said our recommendations) to follow the osm2pqsql
style file but the opposite.
+1
especially
when the main reaction is to say that mapnik/osm2pgsql will fail
because
On 27/04/12 20:11, Anthony wrote:
On Fri, Apr 27, 2012 at 3:06 PM, Tobias Knerr o...@tobias-knerr.de wrote:
Anthony wrote:
If I were writing a renderer (actually, I am), I would assume that a
closed way does not represent an area unless it a) has an always-area
tag such as landuse or b) is
Let's consider two well known examples:
building=* = usually by default area=yes, a non-closed way may be
considered as invalid(?)
highway=* = usually by default area=no, even if a closed way
A common default value would lead to either
~56M area=yes on buildings
or
~52M area=no on highways
28.04.2012 11:34, Peter Wendorff wrote:
Let's consider two well known examples:
building=* = usually by default area=yes, a non-closed way may be
considered as invalid(?)
Yes, it would be invalid. As documented in the wiki, the building key
(ignoring building=entrance and the like) is for
Am 28. April 2012 11:34 schrieb Peter Wendorff wendo...@uni-paderborn.de:
On the other hand, a fenced field is landuse=* (and in this respect
implicitly area=yes) and barrier=fence (and here implicitly area=no), and
that's fine.
I'd tag the way barrier=fence and create a multipolygon for the
I think we should decide the better way to map first, and then let the
programmers prioritize the fix. Since programmers are already
checking for always-area, it doesn't seem like a difficult fix. Are
patches welcome?
Patches welcome.
As programmers, we need a complete machine-readable
On Sat, Apr 28, 2012 at 6:04 AM, Tobias Knerr o...@tobias-knerr.de wrote:
I assume that this is a misunderstanding, because I don't think anybody
was suggesting that area=yes should be used together with tags that are
unambiguous anyway. My suggestion, and current practice as far as I can
On Sat, Apr 28, 2012 at 7:38 AM, Komяpa m...@komzpa.net wrote:
I think we should decide the better way to map first, and then let the
programmers prioritize the fix. Since programmers are already
checking for always-area, it doesn't seem like a difficult fix. Are
patches welcome?
Patches
On Sat, Apr 28, 2012 at 7:59 AM, Anthony o...@inbox.org wrote:
Scanning the wiki it looks like usually-not-area would be less of a
moving target. Otherwise almost every time someone adds a new amenity
you have to add a new always-area tag. The usually-not-area would be
junction=roundabout,
What specific program or programs are we looking at?
Any program that needs to go from OSM data model to OGC-compatible
one, having area object.
That basically lists any database backend (osm2pgsql, osm2sqlite,
nominatim...) and any converter like osm2shp/osm2ogr.
The list of software that
On Sat, Apr 28, 2012 at 8:17 AM, Komяpa m...@komzpa.net wrote:
What specific program or programs are we looking at?
Any program that needs to go from OSM data model to OGC-compatible
one, having area object.
Well, my question is what program or programs are you requesting
patches for.
On 27.04.2012 10:12, Pieren wrote:
You have to know anyway if your feature can be either a closed way or
an area and therefore need some special handling in your apps.
Unfortunately, yes. I wish we already had a proper area primitive so
this whole discussion would be obsolete.
The question is
On 4/28/2012 7:59 AM, Anthony wrote:
Scanning the wiki it looks like usually-not-area would be less of a
moving target. Otherwise almost every time someone adds a new amenity
you have to add a new always-area tag. The usually-not-area would be
junction=roundabout, barrier=*,
On Sat, Apr 28, 2012 at 9:16 AM, Tobias Knerr o...@tobias-knerr.de wrote:
Right now, we already have to distinguish three types of tags:
* always area
* always way
* way unless area=yes is present.
I simply do not think that the possibility to decrease of the number of
tags is worth
Another example is amenity=marketplace. How am I supposed to know if
this is always way, always area, or way unless area=yes is
present? Which one is it?
___
Tagging mailing list
Tagging@openstreetmap.org
For the barrier=city_wall I in fact see way AND area as possible:
A mid-age city wall of a bigger city may have walls of several meters
width sometimes, that include corridors, stairways and more, as another
building would.
If I map a strip of grass as an area with a width of 1m, a city wall
Am 28. April 2012 16:10 schrieb Peter Wendorff wendo...@uni-paderborn.de:
For the barrier=city_wall I in fact see way AND area as possible:
A mid-age city wall of a bigger city may have walls of several meters width
sometimes, that include corridors, stairways and more, as another building
On Fri, Apr 27, 2012 at 2:53 AM, Tobias Knerr o...@tobias-knerr.de wrote:
If a feature can be either a closed way or an area, the default
interpretation should always be the closed way. Otherwise, you'd have to
know arbitrary defaults for each type of object.
You have to know anyway if your
On Thu, Apr 26, 2012 at 8:53 PM, Tobias Knerr o...@tobias-knerr.de wrote:
Anthony wrote:
On Wed, Apr 25, 2012 at 5:17 AM, Nathan Edgars II nerou...@gmail.com wrote:
Where did I mention a renderer? If you draw a closed polygon with
railway=platform, that's a continuous platform with a hole in
On Fri, Apr 27, 2012 at 4:12 AM, Pieren pier...@gmail.com wrote:
On Fri, Apr 27, 2012 at 2:53 AM, Tobias Knerr o...@tobias-knerr.de wrote:
If a feature can be either a closed way or an area, the default
interpretation should always be the closed way. Otherwise, you'd have to
know arbitrary
Am 27. April 2012 20:14 schrieb Anthony o...@inbox.org:
A default set to the value which is correct 99.9%
of the time is not arbitrary.
how would you distinguish between default values and incomplete
data/missing information?
We could have a tag
Op 27 apr. 2012 20:41 schreef Martin Koppenhoefer dieterdre...@gmail.com
het volgende:
Am 27. April 2012 20:14 schrieb Anthony o...@inbox.org:
A default set to the value which is correct 99.9%
of the time is not arbitrary.
how would you distinguish between default
Anthony wrote:
area=no can be considered a sic!, but that tag should never have any
actual effect.
Effect on what?
On renderers or any other applications working with OSM data.
If I were writing a renderer, I would assume that a
closed way railway=platform represented an area unless it
On Fri, Apr 27, 2012 at 2:40 PM, Martin Koppenhoefer
dieterdre...@gmail.com wrote:
Am 27. April 2012 20:14 schrieb Anthony o...@inbox.org:
A default set to the value which is correct 99.9%
of the time is not arbitrary.
how would you distinguish between default values and
On Fri, Apr 27, 2012 at 3:06 PM, Tobias Knerr o...@tobias-knerr.de wrote:
Anthony wrote:
If I were writing a renderer, I would assume that a
closed way railway=platform represented an area unless it was tagged
area=no. So that's an effect.
If I were writing a renderer (actually, I am), I
While this is ongoing, Pieren continues to remove area=yes from
railway=platform, which has been on the page since it was created in
2008:
http://wiki.openstreetmap.org/w/index.php?title=Tag:railway%3Dplatformaction=history
___
Tagging mailing list
On Wed, Apr 25, 2012 at 5:17 AM, Nathan Edgars II nerou...@gmail.com wrote:
Where did I mention a renderer? If you draw a closed polygon with
railway=platform, that's a continuous platform with a hole in the middle.
There may be a few cases of such in real life at a complicated junction.
If
Anthony wrote:
On Wed, Apr 25, 2012 at 5:17 AM, Nathan Edgars II nerou...@gmail.com wrote:
Where did I mention a renderer? If you draw a closed polygon with
railway=platform, that's a continuous platform with a hole in the middle.
There may be a few cases of such in real life at a complicated
The german article still has the recommendation of adding area=yes.
One of the biggest problems in the wiki is the fact, that very often
articles in different languages are not really translations, but
different articles.
As the tag railway=platform is applicable to areas as well, according
to
On 4/25/2012 3:39 AM, Pieren wrote:
On Wed, Apr 25, 2012 at 3:46 AM, Nathan Edgars IInerou...@gmail.com wrote:
It's not highway only. For example, it can be used on railway=platform:
http://www.openstreetmap.org/browse/way/94063273
or man_made=pier:
On Wed, Apr 25, 2012 at 10:43 AM, Nathan Edgars II nerou...@gmail.com wrote:
Because a railway platform is usually drawn as a single line (as is a pier).
Omitting area=yes gives a hole in the middle.
Sounds tagging for the renderer...
Pieren
___
miau.
OSM does not have area object, thus it needs something to mark
object as polygon.
There are some tags that insist that a line/relation is filled inside.
These are area=yes and type=multipolygon.
All the other tags may mean either line or a polygon depending on
context. Sometimes context
On 4/25/2012 4:53 AM, Pieren wrote:
On Wed, Apr 25, 2012 at 10:43 AM, Nathan Edgars IInerou...@gmail.com wrote:
Because a railway platform is usually drawn as a single line (as is a pier).
Omitting area=yes gives a hole in the middle.
Sounds tagging for the renderer...
Where did I mention
On Wed, Apr 25, 2012 at 11:05 AM, Komяpa m...@komzpa.net wrote:
OSM does not have area object,
not yet (maybe in API0.7)
thus it needs something to mark
object as polygon.
No. Most of the polygons do not require a tag area (amenity,
building, landuse, leisure, landuse).
There are some
On Apr 25, 2012 1:54 AM, Pieren pier...@gmail.com wrote:
On Wed, Apr 25, 2012 at 10:43 AM, Nathan Edgars II nerou...@gmail.com
wrote:
Because a railway platform is usually drawn as a single line (as is a
pier).
Omitting area=yes gives a hole in the middle.
Sounds tagging for the
44 matches
Mail list logo
