STAC Catalog
NUVIEW exposes its Earth observation holdings as a SpatioTemporal Asset Catalog (STAC) API — a standardized, machine-readable interface for discovering and searching geospatial data by collection, area of interest, and date range. Any STAC-compliant tool or library can connect to it directly, independent of the platform's web UI.
Catalog root: https://catalog.nuview.space
Requests over plain HTTP are redirected to HTTPS. The endpoint is publicly reachable and does not require an API key or login to browse collections or run searches — it returns standard JSON/GeoJSON to any client.
Authentication note: without an
Authorization: Bearer <token>header, requests are treated as anonymous and only return access to publicly available collections. Collections that require a NUVIEW subscription or licensed access are not visible or searchable until a valid API token is supplied on the request. Generate a token from Account Management → API Token in the platform — see Finding your API token for the full walkthrough.
What you're connecting to
The catalog conforms to the STAC API spec (stac_version 1.0.0-beta.2) plus the OGC API - Features core, and declares the following conformance classes:
ogcapi-features-1— core, OpenAPI, GeoJSONogcapi_common-2— collections- STAC API — core, item search, fields, context, sort
In practice, that means: you can list collections, fetch a single collection's schema, page through a collection's items, and run cross-collection searches filtered by space, time, and other fields — using either GET (query string) or POST (JSON body) against /search.
Key endpoints
| Endpoint | Method | Description |
|---|---|---|
/ | GET | Root catalog document — landing page, links to all collections, search, and conformance |
/conformance | GET | List of STAC/OGC API conformance classes this catalog implements |
/collections | GET | List of all available collections |
/collections/{id} | GET | Full schema for one collection, including its item_assets (bands, GSD, roles) |
/collections/{id}/items | GET | Paginated GeoJSON FeatureCollection of items in one collection |
/search | GET, POST | Cross-collection item search with spatial/temporal/attribute filters |
/api | GET | OpenAPI specification for the full service |
Quick start with curl
List every collection:
curl -s https://catalog.nuview.space/collections | jq '.collections[] | {id, title}'
Get the schema for one collection (band names, ground sample distance, roles):
curl -s https://catalog.nuview.space/collections/sentinel2_l2a | jq '.item_assets'
Search for items by collection, bounding box, and date range:
curl -s "https://catalog.nuview.space/search?collections=landsat9_oli_tirs_l2_sr&bbox=-149.9,61.1,-149.7,61.3&datetime=2024-06-01T00:00:00Z/2024-06-30T23:59:59Z&limit=10"
The same search as a POST with a JSON body (equivalent, and required for more complex filters):
curl -s -X POST https://catalog.nuview.space/search \
-H "Content-Type: application/json" \
-d '{
"collections": ["sentinel2_l2a"],
"bbox": [-149.9, 61.1, -149.7, 61.3],
"datetime": "2024-06-01T00:00:00Z/2024-06-30T23:59:59Z",
"limit": 10
}'
Common search parameters
| Parameter | Example | Notes |
|---|---|---|
collections | sentinel2_l2a | One or more collection IDs — see the reference table below |
bbox | -149.9,61.1,-149.7,61.3 | minLon,minLat,maxLon,maxLat (WGS84) |
datetime | 2024-06-01T00:00:00Z/2024-06-30T23:59:59Z | Single timestamp or an ISO-8601 interval (start/end); either side can be left open |
intersects | GeoJSON geometry | Search by an arbitrary polygon instead of a bbox (POST body) |
limit | 10 | Page size |
Pagination
Results come back with a context object (returned, limit, matched) and, when more results exist, a links entry with "rel": "next" — follow that href to fetch the next page rather than incrementing an offset yourself:
{
"href": "https://.../search?next=1566224105929,ITEM_ID,sentinel2_l2a",
"rel": "next",
"method": "GET"
}
Item and asset structure
Each search result is a standard STAC Item (GeoJSON Feature) with a properties.datetime, a footprint geometry/bbox, and an assets map keyed by band/file. Asset entries carry the direct source href — for open datasets this is frequently a link straight into the original provider's bucket (for example, s3://sentinel-s2-l2a/... for Sentinel-2), not a NUVIEW-hosted copy. Some source buckets are requester-pays; check the provider's own access terms before scripting bulk downloads.
There is no hosted HTML browser at catalog.nuview.space itself — it serves JSON/GeoJSON only (a browser-facing request without Accept: application/json gets a 406). To browse it visually, point a STAC-aware map client (see below) at the root URL.
Connecting with common tools
Python (NUVIEW's PyEOD client): for a first-party, GeoPandas-native client with the same auth model described above — plus Jupyter notebook cell magic and visualization helpers — see PyEOD.
Python (pystac-client):
from pystac_client import Client
catalog = Client.open("https://catalog.nuview.space")
search = catalog.search(
collections=["sentinel2_l2a"],
bbox=[-149.9, 61.1, -149.7, 61.3],
datetime="2024-06-01/2024-06-30",
max_items=10,
)
for item in search.items():
print(item.id, item.datetime, list(item.assets.keys()))
QGIS: the STAC API Browser plugin (or any STAC-aware data source plugin) accepts https://catalog.nuview.space as its catalog URL and will list collections and run item searches from within QGIS.
Any STAC-spec client or library — stac-browser, rustac, stackstac, GDAL's STACIT driver, and similar tools that speak the STAC API Item Search spec — should work against this endpoint without special configuration, since it implements core stac-search.
Collection ID reference
Collection IDs (used in the collections filter) don't always match the product's display name. As of this writing, the catalog exposes 28 collections:
| Collection ID | Title |
|---|---|
ak_alaska_bare_earth | Alaska - Bare Earth |
ak_alaska_digital_surface_model | Alaska - Digital Surface Model |
ak_alaska_first_return_intensity | Alaska - First Return Intensity |
ak_alaska_intensity | Alaska - Intensity |
ak_alaska_maximum_surface_height | Alaska - Maximum Surface Height |
ak_alaska_minimum_surface_height | Alaska - Minimum Surface Height |
ak_alaska_normalized_digital_surface_model | Alaska - Normalized Digital Surface Model |
ak_alaska_pointcloud | Alaska - Point Cloud |
ak_alaska_swath_separation | Alaska - Swath Separation |
landsat8_oli_l1 | Landsat-8 OLI L1 |
landsat8_oli_tirs_l1 | Landsat-8 OLI/TIRS L1 |
landsat8_oli_tirs_l2_sr | Landsat-8 OLI/TIRS L2 Surface Reflectance |
landsat8_tirs_l1 | Landsat-8 TIRS L1 |
landsat9_oli_l1 | Landsat-9 OLI L1 |
landsat9_oli_tirs_l1 | Landsat-9 OLI/TIRS L1 |
landsat9_oli_tirs_l2_sr | Landsat-9 OLI/TIRS L2 Surface Reflectance |
landsat9_tirs_l1 | Landsat-9 TIRS L1 |
mcd43a4 | MCD43A4 NBAR |
mod11a1 | MOD11A1 LST |
mod13a1 | MOD13A1 VI |
myd11a1 | MYD11A1 LST |
myd13a1 | MYD13A1 VI |
naip | NAIP |
sentinel1_l1c_grd | Sentinel-1 L1C GRD |
sentinel2_l1c | Sentinel-2 L1C |
sentinel2_l2a | Sentinel-2 L2A |
usgs_lidar_copc | USGS 3DEP Lidar Point Cloud COPC |
umbra_open_data | Umbra Open Data |
Note: this list is a live snapshot of
/collections(as seen with an anonymous, unauthenticated request) and will drift as the catalog evolves — treat it as a starting point and confirm against the endpoint itself for anything automated. 3DEP Elevation Model, documented in Earth Observation Products, was not present as its own STAC collection at the time of writing. Runcurl -s https://catalog.nuview.space/collections | jq '.collections[].id'for the current, authoritative list.
For product specs (bands, resolution, ownership) matching these collections, see Earth Observation Products.