-
Notifications
You must be signed in to change notification settings - Fork 831
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
natural=coastline renders name along shore/coastline #38
Comments
Likely not a carto port issue, but the yevaud database having fewer ways (coastline ways are normally dropped) http://www.openstreetmap.org/browse/relation/1205139 may be the offending relation. That relation seems to duplicate geodata. |
@pnorman So, what then needs to be done to fix this ? Will this problem also occur when osm-carto is used as the stylesheet on osm.org instead of the mapnik.xml ? |
the best solution seems to be to delete relation 1205139 as I don't see that the carto rendering is wrong. |
The issue appears to be more complex than I first thought. The offending item in the DB is in the planet_osm_polygon table with
In errol's DB it is a ST_Polygon and in @skorasaurus DB it is a ST_MultiPolygon. Both report true for ST_IsValid. This MP may of not been fully in the extract he used. It seems to me there are three issues
The EWKT for the ST_MultiPolygon from skorasaurus' DB is
(reformatted with whitespace) The EWKT from errol's DB is 1.7 MB. |
For what it's worth, this problem isn't on @iandees ' |
So by the sounds of it, there's no problem with this on the main servers, since full planets lead to (multi-)polygons in the database. Am I correct? In any case, the underlying cause is #1 which is causing the unwarranted / unwanted labelling in the first place, regardless of any unexpected output from osm2pgsql. |
Would #1 label area features as well as linear features? These are in the DB as area features |
Closing in favour of other tickets |
On z15+, name of a lake (which, because it's very large, is tagged as natural=coastline) is displayed along its edge, as shown in this image instead of being within the body of water.
Here it is on osm
This may be the result of using different coastline files being used in osm-carto and on the main mapnik server.
The text was updated successfully, but these errors were encountered: