Skip to content
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

Maybe should not render big protected areas #6063

Closed
naoliv opened this issue Sep 18, 2018 · 7 comments
Closed

Maybe should not render big protected areas #6063

naoliv opened this issue Sep 18, 2018 · 7 comments
Assignees

Comments

@naoliv
Copy link
Contributor

naoliv commented Sep 18, 2018

Have this big protected area https://www.openstreetmap.org/way/179088159

In OSM nothing is rendered at this location, for example: https://www.openstreetmap.org/#map=15/-22.5542/-47.9021

But in osmand the screen is filled with light-green P icons:

Maybe areas like this should not be rendered at all? (to avoid filling all the map with green P icons)

@hakuchi
Copy link
Contributor

hakuchi commented Sep 18, 2018

I found a other protected area(https://www.openstreetmap.org/relation/3547850), and it looks similar to the area from your link.
In OsmAnd this is not rendered. I dont know if this is because this is a multipolygon, or for the protect_class=5 tagging.

Can you test the rendering if you add protect_class=5 to your area?

@IgorEliezer
Copy link
Contributor

IgorEliezer commented Sep 18, 2018

Hey @naoliv, that "big protected area" is very close to the region I'm mapping, so in your homage I created another: APA Tietê. :)

This kind of protected area (protect_class=5) is less restrict than those full protected areas (protect_class=1 to 3). I lived there for a few years, you can do pretty much everything in a normal life except there are some restrictions as to farms, woods and specific sites. So I believe it's not necessary to render "P" icons everywhere unless the area is fully protected.

EDIT: Test result in the following post.

@IgorEliezer
Copy link
Contributor

IgorEliezer commented Sep 19, 2018

Update: it took a while to update the map to test how the protected area that I added would turn out.

The protected area (r8712428) is a boundary relation that shares their limits with the administrative boundaries of two municipalities. The result:

  1. No "P" icons (in reference to @hakuchi reply).
  2. The administrative boundaries included in the protected area relation vanished.
  3. Every segment of the protected area boundary has now a Ⓟ POI icon while one instance of such icon was supposed to be at the barycenter of the protected area.
  4. OSM Relation Analyzer says it is ok.

https://www.openstreetmap.org/relation/8712428#map=17/-23.04835/-47.79215
screenshot_2018-09-19-00-18-42

https://www.openstreetmap.org/relation/8712428#map=13/-23.1171/-47.6111
image

@vshcherb vshcherb added this to the Future milestone milestone Sep 19, 2018
@comradekingu
Copy link
Contributor

What is it meant to protect?

@IgorEliezer
Copy link
Contributor

What is it meant to protect?

Mostly scenic landscape and historical sites (18th and 19th century). There are some governamental programs and laws towards environment restoration and sustainable agricultural, forestry and tourism while it allows anthropic interaction.

https://www.iucn.org/theme/protected-areas/about/protected-areas-categories/category-v-protected-landscapeseascape

@xmd5a2
Copy link
Contributor

xmd5a2 commented Oct 2, 2018

@IgorEliezer regarding your example near Rio Tiete. Protected areas with protect_level>=5 are not rendered by design https://github.com/osmandapp/OsmAnd-resources/blob/master/obf_creation/rendering_types.xml#L5152
Also I can't confirm that admin_level boundaries are vanished. Do you use OsmAnd Live?
screenshot from 2018-10-02 17-02-23

xmd5a2 added a commit to osmandapp/OsmAnd-resources that referenced this issue Oct 3, 2018
@xmd5a2
Copy link
Contributor

xmd5a2 commented Oct 4, 2018

Main issue is fixed but issue regarding POI data is created #6134

@xmd5a2 xmd5a2 closed this as completed Oct 4, 2018
@vshcherb vshcherb modified the milestone: Future milestone Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants