any tags you want and i firmly
believe in that. You can question if this freedom applies to
non-verifiable tags but i am not niggling here. Automated edits
adding/modifying wikidata tags are a different subject of course but
that is not the topic here.
--
Christoph Hormann
http://www.imagico.de/
_
onsider for your assessment. And because
of that the mapper in OSM cannot verifiably determine if a wikidata
object created based on such information qualifies for being specified
in a wikidata tag.
--
Christoph Hormann
http://www.imagico.de/
showed that
some (though not all) mappers think wikidata tags have to be unique
(i.e. each value only used once).
Website URLs will often be locally verifiable - either because of
written information (shop sign, restaurant menu etc.) or - like with
the name - by asking informed locals.
--
Chri
ikidata tags - just that the
problems are seemingly outsourced to an external project and the mapper
does not have to deal with them - which is wrong of course.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetm
vide a clear 'upgrade path'
to all widely used educational amenity tags - in particular
amenity=college seems to be currently not covered by your proposal.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Taggi
i.openstreetmap.org/wiki/Automated_Edits_code_of_conduct
for the documentation and discussion requirements of mechanical edits.
> And it is only partly mechanical since I'm reviewing all objects.
Wow - i wish i had that kind of travel budget.
--
Christoph Ho
abel here - which is of course something a lot of mappers
do when they choose name tags.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
cation are an undiscussed
mechanical edit and should be reverted.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
g with the idea of supporting brands in their own
> right, independently of a name .
I should probably add that what can be considered the name of a feature
is ultimately the decision of the local community.
--
Christoph Hormann
http://www.imagico.de/
___
Ta
ing to OSM's verifiability principle. There you are
correct. But human use of names has the tendency to converge to a
uniform name in many cases so if there are verbal identifiers used
there is also often a verifiable name.
--
Christoph Hormann
http://www.imagico
om
dry to water cover follows does not work. Offering this as an option
in case mappers have more in depth knowledge is a good idea, i said
that in the past. But making it mandatory is bound to fail.
--
Christoph Hormann
http://www.imagico.de/
___
Tagg
rse.
2) A good documentation of a tag on the wiki that accurately describes
how the tag is acutally used is very helpful for both mappers and data
users and as such very useful when making rendering decisions.
Attempts at writing a tag page (or a tagging proposal) on the wiki
specifically to get
still a
desire for an authority to stop this even among those who are in
general in support of a liberal and non-authoritarian community.
An egalitarian and open community like OSM is a fragile thing...
--
Christoph Hormann
http://www.imagico.de/
s to document the actual use of tags. Abusing this platform
to push political ideas how tagging in OSM should look like according
to some opinion is what i call derailing the community processes.
--
Christoph Hormann
http://www.imagico.de/
Any tag that is deliberately used by mappers (i.e. that is not a typo or
vandalism or similar) should be documented on the wiki.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
hat could happen to OSM in the long term is
that it becomes 'alternativlos' to both data users and contributors.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
like
Approach 3 on
https://wiki.openstreetmap.org/wiki/Forest
See:
https://wiki.openstreetmap.org/w/index.php?title=Tag:landuse%3Dforest=200189
in particular the section 'Attention'.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing lis
d no, with hard
work i don't mean primarily to engage in endless dysfunctional tagging
discussions here).
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
resets any more since
there would probably be sufficient diversity for this to be self
regulating.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
other
words: Here it just means the opposite of stagnation.
Most people probably agree that in the OSM context the ultimate goal is
to create the best map of the world. And that for this you need a
global community of active local mappers. But this and all the details
around it is a very differ
d by some tagging authority
anyway. Most mappers want tags that represent what they see in
reality, not something that fits into the systematics thought up by
some committee of people from Central Europe and North America with no
clue about the diversity in culture and geography world wide.
--
Christop
lying landcover but many do
> not.
The concept is actually completely key agnostic. You could for example
also use it for urban landuse - like a residential area with also a few
shops using landuse=residential and landuse:secondary=retail.
So not a good opportunity to piggy-back your landcove
wledge of the
ephemeral nature).
By the way about 100k of the 150k features with a seasonal=* tag also
have an intermittent tag and the ~50k which do not include all the
seasonal roads etc. So seasonal=* is for water features mostly used as
a supplemental tag to intermittent=*.
--
Christoph Horman
s primarily a
woodland or a bare rock area but you could document the fact that both
elements are present.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
was exactly opposite
What you wrote was clear, i was talking about Warin's proposal which
implies ("This should not be confused with intermittent") that you
should either tag intermittent=* or ephemeral=* but not both.
--
Christoph Hormann
http://www.imagico.de/
___
semantics are irrelevant for the actual meaning of tags.
What a tag in OSM means depends on what it is actually used for, not
what someone says the key used requires it to mean.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing lis
e: The human brain in highly capable in dealing with
inconsistent rules in the environment. Most languages for example have
grammatic and pronounciation rules with tons of exceptions (which is
not unlike tags in OSM by the way) but people manage to deal with that.
--
Chris
just would not be English any
more.
Your brave new world with an intelligent design of orthogonal keys
would - apart from being an illusion (Kurt Gödel is greeting) - just
not be OSM any more.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
ping geometries of different feature types of the same or
similar semantic levels.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
hese do not depend on a data consumer (other than your fellow
mappers in case of the second point).
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
hose who do the work are - by a very large margin - the
mappers. And developers should use the influence they inevitably have
to support the mappers in making competent and viable decisions - in
their interest, not in that of the data users.
-
s (like using surface=* or usage=* on
features it is so far not commonly used on) is also fine if it matches
previous use in meaning.
* adding new uses to existing primary tags is highly sensitive and
should usually be discussed first. Creating a new tag is almost always
a better idea.
--
C
ithin lakes is that mapping a navigation route that
coincidences with a river/canal running through and being mapped
through a lake is much simpler because you can just use an additional
tag instead of a separate geometry.
--
Christoph Hormann
http://www.imagico.de/
map.org/wiki/Key:drinking_water
covers this matter quite well.
Please keep in mind that OSM is about local knowledge so the important
question is if people locally drink the water or not.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging
em added in all cases is not an approach that is likely to be
successful. Data users just have to deal with that.
As a data user you should in particular be aware of course that
intermittent=yes + seasonal=no is a meaningful combination (with 68k
uses).
--
Christoph Hormann
ant to
stick to the former.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
s in tagging development) would help you in
making decisions regarding tagging presets.
Anyway - i look forward to iD offering the possibility to include
different presets and hope this will lead to more diversity and more
choices in tagging presets available to mappers.
--
Christoph Hormann
http://ww
a process to change tagging.
Please don't interpret this as a critique of your attempts to improve
tagging in OSM (which are admirable). My comment is only about
actively connecting this to editor preset decisions.
--
Christoph Hormann
http://www.imagico.de/
___
not ready to question
your assumtions.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
SM. Don't do that.
If you want to create such a wiki page to describe your subjective
perception of the situation that is fine - but you should indicate it
as such.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
desirable water.
Long story short: My recommendation would be tagging waterway=canal and
specifying usage=* and width=*. This might not look ideal on the map
but will allow all data users to correctly interpret the data.
--
Christoph Hormann
http:/
at the moment. Extending that
would be the best way to move forward IMO.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
r part of the waterway.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
the kind of structures that were not
on the radar of those who originally invented the waterway tags.
> Now most of them are tagged with waterway=ditch.
You probably agree that this is somewhat unfortunate because there is no
way to distinguish them from a classic ditch for the data user.
-
th tag width=*, if you don't want to map
the width then don't create classes based on width thresholds.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
d/landuse=forest is
locally verifiable while the abstract concept of naming some of this
woodland the Amazon rainforest is not.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
Documentation of the tag does not provide any help. At least
the Oceania node seems more like an arbitrary labeling node - and the
classification and definition of Oceania as a continent is quite
culture specific as well.
--
Christoph Hormann
http://www.imagico.de/
___
to convince mappers to map in a certain way for the convenience
of certain data users.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
r than 1m and less wide than 3m you have a pretty
precise measurement.
> However if you enter width="2 m", the width value
> pretends to be exact.
Why do you assume that?
In OSM individual data points - be that in tags or in coordinates - come
with no implication of accuracy of
cases under comparable
circumstances with a known accurate reference value but practically
this is not feasible.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
Re-tagging these into something different would just bury
the problems between other data.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
reservoir is in
addition used widely for any kind of waterbodies containing dirty water
(tailings ponds, sewage treatment plants etc.) where there is obviously
no pre-existing waterbody. So you have two fairly unrelated
applications of this.
t is not how the tag is used.
water=reservoir is primarily used for dammed rivers. landuse=basin is
mostly used for water areas created artificially where there was no
pre-existing waterbody. If in your area these are mostly temporarily
water filled that is due to climate and n
feature and not just generic underground waterway tagging
being used.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
est. This is a pragmatic solution because placing it
inside the mangrove would be non-verifiable. Of course mapping the
mangrove is important for the data to be meaningful in this case.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging ma
r area plus the line of the waterway are
> mapping the longest extention of the river.
To be clear: The upper limit of tidal influence on water levels and the
ecological limit of the marine environment are two very different
things. Tidal influence often goes much further upstream - as
illustr
not correct, not to allow doubt free
decisions in all boundary cases.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
create a verifiable definition of the geometry
(which seems hard) - otherwise you always end up with this kind of
label drawing.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
ter to map what you
can observe on the sources available than to just guess.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
his is a bit different of course.
But i don't want to discourage anyone from a actually defining new tags
here - just make sure you document them in a verifiable form.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
ent a new tag if
there is a clear distinction between the two that is practically
verifiable by a mapper without specialized architectural or historic
knowledge.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.o
f other methods and suggestions
exist (linear way + polygon with the same tag, polygon only, linear
way+ polygon with other tag) but none of them has found consistent use
so far.
* A four node polygon transports no additional information for a runway
compared to a two node way wit
from the spatial
relationship of the boundary relations.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
* mapping a boundary with relation tagging only with no tags on the way
is correct.
* tagging the ways in addition to the relation is ok but not required.
* tagging on boundary relations superseedes any conflicting tagging on
boundary ways.
--
Christoph Hormann
approach is without good alternatives is a misapprehension of
the situation.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
clear misuse of
the tag).
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
between
boundaries at or near the coastline and those away from the coastline.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
n beaches and tidal flats: A
beach is formed by waves, it therefore always has a significant slope
and is rarely wider than a few hundred meters. A tidal flat is a flat
area exposed at low tide that is shaped by the tidal currents.
--
Christoph Hormann
http://www.imagico.de/
_
//www.state.gov/documents/organization/57675.pdf
Independent of that the placement of the coastline at river mouths is
generally somewhat variable. I wrote a proposal a few years back aimed
at defining some verifiable limits for that:
https://wiki.openstreetmap.org/wiki/Proposed_Features/Coastline-Riv
dysfunctional the tag documentation on
the wiki has become - in this case with the attempt to encourage
improvement of the tag documentation being scuttled by silently
removing the verifiability template.
--
Christoph Hormann
http://www.imagico.de
6=14=3=bing-satellite=mapnik=google-satellite
In the upper part this is clearly a beach (as visible in the Bing image
with high water level). In the lower part with the tidal channels
visible in the Google image it is clearly a tidal flat.
--
Christoph Hormann
http://www.imag
haracteristic. I believe, but am not sure, that the same applies to
> the UK manor houses .
I think Martin's point was that a historic manor house does not have to
fulfill a present day function as administrative centre of an
agricultural estate.
--
Christoph Ho
ocumenting tags they invent or to improve missing documentation of
existing tags.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
choices in quite a few cases is
valid. I just disagree that the solution to that is having self
declared leaders watch over the mappers.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
https://de.wikipedia.org/wiki/Lausitzer_Seenland
Such features do not belong in OpenStreetMap.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
in countries with no general anti-discrimination
laws w.r.t. gender identity and sexual orientation is lgbtq=no for
establishments that specifically don't allow lgbtq people. That would
essentially be an access restriction.
--
Christoph Hormann
http://www.imagico.de/
_
n most cases research stations
have a well defined center but not a well defined outline it makes much
more sense to map them with a node than with a polygon.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
the coastline but given
the curved form at the eastern end a linear way could be clearer.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
w.openstreetmap.org/way/372986131
https://www.openstreetmap.org/relation/2824513
a large portion of the geometry and as a result the derived way_area are
completely non-verifiable. Also here a properly placed node would
together with the coastline transport all the verifiable information
about the geog
e of
the node to the bay's shores is minimized. Most existing nodes comply
with this rule remarkably well."
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
e properly placed node. I will keep this case in mind for the
future as a good example to illustrate that.
Note the current node:
https://www.openstreetmap.org/node/561722
is of course not suitably placed. Correct position would be around
here:
https://www.openstreetmap.org/?mlat=57
e
design and placement of a label and scuttling that with the illusion of
a defined extent is sad.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
reetmap-carto/issues/804
https://github.com/gravitystorm/openstreetmap-carto/issues/2068
https://www.openstreetmap.org/user/imagico/diary/43957
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
pport consistent differentiation of standing and
flowing water is one thing - but this is not directly related to the
different tagging schemes and it has nothing to do with anything
Russian.
--
Christoph Hormann
http://www.imagico.de/
___
Tagg
at these are physically based rules
rooted in the observable reality and not based on political or other
purely abstract considerations.
Some newer examples of problematic closure placements (in addition to
the ones in the proposal):
https://www.openstreetmap.org/way/463191729
https
t as a fraction of the open ocean salinity in the
area).
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
et the local situation or when inexperienced mappers are
unaware of the significance of distinguishing between ocean and
riverbank mapping.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
sal which
is linked to from the coastline documentation.
> Given a properly formulated rule-of-thumb, why should remote armchair
> mappers come to a different conclusion to local mappers in this case?
As said this is mostly due to misinterpreting image
s kind
of defeats the whole purpose.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
On Wednesday 26 September 2018, Frederik Ramm wrote:
> Hi,
>
> On 26.09.2018 16:14, Christoph Hormann wrote:
> > Also in Germany we have features with no German name (most notably
> > probably in regions with significant minority languages but also
> > for example some
i.openstreetmap.org/wiki/Proposed_features/Language_information_for_name
but this only covers the single language case and would only have
addressed a very small fraction of the naming problems in OSM.
--
Christoph Hormann
http://www.imagico.de/
As said the aim is not to duplicate the name data but to replace the
generic name tag that has no defined language with the individual
language name tags.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
- even if just from
a single person's perspective. But that is already quite a huge amount
of work.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
convince data users to implement interpretation of a new tagging system
up-front without the database containing significant amounts of data
where this would be useful for. This is not just buying the cat in a
sac, it is like building a home for the cat without having seen it yet.
--
Christo
icient to query in the form you want to use.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
here. What arguments you have against this suggestion will
decide which of the above groups you belong to. ;-)
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
e geography
of the world. That the existence of Jamaica Bay is part of that is not
in dispute but still it is important to make that distinction.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.o
er.
Rendering mangroves with a fill color has already been discussed in:
https://github.com/gravitystorm/openstreetmap-carto/pull/1497
https://github.com/gravitystorm/openstreetmap-carto/issues/2025
--
Christoph Hormann
http://www.imagico.de/
___
Tagg
wiki/Tag:natural=cape
These are typical major capes:
https://www.openstreetmap.org/node/32532727
https://www.openstreetmap.org/node/2510985983
https://www.openstreetmap.org/node/2098928265
https://www.openstreetmap.org/node/4727612495
https://www.openstreetmap.org/node/2696775247
--
C
for the real thing from the sea) near here:
https://www.openstreetmap.org/node/5316727559
The area Cape Canaveral AFS is built on
https://www.openstreetmap.org/relation/7384620
is called Canaveral Peninsula (unmapped in OSM - see USGS topos as well)
which is part of Merritt Island.
--
Christoph
101 - 200 of 342 matches
Mail list logo