Il giorno 18/set/2014, alle ore 07:57, Friedrich Volkmann b...@volki.at ha
scritto:
Say, how does landcover=grass differ
from surface=grass?
I agree that in this case it doesn't make a difference, besides that surface is
typically used as an attribute for highways and not as a feature
On Thu, Sep 18, 2014 at 12:18 PM, Mateusz Konieczny matkoni...@gmail.com
wrote:
That is really poor idea. IMHO remembering location and object type should
be enough to identify it.
OK, I'm game: let us say it is a node with an amenity and name tag
attached. Let us also say that the
On 18.09.14 00:33, Martin Koppenhoefer wrote:
from landuse, meadow would imply grass for me
Meadow IMO means there is some usage taken from the grass/hay (Weide,
Futterwiese,...).
I use landuse=grass in urban areas (Grünstreifen am Straßenrand), for grass
areas that are not a garden but there
Am 18.09.2014 um 08:35 schrieb Alex Rollin:
On Thu, Sep 18, 2014 at 12:18 PM, Mateusz Konieczny matkoni...@gmail.com
wrote:
That is really poor idea. IMHO remembering location and object type should
be enough to identify it.
OK, I'm game: let us say it is a node with an amenity and name
The biggest problem with ids is that it may degenerate into cases where
single objects has a giant list of various ids.
2014-09-18 9:17 GMT+02:00 Peter Wendorff wendo...@uni-paderborn.de:
Am 18.09.2014 um 08:35 schrieb Alex Rollin:
On Thu, Sep 18, 2014 at 12:18 PM, Mateusz Konieczny
Hi!
2014-09-17 23:44 GMT+02:00 Daniel Koć daniel@koć.pl:
We (in Polish forum) think, that changing landuse=grass into natural=grass
would make better tagging scheme, since grass is seldom a landuse (like
the tree is natural=tree, not the amenity or something else). How do you
find this idea?
Il giorno 18/set/2014, alle ore 09:30, Martin Vonwald imagic@gmail.com
ha scritto:
Not good. Contrary to other people I think that the readability of tags is
most important, otherwise we could simply use tags like ptn=pnx or
road=flying_saucer and define that those tags mean
On Thu, Sep 18, 2014 at 8:35 AM, Alex Rollin alex.rol...@gmail.com wrote:
How do I know/get-notified it was changed?
Specifically, how would you setup a system to receive notification that the
object was changed?
Have you done it? Do you have some scripts to share? (Can I please NOT
have
On Thu, Sep 18, 2014 at 7:57 AM, Friedrich Volkmann b...@volki.at wrote:
1. I thought the general consensus was to start using landcover for this
type of object.
No consensus. I strongly oppose landcover=* in view of its weak definition,
and because it invents nothing new. Say, how does
On 18.09.14 09:07, Martin Koppenhoefer wrote:
wouldn't these be better tagged with road or highway as landuse values?
Typically they are part of the road.
We probably misunderstand us...
This here:
http://www.openstreetmap.org/#map=18/48.20528/16.22363
In the south are Böschungen to the
On 18.09.14 09:07, Martin Koppenhoefer wrote:
wouldn't these be better tagged with road or highway as landuse values?
Typically they are part of the road.
We probably misunderstand us...
This here:
http://www.openstreetmap.org/#map=18/48.20528/16.22363
In the south are Böschungen to the
On 18.09.2014 08:24, Martin Koppenhoefer wrote:
Il giorno 18/set/2014, alle ore 07:57, Friedrich Volkmann b...@volki.at ha
scritto:
Say, how does landcover=grass differ
from surface=grass?
I agree that in this case it doesn't make a difference, besides that surface
is typically used as
So far, highway=traffic_signal is only defined for nodes and there are
only few ways and fewer relations.
Correct.
Also in favour of separation I would prefer to use junction=* with
name=* and only highway=traffic_signal with name if it is only a single
light (e.g. the case with a named
in OSM we focus on ground truth and having a local (!) community taking care
of the data and keeping it in shape.
The expected iconography differs between countries, as they are shown on maps
differently in the different countries. At least comparing Japan to America,
what they expect to be
Am 17.09.2014 09:29, schrieb Mateusz Konieczny:
2014-09-17 1:59 GMT+02:00 Bryce Nesbitt bry...@obviously.com
mailto:bry...@obviously.com:
I map contraflow as dual carriageway, to avoid this issue.
Both sides get oneway=yes, plus a full list of the modes allowed
(psv, bicycle,
Am 18.09.2014 16:07, schrieb Lukas Sommer:
So far, highway=traffic_signal is only defined for nodes and there are
only few ways and fewer relations.
Correct.
Also in favour of separation I would prefer to use junction=* with
name=* and only
Am 18.09.2014 21:29, schrieb fly:
Am 18.09.2014 16:07, schrieb Lukas Sommer:
So far, highway=traffic_signal is only defined for nodes and there are
only few ways and fewer relations.
Correct.
Also in favour of separation I would prefer to use junction=* with
name=*
Okay, if I get you right, you want to add to every element with the tag
highway=traffic_signals and the tag name=* also another new tag, either
– highway=junction
or
– junction=traffic_signals
and the presence or absence of this tag shall influence the rendering?
* Here, I still do not see your
Agreed. The general-purpose renderings, at least those intended for
small-screen use, should use a limited number of icons, and those should each
apply to a range of related object types. Large-screen and printed maps can use
a wider range of icon types, since there is room for a map legend.
19 matches
Mail list logo
