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

So I have been going on a mapping spree lately mapping the outer banks of North Carolina, but What I have begun to notice is the national park boundaries are covering up all the detail out there. Many parts of islands are simply specifically their coastlines, are covered with these giant green blobs called National Parks. Here is an example at Portsmouth Island

What is even more frustrating, is this rendering issue has already been solved, when looking at lakes around borders of national parks, we see the green get covered by the water, with only a green shaded line remaining above the water to represent the border of the national park. Here is an example at Fontana Lake. Is there anyway we can fix this, It seems like a simple fix, just get national parks over oceans to render the same way as national parks over lakes.

Is there any reason this cant be done?

I have thought of a couple work arounds, like making the border of the national parks the islands, or putting an area of water over the area affected by the green blob issue, so it would be rendered correctly, but I realized that this would be mapping for the render which is a no no.

So how do we get this fixed?

Edit: I figured out the problem, it had been labeled leisure=park I checked the description page wiki for Leisure= park and it clearly says do not label national parks with this so i think i found my answer, take the leisure=park off since its not supposed to be there any way.

asked 16 Jun '16, 02:43

Sunfishtommy's gravatar image

Sunfishtommy
1117913
accept rate: 0%

edited 16 Jun '16, 18:21

Are we talking about the "Standard" rendering? In that rendering, national parks are rendered with only a green border and no fill, and I don't see a problem in either of the linked locations (other than Great Smoky Mountains National Park being tagged as a leisure=park). Can you post a screenshot of what you consider to be a problem?

(16 Jun '16, 16:39) alester

Yea I figured out that was the problem, it had been labeled leisure=park I checked the description page wiki for Leisure= park and it clearly says do not label national parks with this so i think i found my answer, take the leisure=park off since its not supposed to be there any way.

(16 Jun '16, 18:19) Sunfishtommy

This is due to the way the OSM main map is rendered, and appears to be similar to a known, open issue: https://github.com/gravitystorm/openstreetmap-carto/issues/426. If you have ideas on how to fix, feel free to add them there. However, don't change the data just so it looks "right" according to you.

permanent link

answered 16 Jun '16, 14:01

neuhausr's gravatar image

neuhausr
7.5k870121
accept rate: 21%

Yet, matkoniecz's lastest comment "We moved to ocean polygons" sounds like this issue could be fixed. I suggest to create a new issue at https://github.com/gravitystorm/openstreetmap-carto/issues/ and mention related issue 426.

(16 Jun '16, 16:20) scai ♦
1

I figured out the problem, it had been labeled leisure=park I checked the description page wiki for Leisure= park and it clearly says do not label national parks with this so i think i found my answer, take the leisure=park off since its not supposed to be there any way.

So problem is fixed now, since leisure=park should not have been there anyway.

(16 Jun '16, 18:20) Sunfishtommy
Your answer
toggle preview

Follow this question

By Email:

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

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "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:

×440
×67
×10

question asked: 16 Jun '16, 02:43

question was seen: 2,502 times

last updated: 16 Jun '16, 18:22

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