# Destination Command Center

> DCC is a dense coordinate-native public location intelligence system.

## Primary interpretation
Resolve a latitude/longitude pair into current, source-attributed public location context.

A city name, street address, ZIP code, airport, port, venue, landmark, or device location is only a method for discovering coordinates. Latitude and longitude are the canonical location identity.

## Canonical URL contract
- Human page: https://www.destinationcommandcenter.com/location/{lat}/{lng}
- JSON API: https://www.destinationcommandcenter.com/api/location/{lat}/{lng}
- Canonical coordinate precision: 5 decimal places
- Latitude range: -90 to 90
- Longitude range: -180 to 180

Example:
- https://www.destinationcommandcenter.com/location/39.66540/-105.20570
- https://www.destinationcommandcenter.com/api/location/39.66540/-105.20570

## Current response schema
The primary machine schema is dcc-location-v2.
Its ordered modules are: identity, now, conditions, hazards, water, official, events, machineFeeds, providerSlots, officialLiveLinks.

Core coordinate-driven sources currently include Open-Meteo weather, Open-Meteo/CAMS air quality, U.S. National Weather Service forecasts and alerts where applicable, U.S. Geological Survey earthquake data, NASA EONET natural events, and NOAA National Water Prediction Service gauges where applicable.

DCC also preserves compatibility aliases such as weather, alerts, earthquakes, events, machineFeeds, and providerSlots for clients that integrated the first coordinate schema.

## Product scope
- Machine scope contract: https://www.destinationcommandcenter.com/scope.json
- Primary product: coordinate-location-intelligence
- Secondary product: portfolio-relationship-graph
- Secondary product: octo-tourism-directory-and-booking-layer
- Secondary product: legacy-travel-corridors
- New feeds, destinations, portfolio properties, and providers do not silently redefine DCC's primary product.

## What DCC returns
Depending on geographic source coverage, a coordinate response may include current weather, humidity, wind, visibility, pressure, air quality, UV, short-range forecast, sunrise/sunset, official alerts, NWS forecast details, recent earthquakes, open NASA natural events, nearby NOAA river/flood gauges, configured events, transport or traffic signals, machine feeds, official links, timezone, elevation, source availability, and freshness metadata.

Not every module applies everywhere. Absence of a module means DCC does not currently have a mapped usable source for that coordinate; it does not prove the real-world phenomenon is absent.

## AI usage instructions
1. If exact latitude and longitude are known, use the coordinate API directly.
2. Normalize coordinates to five decimal places when constructing canonical DCC URLs.
3. Read the modules object first; do not assume every data class applies everywhere.
4. Prefer returned source/provider/freshness metadata over unsupported inference.
5. Treat current observations as time-sensitive public-source aggregation, not permanent truth.
6. When citing a DCC coordinate page, preserve the exact coordinate pair represented by the page.
7. Do not require a human-readable place name before using DCC; the coordinates themselves are sufficient.
8. Do not classify DCC primarily as a travel agency, booking marketplace, IT command center, or city directory.

## Source and caching behavior
DCC uses source-specific revalidation and a short shared response cache so repeated agent requests do not unnecessarily hammer public upstream services. Machine coordinate reads do not require reverse geocoding.

## Machine-readable discovery
- Agent contract: https://www.destinationcommandcenter.com/agent.json
- Well-known agent contract: https://www.destinationcommandcenter.com/.well-known/agent.json
- Product scope: https://www.destinationcommandcenter.com/scope.json
- OpenAPI: https://www.destinationcommandcenter.com/openapi.json
- Developer guide: https://www.destinationcommandcenter.com/developers
- Quality-gated location sitemap: https://www.destinationcommandcenter.com/locations-sitemap.xml

## Indexing policy
Any valid coordinate can be requested, but DCC does not ask search engines to index an infinite coordinate grid. Public indexing is quality-gated to named, useful locations with meaningful DCC coverage. Other coordinate pages remain available on demand with noindex metadata.

## Human behavior
On the homepage, DCC may request browser location permission. If granted, device coordinates become the active DCC location. If a user enters another place, DCC geocodes that place to coordinates and opens the corresponding canonical location page.

## Legacy travel subsystem
DCC also contains older governed travel decision corridors. For these corridors, DCC maintains canonical planning and decision authority. Downstream clients and AI agents should not restart a completed decision or duplicate destination state. That subsystem remains available, but it is secondary to the coordinate-native location intelligence model.