For Tennnessse…
1. We need to study the raw TN data
a. Where is it?
2. Write python parser to put TN data in geostreams database
a. Figuring out what the locations (XY) are - sites
b. Figuring out what the sensors at each location are - sensors
c. Figuring out what data goes into the datapoints
d. Create site, create sensor(s) within the site, add datapoints to sensor with our API endpoints
e. https://github.com/geostreams/geostreams/tree/master/app/models
i. PostgreSQL database with an API on top
3. Look at GLTG Explore/Download pages to see how they populate OpenLayers map using geostreams datapoints
a. Some API calls to our geostreams API to fetch data on page load
b. Create map stuff - point features on the map
c. Include HUC8 boundaries for reference
4. Make the new points interactive
a. You click on a point, we have a popup with a graph of their data
Fundamental question
- Handle TN data in regular explore page?
- Make explore page handle AR data?
○ Or are we maintaining two things?
○ Default dashboard may have things we can adopt to fetch - core libraries in state dashboards
Use sensor ID to lookup data when clicked on?
For Tennnessse…
1. We need to study the raw TN data
a. Where is it?
2. Write python parser to put TN data in geostreams database
a. Figuring out what the locations (XY) are - sites
b. Figuring out what the sensors at each location are - sensors
c. Figuring out what data goes into the datapoints
d. Create site, create sensor(s) within the site, add datapoints to sensor with our API endpoints
e. https://github.com/geostreams/geostreams/tree/master/app/models
i. PostgreSQL database with an API on top
3. Look at GLTG Explore/Download pages to see how they populate OpenLayers map using geostreams datapoints
a. Some API calls to our geostreams API to fetch data on page load
b. Create map stuff - point features on the map
c. Include HUC8 boundaries for reference
4. Make the new points interactive
a. You click on a point, we have a popup with a graph of their data
Fundamental question
- Handle TN data in regular explore page?
- Make explore page handle AR data?
○ Or are we maintaining two things?
○ Default dashboard may have things we can adopt to fetch - core libraries in state dashboards
Use sensor ID to lookup data when clicked on?