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

add elevation profiles to park unit connections #58

Open
RobLBaker opened this issue Mar 22, 2023 · 1 comment
Open

add elevation profiles to park unit connections #58

RobLBaker opened this issue Mar 22, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@RobLBaker
Copy link
Member

RobLBaker commented Mar 22, 2023

currently set_content_units gets the geographic bounding boxes of park units, but it does not get the elevational bounding boxes (lowest and highest points) of a park unit. It would be nice to include this information.

hit USGS api: https://epqs.nationalmap.gov/v1/docs

https://lpdaac.usgs.gov/resources/e-learning/getting-started-with-the-a%CF%81%CF%81eears-api-submitting-and-downloading-an-area-request/

@RobLBaker RobLBaker self-assigned this Mar 22, 2023
@RobLBaker RobLBaker added the enhancement New feature or request label Mar 22, 2023
@RobLBaker RobLBaker added the wontfix This will not be worked on label Apr 18, 2023
@RobLBaker
Copy link
Member Author

Although solvable using Amazon Web Services, trusted sources such as USGS currently do not have easy access to generating elevation minimum and maximums for polygons. Additionally, park polygons accessible via the NPS API aren't nearly as accurate as one might hope for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant