NOTICE: is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum

Good Day. We maintain a section that has about 350 manmade piers that all have specific number associated with them. This morning I noticed that someone came along and changed the key and the name (in this case pier number) no longer displays..? I have two questions: 1.) Can I identify who made the changes? 2.) All the "Name" values are still in there, and correct, is there a way for them to display? I would prefer to keep the changes the user performed because they are more properly represent what is actually there, but not at the cost of loosing the labeling in view mode on the internet.

(One of the example ways is # 151393896 -83.45842 x 41.73366

I would really appreciate help here as I have a LOT of hours in this..

Thanks, and All the Best! Bill

asked 11 Apr '14, 14:07

Mad%20Boater's gravatar image

Mad Boater
accept rate: 0%

edited 11 Apr '14, 15:35

SK53's gravatar image

SK53 ♦

To see all changes made to a particular way you have to take a look at the corresponding way history (in this case for your way with the ID 151393896). As you can see, the last change has been done 2 years ago.

So why did the rendering change nevertheless? Because the rules defining how something is rendered are defined somewhere else: in the stylesheet of the corresponding renderer. So it is very likely that these rules did change instead of the data.

The stylesheet used for the default OSM layer is maintained at the openstreetmap-carto GitHub project. There have been some recent changes regarding the name tag which probably lead to the fact that name on man_made=pier will be ignored. This doesn't necessarily mean that this is intended behavior, it could also be a mistake. And if you think you found a bug then you can create a new issue for openstreetmap-carto (unfortunately this requires a separate GitHub account).

However I think there is a mistake in the data. In my opinion those numbers aren't names. The name tag should contain the name only. Therefore the numbers belong to the ref tag and I suggest you should fix the piers accordingly.

This won't make them appear on the map. But it fixes the map data which is of higher importance. Keep in mind that we can't show all features on the map because otherwise it would become too cluttered. But of course you can render your own map with your own customized stylesheet where ref and name on a man_made=pier are rendered.

permanent link

answered 11 Apr '14, 14:36

scai's gravatar image

scai ♦
accept rate: 23%

edited 11 Apr '14, 14:41

SomeoneElse's gravatar image

SomeoneElse ♦

You also might want to go through them all and fix the tagging. I just checked a few, and there are some that are missing the man_made=pier tag, but do have all sorts of wacky tags like amenity=parking, highway=unclassified, and waterway=dock. There are also many that don't connect to anything else, or cross another way without a node joining them. In short, there are bigger problems with the underlying data that should be resolved before worrying about how their labels render on one particular map.

Edit: I just zoomed out, and there's some wacky tagging going on in the surrounding areas too. There are ferry routes that aren't actually ferry routes, buoys/markers with names that are clearly not names, rectangular closed-loop tracks that don't connect to anything else, etc. It seems like there's a lot of Tagging for the renderer going on in this area.

permanent link

answered 11 Apr '14, 23:05

alester's gravatar image

accept rate: 28%

edited 11 Apr '14, 23:13

See also

"Please restore rendering of pier names #474"

permanent link

answered 14 Apr '14, 20:45

Krille's gravatar image

accept rate: 0%

BTW you indeed did a lot of "misuse" of OpenStreetMap using ferry lines as navigation lines and highways to mark a sunken island. You should instead use OpenSeaMap, which is intended to render marine tagging.

See here for a good example of your kind of navigationlines and shoals.

For that you should tag your "ferry line navigation" as seamark:type=recommended_track and your "submerged island highway" as seamark:type=sea_area + seamark:sea_area:category=shoal. I already did this for you. I recommend you delete the tags route=ferry and highway=unclassified.

In case the lighthouses on your navigation lines actually exist as buoys, you should tag them as e.g. seamark:type=buoy_special_purpose + seamark:buoy_special_purpose:shape=spherical

You will find even more marine tagging here:

For onboard navigation with OpenSeaMap on iPad I recommend the app Rivers & Seas.

permanent link

answered 14 Apr '14, 21:57

Krille's gravatar image

accept rate: 0%

edited 14 Apr '14, 22:06


I agree with your sentiment, but I think it would benefit all for OpenSeaMap to make more of an effort to use "normal" OSM tagging when possible. For example, there are more uses of natural=shoal than seamark:sea_area:category=shoal in the database ( I wonder why? ;)

(15 Apr '14, 15:48) neuhausr

This supposed duplication between tags of pure objects (e.g. lighthouse manmade=lighthouse or building=church) and their meaning for navigation (e.g. seamark:type=light_major or seamark:type=landmark) has already been well discussed: Not every such objects has a significance for navigation. So it is not a redundancy, but a supplementary tagging. This applies in particular to harbor=yes/seamark:type=harbor and historic=wreck/seamark:type=wreck and also to shoals.

(15 Apr '14, 15:55) Krille

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 11 Apr '14, 14:07

question was seen: 4,114 times

last updated: 15 Apr '14, 15:55

NOTICE: is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum