Can a planning assistant explain a city’s trade-offs?

Connect housing, transport, land and construction context to prototype urban planning scenarios.

The record concepts include housing tenure, dwelling / occupancy history, residential transitions, trip / commute context, transport access, mobility events and parcel history. Review housing, transport, land and project relationships. Keep scenario parameters explicit when discussing trade-offs. Distinguish recorded facts from proposed planning scenarios.

This dataset is prepared to order. Choose the city, date range and required scope; the accepted order defines the population, final fields, formats and delivery.

Onboarded city options

Nairobi (Kenya) · Lagos (Nigeria)

Custom city requests

African Major Cities · Additional cities require availability, scope and quote confirmation.

Data type

Synthetic

Connected domains

Housing, Transport, Land, Construction

Catalogue structure

Connected longitudinal

Key features

Record concepts for your order-specific extract.

Who it is for

• Civic-tech teams
• planning labs
• urban researchers
• AI engineers

Entities represented

Area + system

This identifies the entities described by the catalogue. The analytical row grain, eligibility, keys and dates are agreed for your extract.

Explore defined housing and transport options with linked land and construction evidence.

Record concepts for your extract

• housing tenure
• dwelling / occupancy history
• residential transitions
• trip / commute context
• transport access
• mobility events
• parcel history

The agreed specification defines the final columns, keys, relationships and observation period for your order.

Provide common scenarios and reference evidence; score factual support, coverage of competing considerations and unsupported claims about future effects.

Proposed questions for your custom order

1. Can an AI compare defined housing and transport planning options using linked land and construction evidence, while separating recorded facts from scenario assumptions?
2. Can a planning assistant connect housing, travel and land context in one explanation?
3. Can an urban-planning assistant explain transport and housing trade-offs from linked records?
4. Can an assistant connect housing circumstances with travel access?
5. Can an AI assistant trace a parcel’s history before discussing development?
6. Can an AI assistant compare scenarios using only the supplied urban records?
7. Will an AI assistant identify missing evidence instead of inventing a planning conclusion?

Proposed research and analytical applications

• Task prototyping
• Evidence tracing
• Error analysis
• Controlled evaluation

Study and modeling guidance

Information available at prediction or evaluation time

Use only evidence valid and available at the agreed anchor; do not use later outcomes as features.

Comparison and evaluation

Specify comparable cohorts or held-out evaluation before reporting results.

Incomplete observation

Agree follow-up and retain incomplete observation as censored or unknown.

Data generation

FCTE synthetic city engine

Data classification

Synthetic

FCTE generation methods and published city/domain checks provide source context. The order defines the final extract and the release-specific checks, documentation and limitations supplied with it.

Known limitations

• Confirm scenario questions, reference answers and evaluation labels. The data does not certify a planning recommendation or guarantee network-level analysis.
• Synthetic records describe generated scenarios; they do not establish observed population prevalence or real-world causal effects.

Catalogue base price

$795 USD

Price basis

Base price per selected city

Availability

Prepared after order

The displayed catalogue amount is a base price per selected city. Your requested dates, population, fields, formats and usage rights determine the agreed scope and final quote. Applicable published discounts and taxes are confirmed with that quote.

Your prepared package

Your order confirms the data files, documentation, evidence, examples and release controls included in the prepared package.

• Agreed data extract
• Schema and field documentation
• Release-specific evidence and limitations
• Agreed loading or analysis examples
• Licence, manifest, checksums and delivery note

SD_RESEARCH_DATASET/
├── data/
│   ├── housing_records.parquet
│   ├── transport_records.parquet
│   ├── land_records.parquet
│   └── construction_records.parquet
├── tasks/
│   ├── task_definition.yaml
│   ├── questions.jsonl
│   ├── reference_answers.jsonl
│   └── evidence_paths.jsonl
├── evaluation/
│   ├── baseline_model.py
│   ├── metrics.json
│   └── example_notebook.ipynb
├── documentation/
│   ├── README.md
│   ├── DATA_DICTIONARY.csv
│   ├── SCHEMA.md
│   └── METHODOLOGY.md
├── evidence/
│   ├── CERTIFICATION.json
│   ├── VALIDATION_REPORT.pdf
│   └── KNOWN_LIMITATIONS.md
├── MANIFEST.json
├── CHECKSUMS.sha256
└── LICENSE.pdf

Delivery process

Confirm the cities, date range, records, formats, rights and price in writing. The order-specific extract is then prepared and supplied under the agreed payment and delivery conditions.

One secure download package for the agreed release and licensed entity.

Delivery timing, access expiry, formats and prerequisites are confirmed in the accepted order.

Support, refreshes, future releases, hosting and APIs are included only when expressly ordered.

Data Licensing Agreement · 2026-10

A non-exclusive, non-transferable licence for the named customer within the accepted scope and duration.

Permitted use

Internal research, development, testing and analytics within the accepted order.

Model training

Model training, external applications, commercial distribution and access by other legal entities must be expressly addressed in the order.

Redistribution

Raw or substantially reconstructable data cannot be resold, published or redistributed without separate written authorization.

Attribution

Preserve release provenance and applicable third-party notices. Published outputs must identify the data as synthetic.