akbstone / erddap-realtime-app Goto Github PK

• Will Preact work?
• Do we need a a full mapping library?
• Does deployment process eliminate unneeded code/assets?

Seems like CORS isn't turned on by default for ERDDAP. Having a CORS proxy would make it easier to try different ERDDAP installs.

This might work:
https://cors-anywhere.herokuapp.com

• get user location
• request nearby stations from erddap-parser
• display as map and/or list

Related #1

• Time frame (defaults to past 30 days?)
• Unit system?
• How to handle 'nearby' functionality

/favorites

• Create component for tagging stations as favorites
• Track saved object within session as object.
• Save station ids to cookie
• Use search to read back favorites based on IDs and display (shared component with search and history)
• Display favorite button on search/station page that allows user to fave/unfave

Look into what's needed to implement this real-time app as a Progressive Web Application.

Breadcrumbs:

StackOverflow
Google
React example

/search

• pull data from erddap using erddap-parser
• display results in endless scroll https://bvaughn.github.io/react-virtualized/ (ERDDAP REST doesn't seem to have pages available)
• link in to station pages

Tried adding these repos to package.json dependencies but it didn't work correctly. Might need to publish to NPM for this to work.

npm run build creates deployable files in /build

• dockerize
• create digitalocean account
• set up digitalocean environment 1
• integrate deployment with git 1

First pass would be pulling it in via environment var (and therefore can be set via Dockerfile/docker run argument).

Can be extended further via a dropdown or similar with known and labeled ERDDAP deployments.

/station/:id

• Create mockup/wireframe
• Pull in data using erddap-tabledapp-js
• Display sensor charts using erddap-timeseries-chart
• Display relevant station level metadata

/history

• Track stations viewed object
• Save to cookie?
• List stations viewed (shared components with search)