Proper coastlines and, generated from them, land or water polygons, are essential for many maps. But it is difficult to get the coastlines mapped without any errors. This OSM Inspector view helps with finding all the errors in the coastline.
All data in this view is derived from OSM data. The OSMCoastline program is used to assemble the coastline data and all errors that show up in this process are shown in this view.
Data for the whole world is available in this view.
The most important rules are: Land is always to the left of coastline ways, water is to the right. Coastline ways can never just stop in a dead-end, they always have to be connected to another coastline (or themselves).
- It is often easier to see the errors when you switch off all the "Coastline error lines" layers and only look at the nodes.
- If a node is marked as error but you can't see any problem, select this node in JOSM by drawing a rectangle around it. In many cases you'll notice that there is either two or more nodes at the same position or a way with only a single node there. Merge the nodes and remove single-node-ways.
- Two or more ways tagged as natural=coastline on top of each other can show up in different ways. Sometimes they show up as "Overlapping lines", sometimes you see "Intersection" markers for many of the nodes. Make sure there is only ever on way tagged as coastline in the same place. Example image:
- Do not tag relations as natural=coastline, it does not work.
- In JOSM it often is useful to search for "natural=coastline". This will highlight all coastlines.
Coastline shows all ways tagged natural=coastline. This is the only layer thats not showing some kind of problem. This layer is only shown in higher zoom levels when the detail is important and drawing is faster.
Coastline error lines
Not a ring means that the coastline could not be formed into a complete closed ring. Either there aren't enough points or the coastline is not closed. This is never supposed to happen and must be fixed. Use the "Coastline error points" layers to find the specific problem and fix it.
Invalid geometry shows coastlines that are invalid for some reasons, for instance because there are self-intersections or so. This is somewhat of a catch-all, i.e. it is shown when we can't give a more specific error message. Fix all specific errors shown on some other layer on this coastline and this error should go away also.
Wrong direction shows coastlines that go in the wrong direction, i.e. the land is not on the left. This should be fixed. But be careful, this error often is the result of another error somewhere else. This can happen if there is a body of water inside a continent. If the continent has some error the body of water inside might be flagged here, but is perfectly okay. Direction errors can be fixed quickly by loading the data into JOSM, selecting the way and using the "r" key to reverse the way. Put some aerial images in the background and you can usually see immediately if a way really has the wrong direction.
Questionable shows coastline rings with possible problems. There are several different kinds of problems that are shown in this way: a) Coastline rings that touch other coastline rings in a single point. Those should probably be fixed. b) Coastline rings having the wrong direction. Those should be fixed. c) Smaller water areas inside a continent. Those should probably be changed to use natural=water or similar tags. Sometimes when there is a gap in the coastline, this will show the direct connection between the endpoints of this gap, even though there is no actual way there. Use your judgement in all these cases!
Coastline error points
Unconnected shows points where the coastline ends. This is, of course, never supposed to happen and must be fixed. Usually there is another unconnected end somewhere nearby and you can just connect them properly. Sometimes a (longer) coastline way has been deleted and there is now a larger gap in the coastline. In this case it might be best to find the deleted way and un-delete it.
Intersections show places where the coastline intersects itself. This is never allowed and must be fixed. This often happens when there was say an island somewhere that was only roughly drawn and somebody drew a better outline on top and forgot to remove the old island. The coastlines for the old and new island outline now intersect. Remove the version thats not so good. If you see many intersections right next to each other it can mean that there are two coastline ways on top of each other.
Double node shows nodes that appear more than once in a coastline. This must be fixed. Note that double nodes can also show up as some other error depending on the exact configuration.
Tagged node shows nodes that are tagged natural=coastline. Because ways and not nodes should be tagged this way, this is probably an error. This happens sometimes when a node was selected by accident when somebody wanted to add the tag to a way. Some people use this tag to mark headlands, cliffs, bays, or other features related to coastlines. Use the proper tag instead.
What you can do with this view to improve OSM data
Fix all coastline problems. Even small problems in the coastline can lead to big problems with the data. Any gap in the coastline somewhere in Siberia can mean the whole Africa-Asia-Europe continent might be broken!