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

[Feature Request]: Make us of non-administrative boundary files #1248

Open
wadhwamatic opened this issue May 15, 2024 · 0 comments
Open

[Feature Request]: Make us of non-administrative boundary files #1248

wadhwamatic opened this issue May 15, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request triage to be triaged for next action

Comments

@wadhwamatic
Copy link
Member

Provide a clear and concise description of what you want to happen.

In some cases, there can be boundary files that are not administrative boundaries. This includes groupings such as agro-ecological zones, livelihood zones, or watersheds / drainage basins.

As a PRISM user, I want to be able to:

  1. Optionally visualize boundaries / polygon layers that are not displayed by default so that I can see climate layers in relationship to locations beyond administrative areas
  2. Create zonal stats using the run analysis feature for non-administrative area polygons

During the PRISM configuration process, I want to be able:

  1. Add a new layer with type boundary in layers.json using the same process as admin boundary layers
  2. In prism.json, add a new set of layers called additionalLayers which is an array of layers that are hidden from the UI until a user activates them

One suggestion to show these layers in the UI is to place them at the bottom of the legend section. I think this is clearer than adding them to the left side panel since they are non-standard layers. Here's a quick mockup:
Screenshot 2024-05-14 at 16 56 37

Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.

I have added a basin_boundaries layer as type boundary here: #1247

@wadhwamatic wadhwamatic added enhancement New feature or request triage to be triaged for next action labels May 15, 2024
@wadhwamatic wadhwamatic self-assigned this May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage to be triaged for next action
Projects
None yet
Development

No branches or pull requests

1 participant