GEOAMCAN API / METHODOLOGY

Data methodology and provenance

Understand source releases, geographic coverage, uncertainty and the limits of derived analysis.

Public sources, an independent API

Geoamcan organizes public Census, Statistics Canada, BLS, BEA, HUD, FEMA, EPA, USDA and other source data. Source agencies create the underlying statistics. Geoamcan provides retrieval and supported analysis, without agency endorsement.

Releases and updates

Available datasets refer to validated active releases. Release periods and geographic vintages may differ across datasets. The live catalog reports readiness; a page’s review date does not imply that the source agency released new data that day. Updates become public after import and validation.

Geographic joins

Join by explicit geography identifiers and vintages, not names alone. A county can intersect several cities; a county statistic is not a city statistic. US geographic identifiers and Canadian DGUIDs use separate systems. Custom-area geographic analysis and market discovery currently support US areas.

Uncertainty and suppression

Retain published margins of error where available. Null, missing, suppressed and insufficient-data values do not mean zero. Match the statistical universe before deriving a percentage. Medians are not additive; only supported aggregation methods should be used.

Historical and spatial interpretation

Do not mix periods silently. Business locations differ from official establishment counts, roads are geometry rather than live traffic, and hazard indicators are not property-specific forecasts. Canadian census-profile coverage is national and provincial; Canadian population has broader geographic coverage.

Reproducibility

Save request parameters, source organization, release, period, units and geographic vintage with downstream results. Use export checkpoints and snapshot metadata for repeatable bulk workflows. See the API reference for the authoritative interface.

Questions or corrections

Send source or coverage questions through the contact form. Include the dataset and public source reference, without sending confidential API credentials.