Workflow for getting IceNet data onto map
This is a documentation thing which spans multiple APIs but the tricky bits are on GeoServer...
Inputs: 2 daily netCDFs (one for each hemisphere), approx 100mb each - rolling composites of ice forecast data
- API token generated with charon
-
Initial push to files API (POST), set public=true
- Successive pushes update the file content via their IDs (PUT)
-
Ingestion into GeoServer via its own API calls
- Creation of a new BAS user with the right permissions?
-
How to import?
-
From files API via URL?: Nope, NetCDFurl
only supports local files -
By mounting files API files into geoserver and accessing directly?: Nope, files API stores files gzipped, so geoserver can't read them- Do we allow writing some files as ungzipped? Would rather not - adds complexity to files API, more disk used
-
An extra API running in geoserver container?: Nope, would need to refresh on Java and how to develop a Tomcat app - An extra, hidden endpoint on the files API, to write the decompressed file to another directory, and then read that?: Seems like the quickest thing to do right now. Could also add a
?decompress=true
argument for thePOST
andPUT
arguments.
-
- (How to / do we) tell it to reproject the layer(s)?
- (How to / do we) tell it to re-import the files when they're updated?
- Creation of layers on map service which point to the tiled layers via GeoWebCache
Send details of how to do these steps to James Byrne jambyr@bas.ac.uk