City2Graph
The City2Graph tab builds heterogeneous urban graphs from real-world data: buildings, streets, amenities, and transit, connected by morphological, proximity, and metapath relationships.
The root City2Graph panel is a status header. It reports the active object’s type (OSMnx network, City2Graph features, tessellation, morphological graph, or travel graph) and its feature/node/edge counts. OSMnx street networks can be used directly by every City2Graph operation, so the two tabs are designed to be used together.
Panels in this tab
| Panel | What it does |
|---|---|
| Data Import | Acquire the raw layers: Overture/OSMnx features, local files, GTFS transit. |
| Urban Morphology | Build tessellations and morphological building/street graphs. |
| Transportation | Turn a loaded GTFS feed into travel-summary and OD graphs. |
| Mobility (OD Matrix) | Build graphs from an external origin-destination matrix. |
| Graph Tools | Clip, filter, isochrone, and largest-component utilities. |
| Proximity Graphs | Spatial networks (KNN, radius, Delaunay…) over feature objects. |
| Metapath Analysis | Connect amenities through the street network. |
| GeoAI Export | Export graphs for GNN training (JSON/GraphML, PyG loader). |
Header status fields
When a compatible object is active, the header reports:
| Field | Meaning |
|---|---|
| Object | Name of the active object. |
| Features | Feature count for City2Graph feature objects. |
| Nodes / Edges | Node and edge counts for graph objects. |
| Type | Detected type: OSMnx Street Network, Urban Tessellation, Morphological Graph, or Travel Graph. |
If nothing compatible is selected, the header invites you to import data with the panels below.
Most operations align their output with the active OSMnx graph when one is present, so downloaded features, dual graphs, bridges, and metapaths all share the same coordinate space as the street network.