e-Stat (Japan): This service uses API functions from e-Stat, but the Government of Japan does not guarantee the contents.
India (data.gov.in): State-level coverage for India is prepared, and it will be added once source access is finalized.
Destatis (Germany): German state-level coverage is prepared, and it will be added once source access is finalized.
Geographic Model
EconData uses a three-level geographic hierarchy: Countries, States & Regions (provinces, prefectures, states), and Districts & Counties (counties, departments, and similar local units).
Each geography stores a geoTypeLabel reflecting the local naming convention. The platform does not assume every country uses the same administrative structure.
Not every country has subnational data. Coverage badges show what level of data is actually available today.
Provenance
Every datapoint preserves source metadata including provider name, dataset, series code, source URL, methodology URL, retrieval timestamp, and caveats.
When multiple providers report the same indicator for the same geography and time, the platform does not silently flatten those values into one number. Conflicts remain traceable.
Source Conflict Detection
During ingestion, the platform compares values across providers for the same indicator, geography, and date. If values differ beyond a configured threshold, a Source Conflict record is created.
In the UI, those appear as source-disagreement warnings with metadata preserved for auditing.
Revision Tracking
Economic datasets are regularly revised. When a provider updates a previously stored value, EconData keeps track of that change instead of pretending the old observation never existed.
Subnational Comparability
Comparing subnational units across countries requires caution. Definitions of unemployment, GDP, GVA, and related indicators can differ between statistical agencies.
EconData preserves those differences in metadata and surfaces comparability notes when needed.
Current Limitations
Subnational coverage remains uneven by country and provider.
Live provider status is listed above from the current provider registry and coverage summary.
Some providers are implemented in code but still depend on ingestion runs or API access.
Data freshness depends on provider release schedules and platform refresh timing.