osm-topology

Extract road networks from OSM data using DuckDB's OSM extension, apply GF(3) coloring to classify edges into three balanced groups, and validate connectivity and edge properties. This produces a routing-ready graph with topological constraints satisfied.

GF(3) coloring assigns one of three trit states to graph edges, balancing network structure for routing algorithms. It ensures symmetric edge properties and prevents algorithmic failures on unbalanced road networks.

Yes. DuckDB's OSM extension ingests PBF or Parquet data, extracts nodes and ways with topology fields, runs validation checks for dead-ends and self-loops, and outputs edge attributes compatible with routing queries.

Run validation checks on the colored graph to detect dead-ends, self-loops, duplicate edges, and connectivity gaps. DuckDB queries against the topology model identify and flag these issues before routing.

Ingest OSM data as PBF (Protocol Buffer Format) raw exports or pre-processed Parquet tables. Both formats integrate with DuckDB for extraction and graph construction.

Always validate before routing to catch dead-ends, disconnected nodes, and malformed edges that degrade pathfinding. Topology checks prevent query failures and ensure routing correctness across the network.