You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 7, 2019. It is now read-only.
I think with a hosted AGOL resource proxy, I can drop the Flask portion of this application and still use Esri premium services for the watershed and elevation profile fallback. That would vastly simplify builds, deployment, and hosting (I could even run it from a gh-pages branch here).
It would require:
a bit of work to migrate from the Flask application structure and jinja2 templates to a Jekyll structure with liquid templates.
some slight changes the javascript to remove token handling
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think with a hosted AGOL resource proxy, I can drop the Flask portion of this application and still use Esri premium services for the watershed and elevation profile fallback. That would vastly simplify builds, deployment, and hosting (I could even run it from a
gh-pages
branch here).It would require:
The text was updated successfully, but these errors were encountered: