Flux
Flux is the Earthmover Platform's data delivery service. Flux serves up your Arraylake data via standards-compliant API endpoints, making it easy to query your data and integrate it into downstream applications.
Choosing the Right Protocol
Protocol Comparison
| Feature | EDR | WMS | Tiles | DAP2 |
|---|---|---|---|---|
| Query Type | Points, polygons, trajectories | Bounding boxes, tiles | XYZ tile indices | Array slicing |
| Output Formats | JSON, CSV, NetCDF, GeoTIFF | PNG images | PNG, JPEG, WebP | Binary, ASCII |
| Best For | Data extraction & analysis | Visualization & mapping | Map tile services | Scientific tools |
| CF Convention Required | Yes (X, Y axes) | Yes (lat, lon) | Yes (CRS, coordinates) | No |
| Typical Data Size | Small (subset) | Small (tiles) | Small (256x256, 512x512 tiles) | Flexible |
| Client Complexity | Simple HTTP | Tile layer | Tile layer | OPeNDAP client |
Here is an live example using tiles to serve gust data.
Learn More
📄️ Flux Administration
In the following
📄️ Repo Doctor
The Repo Doctor is a diagnostic tool that analyzes your Arraylake repositories to ensure they are compatible with Flux services. It checks for CF convention compliance and helps you fix any issues that would prevent your data from being served through Flux protocols.
📄️ Authentication
Flux supports both authenticated and public services.
📄️ EDR: Environmental Data Retrieval
EDR is a standard of the Open Geospatial Consortium (OGC)
📄️ Tiles: Map Tiles API
The Tiles API is a standard of the Open Geospatial Consortium (OGC).
📄️ WMS: Web Map Service
WMS is a standard of the Open Geospatial Consortium (OGC)
📄️ DAP2: OPeNDAP
DAP2 (Data Access Protocol version 2) is the core HTTP protocol used by OPeNDAP (Open-source Project for a Network Data Access Protocol) for data transport and access over HTTP.
📄️ FAQ
What happens if I edit the dataset? Should I restart manually?