(1)
In general I agree but I would de-emphasize current issues in specific data
consumers
("Areas tagged place=sea without natural=water do not render in major renderers
such as OpenMapTiles or the Standard Tile Layer.") which may be trigger for
this
proposal but is not a good reason for changing data design in OSM.
("Data consumers do not and cannot do X and X is important" would be a good
reason,
"Data consumers do not do X and refused to do X for reasonable reasons" also
would be
while "Data consumers are not doing X" is not a good reason and results in
things
like manual data processing of bus stops in so called PTv2 which could be
easily automated)
"The exact water boundary of an oceanic sea is inexact and not verifiable" was
put at the
end while it is among the most serious issues (unless you intended to start
from minor ones
and end with the most substantial?)
(2)
"Below is a listing of all beast megapolygons" can you add reference with
explanation
how you get them? Even if it is SQL query in global osm2pgsql database which is
not easily accessible for all then it can also be useful for some or future you
updating
this page. And maybe someone will learn something new how to use OSM data :)
(3)
"and thus a wikidata QID should be tagged" - maybe
"and thus a wikidata QID is useful to be tagged"?
I would not imply that someone not adding wikidata is doing something
incorrectly.
(4)
I think that for example
https://wiki.openstreetmap.org/wiki/File:Mediterranean_Americana.jpg
is missing {{ODbL OpenStreetMap}} on its file page
https://wiki.openstreetmap.org/wiki/Template:ODbL_OpenStreetMap
(disclaimer: IANAL, info based on my best current personal knowledge)
Maybe making Americana equivalent of
https://wiki.openstreetmap.org/wiki/Template:OSM_Carto_screenshot
would be nice and useful?
Also, I would recommend uploading such images to Wikimedia Commons
instead at https://commons.wikimedia.org/ .
That makes them usable for wider community and uploading images
there has much lower number of traps caused by unmaintained software
(Wikimedia Commons is a bit creaky and underfunded by WMF that prefers to
waste funds, but their image upload process is actually maintained)
Jan 2, 2023, 03:55 by zelonew...@gmail.com:
> A proposal[1] to recommend the tagging of oceanic seas as nodes rather than
> areas is now open for comments.
>
> This proposal follows a community forum discussion[2] regarding the modeling
> of the Gulf of Mexico as a node rather than as a crude polygon. This change
> was made in [3]. This proposal would codify the practice of tagging seas as a
> node as a general practice.
>
> If approved, this proposal would create a recommendation that mappers not
> create complex "beast" mega polygons on top of the ocean (outside the
> coastline), such as the 5,400+ member Gulf of Saint Lawrence [4], as this
> practice is unnecessary for labeling.
>
> [1] > https://wiki.openstreetmap.org/wiki/Proposed_features/High_seas
> [2] >
> https://community.openstreetmap.org/t/gulf-of-mexico-object-rendering-of-large-seas
> [3] > https://www.openstreetmap.org/changeset/130767988
> [4] > https://www.openstreetmap.org/relation/9428957
>
>
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
