Skip to content

Commit 5f1e03a

Browse files
authored
Merge pull request #134 from NASA-IMPACT/gc/features_api_additions
Add OGC Features API to Dev/Staging API Docs
2 parents 0e29dc1 + a97952d commit 5f1e03a

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

services/apis.qmd

+12-12
Original file line numberDiff line numberDiff line change
@@ -16,19 +16,19 @@ Maintenance on the staging environment will be announced internally and selected
1616
### Staging (maintenance will be announced):
1717

1818
* STAC browser: [veda-staging-stac-browser](http://veda-staging-stac-browser.s3-website-us-west-2.amazonaws.com/)
19-
* STAC API (metadata): [https://staging-stac.delta-backend.com/docs](https://staging-stac.delta-backend.com/docs)
20-
* List collections: [https://staging-stac.delta-backend.com/collections](https://staging-stac.delta-backend.com/collections)
21-
* Raster API (tiling): [https://staging-raster.delta-backend.com/docs](https://staging-raster.delta-backend.com/docs)
22-
* STAC viewer (experimental): [https://staging-stac.delta-backend.com/index.html](https://staging-stac.delta-backend.com/index.html)
19+
* STAC API (metadata): [staging-stac.delta-backend.com/docs](https://staging-stac.delta-backend.com/docs)
20+
* List collections: [staging-stac.delta-backend.com/collections](https://staging-stac.delta-backend.com/collections)
21+
* Raster API (map tiles and timeseries): [staging-raster.delta-backend.com/docs](https://staging-raster.delta-backend.com/docs)
22+
* Features API (vector data): [firenrt.delta-backend.com](https://firenrt.delta-backend.com) - see also the [usage tutorial](../notebooks/tutorials/mapping-fires.html)
23+
* STAC viewer (experimental): [staging-stac.delta-backend.com](https://staging-stac.delta-backend.com/index.html)
2324

2425
### Development, aka Dev (experimental work, expected downtime)
2526

2627
* STAC browser: [veda-dev-stac-browser](https://dev.openveda.cloud/)
27-
* STAC API (metadata): [https://dev.openveda.cloud/api/stac/docs](https://dev.openveda.cloud/api/stac/docs)
28-
* List collections: [https://dev.openveda.cloud/api/stac/collections](https://dev.openveda.cloud/api/stac/collections)
29-
* Raster API (tiling): [https://dev.openveda.cloud/api/raster/docs](https://dev.openveda.cloud/api/raster/docs)
30-
* STAC viewer (experimental): [https://dev.openveda.cloud/api/stac/index.html](https://dev.openveda.cloud/api/stac/index.html)
31-
28+
* STAC API (metadata): [dev.openveda.cloud/api/stac/docs](https://dev.openveda.cloud/api/stac/docs)
29+
* List collections: [dev.openveda.cloud/api/stac/collections](https://dev.openveda.cloud/api/stac/collections)
30+
* Raster API (map tiles and timeseries): [https://dev.openveda.cloud/api/raster/docs](dev.openveda.cloud/api/raster/docs)
31+
* STAC viewer (experimental): [https://dev.openveda.cloud/api/stac/index.html](dev.openveda.cloud/api/stac/)
3232

3333
## Using tile layers in external services
3434

@@ -51,9 +51,9 @@ That is because, unfortunately, neither XYZ nor WMTS have time series capabiliti
5151

5252
You can see how to retrieve time steps and tile layer URLs from these tutorial Python notebooks (mostly REST API calls):
5353

54-
1. [Using /stac/tilejson.json with STAC collection and item IDs](../notebooks/datasets/ocean-npp-timeseries-analysis.qmd#visualizing-the-raster-imagery)
55-
2. [Creating layers from filters and mosaics (advanced)](../notebooks/quickstarts/hls-visualization.qmd)
54+
1. [Using /stac/tilejson.json with STAC collection and item IDs](../notebooks/datasets/ocean-npp-timeseries-analysis.html#visualizing-the-raster-imagery)
55+
2. [Creating layers from filters and mosaics (advanced)](../notebooks/quickstarts/hls-visualization.html)
5656

5757
It comes down to querying for STAC items (timesteps) and then asking the Raster API for `tilejson.json` specifications for the items you are interested in.
5858

59-
Once you retrieved the WMTS or XYZ layer URLs this way, you can use them seamlessly with all mapping clients.
59+
Once you retrieved the WMTS or XYZ layer URLs this way, you can use them seamlessly with all mapping clients.

0 commit comments

Comments
 (0)