Logic Cloud Geo service 01

USGS 3DEP elevation, through a small and explicit API.

Submit WGS 84 coordinates and receive bare-earth elevations with units, horizontal reference, dataset, resolution, provider, and vertical-reference metadata.

DatasetUSGS 3DEP bare earth
Nominal resolution1/3 arc-second · ~10 m
Input CRSEPSG:4326
Output unitsMeters or feet

Service contract

One point or an ordered batch.

The single-point endpoint is useful for map clicks and simple lookups. The batch endpoint accepts as many as 500 uniquely keyed coordinates and returns them in request order, making it suitable for GIS joins and profile workflows.

GET /api/v1/elevation

Latitude, longitude, and requested units.

POST /api/v1/elevations

An ordered list of keyed points, with a 500-point request maximum.

Controlled Florida comparison

Consistent with an independently extracted USGS raster profile.

A 486-point comparison against a historical USGS 1-arc-second DEM showed strong agreement. This validates workflow consistency; it does not make either DEM a surveyed benchmark.

Mean bias
+0.22 ft
Mean absolute difference
1.34 ft
RMSE between datasets
2.16 ft
Within 5 feet
96.1%

Download and learn

Reviewed Jupyter notebook examples.

Each notebook uses the public HTTPS API and keeps the request, validation, and export steps visible for adaptation.

IPYNB

Elevation API examples

A compact introduction covering one coordinate, a keyed point list, and a pandas join back to the source table.

Download notebook
IPYNB

Topographic profile

Validates ordered coordinates, batches service requests, measures WGS 84 geodesic distance, charts a profile, and exports CSV and GeoJSON.

Download notebook

Appropriate use

Returned values are samples from a digital elevation model. They are useful for mapping, screening, visualization, profiles, and reproducible analysis, but they are not surveyed spot elevations and should not replace project-specific engineering or legal surveys.