Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I Icenet Workflow
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MARS Public
  • Icenet Workflow
  • Issues
  • #1

Closed
Open
Created Mar 08, 2022 by Owain Jones@owanesOwner0 of 9 tasks completed0/9 tasks

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, NetCDF url 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 the POST and PUT 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

Edited Mar 18, 2022 by Owain Jones
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking