Human page
https://www.destinationcommandcenter.com/location/39.66540/-105.20570Open example →Destination Command Center · Developers
One coordinate in. Dense public context out.
Latitude and longitude are the canonical DCC location key. If you know a coordinate, you do not need to know which public weather, alert, earth, water, air-quality, event, or local source covers it. DCC selects the geographically applicable sources and returns one predictable location object.
Canonical contract
dcc-location-v2Human: /location/{lat}/{lng}
JSON: /api/location/{lat}/{lng}
Precision: 5 decimal places
Machine endpoint
https://www.destinationcommandcenter.com/api/location/39.66540/-105.20570Open JSON →Ordered response modules
Read the modules object first. DCC returns only what mapped sources can support for that coordinate.
identityCoordinate, timezone, elevation and canonical identity
nowCurrent weather and air-quality conditions
conditions12-hour weather/air outlook and three-day context
hazardsOfficial alerts, recent earthquakes and NASA natural events
waterNearby NOAA river/flood gauges when applicable
officialOfficial NWS forecast/zone context when applicable
eventsConfigured nearby event feeds when available
machineFeedsAdditional geographically mapped public machine feeds
Current core public sources
Open-Meteo weather
Open-Meteo / Copernicus CAMS air quality
U.S. National Weather Service forecasts + alerts
U.S. Geological Survey earthquakes
NASA EONET natural events
NOAA National Water Prediction Service gauges
Each response includes per-source availability and checked timestamps. DCC uses source-specific revalidation plus a short shared response cache so repeated agent reads do not hammer public upstream services.
Machine discovery
How to interpret a response
DCC aggregates time-sensitive public-source observations. Use provider names, timestamps, freshness fields, and source links when available. A missing module means DCC does not currently have a mapped usable source for that coordinate; it does not prove that the real-world condition or service is absent. Machine coordinate reads do not require reverse geocoding; a human-readable place name is optional.