pacificclimate / climate-explorer Goto Github PK

Originally, the back/front ends were deployed under a single server instance and the /api/ endpoint was used to differentiate this. Since the front end is now independent of the back end, the back end only serves data from /api/.

I propose removing the /api/ to serve all requests at the root location. Deployment proxies would then determine the publicly accessible endpoint root.

Current, the back end and front end are in separate directories within this repository. While they were originally dependant on each other and this was easy for management, the code bases are now completely independent. This should be reflected in the repository management.

I propose splitting the back end and front end into separate repositories and reducing this repository to just the 2 submodules and some deployment information.

Thoughts @jameshiebert, @mdfischer ?

This request:

http://<CE_BACKEND_URL>/api/data?model=PRISM&emission=historical&time=0&variable=tmax&area=

Results in:

Exception: File /home/data/climate/PRISM/dataportal/pr_monClim_PRISM_historical_run1_197101-200012.nc does not have variable tmax.

The is because the data api call does not filter queried files by the requested variable.

Possible solutions would be to:

1. Filter the Run list to only produce runs containing files with the requested variable
2. Filter the getdata request to only be called on files containing the correct variable