Subbasin: Evaluate New SRAT API

[rajadain]

From Scott Haag:

Anthony and Arianna

I have been in discussion with Barry and we feel that it would be more accurate to return a null value for NHD plus catchments where we do not know the total upstream load in stead of a zero value. So for example, if a NHD plus catchment is along the Delaware River and a user runs a hotspot mapping analysis for the HUC10, the streams in the river will currently return all zeroes because we do not know the total upstream load. Barry and I want to replace these zeroes with null values, I have 2 questions about this

1. Anthony do you agree with this logic?
2. Arianna can you ingest nulls in place of zeroes from the API? The fix is straightforward on my end, in fact I have it running on our development API right now.

• [x] Get new development API URL and Key from Scott
• [x] Link a local dev version of MMW with the new SRAT API that returns NULLs
• [ ] Test the app and find and replace all errors
• [x] Find out how NULLs should be represented in the front-end (empty string, "-", something else?)
• [ ] Update UI accordingly: Per @aufdenkampe , show a medium grey stream segment on the map, and NULL in the table

[ajrobbins]

From Austin:

The endpoint for the dev server is:

https://rychrnjrs6.execute-api.us-east-1.amazonaws.com/dev/SratRunModel_DEV

The Azavea API key will work for both endpoints.