Talk:Key:seamark:name
Jump to navigation
Jump to search
Is there any justification to reinvent and duplicate tag name?
For example - is there any good reason to use "seamark:name=5N" instead of "name=5N"? Mateusz Konieczny (talk) 12:51, 2 August 2015 (UTC)
- I've verified that neither OpenSeaMap nor JOSM's OpenSeaMap display
seamark:name=*
, not even whenname=*
is missing. Also, iD does not support it. 4 out of the 60 OpenSeaMap presets for JOSM useseamark:name=*
only, all others (the vast majority) usename=*
only. So,seamark:name=*
is probably an ancient leftover that could be moved to other name tags such asofficial_name=*
to facilitate geocoding using standard tools such as Nominatim. - I think "5N" is probably a
ref=*
code, not a name. However, OpenSeaMap does not displayref=*
, nor does the standard layer for unnamed elements that can be combined with sea marks (eg. sea lights andman_made=lighthouse
). I think they should support it, but the combination is not very common. In my area nearLagoa dos Patos, whenever a sea mark has both a name and a reference code, official nautical maps represent it in the format "Name (code)", and when there's only a reference code, it's only "(code)".
- Also in my area,
ref=*
in sea marks seems to represent a database record identifier. If that's right, it should be moved into a more specific tag identifying the data source, as is usually done with other kinds of data imports in OSM. Also,seamark:name=*
is being used for the name displayed in official nautical maps, whilename=*
is a shortened, more standardized version of it that fits nicely into OpenSeaMap.--Fernando Trebien (talk) 19:58, 1 March 2019 (UTC) - @Malcolmh: - in https://wiki.openstreetmap.org/w/index.php?title=Key:seamark:name&curid=99243&diff=2184554&oldid=2184550 you claim that "The "ref" for a seamark object would be the catalogue number in the lists published by navigation authorities." - how it exactly differs from
ref=*
tagging? Mateusz Konieczny (talk) 07:40, 8 August 2021 (UTC)
- Hello @Mateusz Konieczny: I did a test too and got different results. OpenSeaMap only renders
seamark:name=*
, notname=*
. Example - only one of the three lights hasseamark:name=*
, and that's the only one that's rendered. --Kylenz (talk) 00:30, 6 November 2021 (UTC)- @Kylenz: it is not a good justification, see Tagging for the renderer. It seems that OpenSeaMap should be fixed to use standard tags rather than duplicating them Mateusz Konieczny (talk) 06:31, 6 November 2021 (UTC)
- I totally agree, I personally will be using
name=*
anddescription=*
instead ofseamark:name=*
andseamark:information=*
. Just worth pointing out that OpenSeaMap currently doesn't support the two standard tags --Kylenz (talk) 07:00, 6 November 2021 (UTC)
- I totally agree, I personally will be using
- @Kylenz: it is not a good justification, see Tagging for the renderer. It seems that OpenSeaMap should be fixed to use standard tags rather than duplicating them Mateusz Konieczny (talk) 06:31, 6 November 2021 (UTC)
- Hello @Mateusz Konieczny: I did a test too and got different results. OpenSeaMap only renders
- While I don't like it, you should look at it together with
seamark:national_name=*
. - I'm more annoyed by not using
ref=5
for theseamark:name=5
example here. - ---- Kovposch (talk) 07:33, 6 November 2021 (UTC)
Effort to document difference from, and use with, name
When tagging something like seamark:type=bridge
for the benefit of water-based navigation, there are a bunch of seamark-tags that apply. seamark:name=*
is one of them. There a number of details I would like to improve the documentation of:
- The documentation currently says that the value of this tag should not be a description, similar to how
name=*
is used. I've seen this tag (ab)used in this manner though. There is no correspondingseamark:description=*
. What is the guideline for moving descriptive names to a more suitable tag?
- Another point that could use clarification: what is the relation with
name=*
? Shouldname=*
be used together with this tag, or only when they differ?
- @Malcolmh: You added this phrase “This name is often different from the local customary name, which would be used for the "key:name" tag.”. How and when is this tag's value different from that of
name=*
?
--JeroenHoek (talk) 17:59, 24 December 2021 (UTC)
- "There is no corresponding seamark:description=*. What is the guideline for moving descriptive names to a more suitable tag?" - see ATYL, you are free to fix mistaggings, also when it needs creation of new tags Mateusz Konieczny (talk) 00:09, 25 December 2021 (UTC)
- "Should
name=*
be used together with this tag, or only when they differ?" - if object has name then it should be tagged inname=*
Mateusz Konieczny (talk) 00:10, 25 December 2021 (UTC)seamark:information=*
.- Likely no Seamark equivalent.
- They are separate. Use both. One difference seen in Key:seamark:name#Names_of_Navigation_Objects is this will get
seamark:name=5
, while the ordinary OSM standard would beref=5
. This tag is defined as "The unique identifier of a navigation object.". - Should use
seamark:national_name=*
for that.
- Useful list in Seamarks/Seamark Attributes. ---- Kovposch (talk) 10:07, 25 December 2021 (UTC)