osm-americana/openstreetmap-americana

Rendering style for marine protected areas

Open

#54 opened on Jul 26, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (78 forks)auto 404
boundariesenhancementhelp wanted

Repository metrics

Stars
 (238 stars)
PR merge metrics
 (PR metrics pending)

Description

Many protected area boundaries cross water and land, so the styling absolutely has to contrast well with both. Using a different style for marine sanctuaries is not a solution to that problem. However, since marine sanctuaries are entirely over water a different style could look much better especially at low zoom levels.

On the coast of Massachusetts for example, there are two large protected areas. The boundary of Cape Cod National Seashore crosses land and water, but stays close to the coast. At low zoom this is barely visible and the boundary line just looks like it's on the shore. On the other hand, the boundary of Stellwagen Bank National Marine Sanctuary is entirely in the ocean. The coast of California also has many of these marine protected areas sticking far out into the ocean.

Using a blue outline where the boundary is entirely or mostly over water would be a nice cartographic effect and less distracting than a green outline in the middle of the ocean. We could also decide to simply exclude marine sanctuaries on the basis that this map style focuses on land based features.

Screen Shot 2021-07-26 at 9 47 32 AM Screen Shot 2021-07-26 at 9 47 53 AM

Originally posted by @zekefarwell in https://github.com/osm-americana/openstreetmap-americana/issues/49#issuecomment-886741275

Contributor guide

Research direction
Investigate how protected area boundaries are rendered in the map style, specifically identify the rules for marine vs. land boundaries. Consider adding a conditional style that changes border color to blue when the boundary is entirely or mostly over water, or alternatively exclude marine sanctuaries.
Tech stack
javascript
Domain
web devfrontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CSS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80