Open urban research infrastructure

Observe. Measure. Understand.

UrbanProbe publishes urban datasets, indicators, and methods as infrastructure that researchers and cities can inspect and reuse. Every resource carries its geography, provenance, processing, licence, and known limitations.

Three registries

Urban evidence with context.

Each registry lists public resources of one kind. A resource is a documented release, not a download link: it states where the data came from, how it was processed, what it covers, and where it should not be used.

Resource standard

What every resource documents.

Six fields are common to all three registries. Each registry adds fields specific to its kind.

Geography & time geography_time
Spatial extent, spatial unit or resolution, time span, and update cadence.
Provenance provenance
Original sources, how they were obtained, and the rights attached to them.
Processing processing
Every step between the source and the released resource, with the code that performs it.
Validation validation
How the resource was checked, against what, and the results of those checks.
Limitations limitations
Known gaps, biases, and misuse risks.
Licence, access & citation version license access links citation
The licence of the release, any access conditions, what may not be redistributed, a version, and how to cite the resource.
Principles

Context before download.

Provenance is part of the dataA resource without its sources and processing history is not released.
Indicators are defined, not only computedEvery indicator states what it is meant to measure and how well it does so.
Methods run end to endA method is released with the inputs, environment, and example needed to reproduce it.
Limits are stated up frontCoverage gaps, biases, and inappropriate uses are documented where people will read them.
Release process

From observation to resource.

CollectRecord every source, its rights, and how it was obtained before any processing starts.
ProcessScript each step so the release can be regenerated from the sources.
ValidateCheck coverage, consistency, and agreement with reference data; keep the results.
Document & releaseFill the resource card, assign a version and licence, and add the entry to the registry.
Repository

Releases are tracked in the open.

Resource cards, processing code, and validation results live in the public repository. Proposals, data requests, and corrections are handled as issues.

View the repository