ity (not
in absolute terms but 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
interpret 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
stream - as
illustrated by Kevin's example.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
e forest. 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/
___
Taggi
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
are unfamiliar with an area it is usually better 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
eas this 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
n cases where
waterway=river is clearly 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
ecause they evidently coincide with physical features like ridges)
but there are huge parts of the world where they are not and you would
only try to estimate them based on already existing data.
In short: This is not something you can reasonably map in OSM.
--
Christoph Hormann
y data for
accurate maps is orders of magnitude easier than elsewhere. Compared
to that the would-be gain of having watershed geometries available in
addition would be relatively small.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing li
quot; tag any more for
anything other than legacy fallback if other data is missing. Any
proposal to separately tag the language of the name tag (several
initiatives in that direction have been made in the past) is a very
different idea.
--
Christoph Hormann
http://www.imagico.de/
__
tag the language of the name
> > tag ... is a very different idea.
>
> Functionally both ideas work the same, right?
No, most of the advantages of my tagging concept depend on not having an
aggregate name tag but tagging the individual names in different
languages (like name
mes - which is exactly what the name tag is
currently used for, just in a less transparent, less consistent and
more difficult to maintain and to interpret form.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
On Sunday 16 September 2018, Joseph Eisenberg wrote:
> On Sun, Sep 16, 2018 at 1:23 AM Christoph Hormann
wrote:
> > > Are you objecting to the idea of tagging places as well as
> > > boundaries? What about the protected area / aboriginal lands
> > > boundarie
st of languages. If
this is just a question of typesetting rules that is the resposibility
of the map designer obviously but i have the impression this is also a
matter of local culture w.r.t. names and languages and that is
something that can and should be mapped.
--
Christoph
- usually enclosed by spaces. But that is
obviously based on latin script dominance. Other scripts and to some
extent also latin script languages have different conventions. If you
have names in well distinguishable scripts a separator is often
unneces
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
ed this 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/
ng.
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
ite useful - 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
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
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
point here is
verifiability of the geometry, not semantic nuances.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
sense 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
/gravitystorm/openstreetmap-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
with 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
cal map designer or geodata
engineer who is used to think polygon centered this requires some
amount of outside-the-box thinking.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
metries:
https://www.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 informa
re not
specifically designed for this kind of task. What you need to do is
essentially to 'probe' the coastline environment and determine the
extent of the bay and where the desired label best fits in there.
Obviously you can take a map sheet bounding box into account when d
street from a
single 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.openstreetm
m to optimize the
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
f
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
uch clearer and simpler matters have shown me
that. I can just hope most mappers will emancipate themselves from
this and not invest their time and energy in mapping and maintining
polygon mazes over coastal waters.
--
Christoph Hormann
http:/
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://li
not appropriate is to incentivize mapping bays with polygons by
labeling them from polygons in a different form that in particular for
large bays is more suitable and attractive than when mapped with nodes.
Or like for straits to label them when mapped with polygons but not
show them at al
German: Umgekehrt wird ein Schuh draus.
You should not need to add non-verifiable data to the database to be
able to map verifiable knowledge of the geography and see it in
OSM-Carto.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mai
enemy of the good.'
It means more or less: That idea makes more sense the other way round.
Literally: It will turn into a shoe the other way round.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.o
without taking into account the verifiability
question.
--
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
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
g narrow and deep in a narrow
valley further downstream).
And even if you'd change the definition of river/stream to represent
importance this could never be locally verifiable and globally
consistent at the same time.
--
Christoph Hormann
http://www.imagico.de/
__
ould be an obvious choice
although it could be useful to make the distinction natural/artificial
waterway indeed mandatory).
Greetings,
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstr
roken boundary relations
maybe).
Greetings,
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
etermine except at a
measurement station where it would make more sense to tag the node.
If someone has an idea for a practically measurable quantity that has a
clear relation to the discharge of a river that would be useful to tag
of course.
Greetings,
--
Christoph Hormann
http://www.imagic
and in terms of
individual territorial claims (which are obviously limited to the
normal territorial waters).
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
With waterway=riverbank you have to find the corresponding
centerline first (assuming it exists).
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
of the problems with waterbody tagging is that there ia no clear
criterion to distinguish between lakes and rivers/riverbanks. The new
tagging scheme acknowledges this and makes the distinction optional.
--
Christoph Hormann
http://www.imagico.de/
___
.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
rt from that
fast flowing rivers can reduce the salinity quite far out into the
ocean.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
f the coastline matching the UNCLOS
> baseline.
Under the proposed rules an argument could be made for placing the
coastline near Montevideo. Buenos Aires could well be considered to be
located at the river rather than the coast although the transit could
also be placed further upstream of
of course
these areas have no sharp boundaries.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
basic boolean operation on polygons. If you
have a large multipolygon with like a hundred ways in it you want to
cut in two for example this is quite cumbersome and error prone at the
moment.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mai
utomatically in principle but doing this in the
general case is very expensive so it would make sense to record this
information in the database.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.op
rea, usually the
favorite city of the one making the style decision. Choose a different
area where the map scale is different or the geographic setting leads
to a different distribution of POIs and things fall apart quickly.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
ing
substantial about the peak in question.
I am sorry if this sounds like a rant but there are simply so many tags
used a lot but completely useless in terms of informational value
exactly because of this. Please just make sure you do not fall into
this trap with your peak=* concept.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
to
remap the area from scratch.
[1] http://wiki.openstreetmap.org/wiki/Antarctic_Digital_Database
[2] http://www.eea.europa.eu/publications/COR0-landcover/land_cover.pdf
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openst
qualify as natural=bare_rock in total even if locally there is
exposed bedrock of course.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
xample this:
http://www.openstreetmap.org/node/2001818936
has an east-west orientation when you look at it closely but on a coarse
scale it is a north-south crossing.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@opens
ucht).
This argument by the way was already made in a slightly different
context in
https://github.com/gravitystorm/openstreetmap-carto/issues/804
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetm
at bay. If you want to edit the coastline in such situation you
would end up having to deal with a handful of convoluted multipolygon
relations, some of them of colossal size. Properly editing coastlines
is difficult for beginners in the first place. This would make it
borderline impossi
ular the case of small islands within a bay
deserves consideration.
> Some coastline ways would belong to more relations, so what ? They
> already usually belong to 3-4 administrative boundary relations,
Yes - and boundary relations are well known to be constantly broken and
a pain to maintai
the ease of rendering labels.
> (in other words, not treat them
> any different than any other area-like obbjects in osm).
You mean like place=town, place=city etc?
SCNR.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
around and out to open water for a similar distance, maybe somewhat
further, is a bay and is named ...
This is a much more accurate description of reality than a polygon.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Taggi
?
>
> Yes, and like everything that can be mapped as a polygon:
> amenity=hospital, leisure=pitch, natural=wood, etc etc etc.
as well as highway=*, waterway=*, natural=tree...
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
appropriate by the mapper).
If you want to formulate a formal mathematical rule for where the node
for a bay is best placed: Place it so the variance of the distance of
the node to the bay's shores is minimized. Most existing nodes comply
with this rule remarkably well.
--
coastal landforms dominated by mangrove.
Technically you might also consider the inner bay a lagoon rather than
a bay.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
the area outline would be formed by coastline.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
splines) based on the
nodes and the surrounding coastlines and place the text along them.
The main problem is that spatial database systems are not well suited
for this kind of work (i.e. tasks like 'find the closest coastline in a
certain direction').
--
Christoph Hormann
http:/
times at the moment,
guest_house=bed_and_breakfast 154 times.
Generally given the huge influence the standard style has on mapping and
that a lot of people articulated the need to differenciate between B&B
and larger guest houses in discussions i agree this change indeed is
probably not to the better.
y good
criterion for importance and it is very widely available already (35551
nodes aeroway=aerodrome with 31752 ways aeroway=runway). The problem
here is not having this information mapped i think but querying it from
the rendering database.
--
Christoph Hormann
http://www.imag
needed again. In total analyzing
30k-40k airports would not be such a big deal. But doing this again for
every zoom level and repeatedly near the metatile boundaries would hurt
of course.
--
Christoph Hormann
http://www.imagico.de/
___
Tagg
ntermittent=yes, seasonal=no
although i don't think past imports of NHD data have made this
distinction.
waterway=wadi can mean either intermittent or ephemeral or permanently
dry, see also
https://wiki.openstreetmap.org/wiki/Talk:Tag:waterway%3Dwadi
--
Christoph Hormann
h
known and reserve waterway=wadi - despite the then
misleading key - for valleys where waterflow is unknown.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
ons you
should not import the data unless you produce the information in some
way (either through manual mapping, computing the missing data or
getting it from other sources). Otherwise the data becomes dead mass
in the OSM database.
--
Christoph Hormann
http://www.imagico.de/
__
e river system
structure.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
ormulation there was somewhat ambiguous. I think it was meant to
indicate a way waterway=river is required to be mapped within the
waterway=riverbank polygon but not that its location must be exact. I
clarified this in the wiki.
--
Christoph Hormann
http://www.imagico.de/
sed to indicate tags that are vague in definition.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
nation (not an approval):
> It started as tagging for the end-users because GIS people and pilots
> were looking for leisure=common for unofficial landing sites in some
> places such as West Africa.
And that by the way is the very definition of cargo cult
(http://en.wikipedia.org/wiki/Car
nging it into a form of a
suitable tagging proposal (see other successful proposals from the past
for some hints) before formally starting the RFC.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstre
ning tracks of a car driving
across a wayless area to a solidly built gravel road.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
y this ponor.
Which is why mapping this is not really within the scope of OSM -
natural underground waterflows are inherently non-verifiable.
You can and should map the surface phenomena related to the underground
water flow of course - ponors, dolines, karst springs and other stuf
es + salt=yes would be right, otherwise
there is no well matching established tagging.
You could of course think about tagging it geological=salt_pan but it
might not be such a good idea to make the dominance of salt the
defining criterion here - the more generic term would be 'dry l
than a combination of all of them (which is what
natural=salt_flat would imply).
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
have no way
to decide how treat such feature. It would just say 'this waterway is
tubed' not what kind of waterway it is (artificial/natural, clean/dirty
water etc.)
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Taggin
You'd loose this distinction with
waterway=penstock. Generally waterway=* characterizes the water and
its flow while the term 'penstock' identifies a man made
infrastructure. Your tagging suggestion mixes these two separate
concepts into one tag which can be confusing f
and pipelines without a
pipe' underground.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
o the space constraints in urban environments.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
On Friday 06 November 2015, Paul Johnson wrote:
> Stop rendering this key and instead render the relations
Is there *any* map style that does this at the moment?
AFAIK osm2pgsql does not support including relation membership info in
the rendering database.
--
Christoph Hormann
h
it is rendered in the standard style - might
make sense to also render amenity=public_bath to avoid this.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
lify as such or not (which
would be commonly called 'Erlebnisbad').
Since leisure=swimming_pool is rendered in the standard style in blue it
is not widely used for tagging things other than the pool itself.
--
Christoph Hormann
http://www.imagico.de/
__
indoor swimming pools (for example public
> swimming pools used for swimming lessons)?
Yes.
With indoor facilities it is of course not usually possible to see if
they qualify as water_park without having been there but there are
definitely also many very basic indoor swimming pool facilities that
refer to the top - but keep in mind that the elevation
does not have to be constant.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
t mappers had a
highly variable understanding of what this tag means and its use was
very incoonsistent as a result.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
ainfall. Dust from the Sahara
has been found to be an important source of nutrients for the Amazon
rain forest for example.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
ances in wetland types. There is
already some limited use of wetland=string_bog/palsa_bog/raised_bog.
Current tag use indicates severe underuse of wetland=fen and overuse of
wetland=bog. Probably more than half of what is tagged wetland=bog is
actually
regions (like Tunesia) where climate
would not allow the formation of bogs.
--
Christoph Hormann
http://www.imagico.de/
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
201 - 300 of 357 matches
Mail list logo