# pgRouting/pgrouting

Repository contains pgRouting library. Development branch is "develop", stable branch is "master"

Repository: https://github.com/pgRouting/pgrouting
Canonical: https://ross.abutalabs.com/products/pgrouting
Homepage: https://pgrouting.org
Language: C++
License: GPL-2.0
License Family: copyleft
Topics: postgis, postgresql-extension, routing, spatial-analysis, network-analysis, osgeo
Last push: 2026-08-22T12:20:18+00:00

## Health v2 (maintenance only)
Score: 84/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 56, longevity 100
- inputs: {"age_days": 5781, "days_push": 11, "days_rel": 214, "gap_med": 40, "n_releases_24m": 8}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1426, forks 395 (observed 2026-08-28T04:04:41.702521+00:00)

## What it is
pgRouting is a C/C++ PostgreSQL extension that adds geospatial routing and network analysis functions on top of PostGIS/PostgreSQL. It provides shortest path algorithms (Dijkstra, A*, bidirectional), driving distance, k-shortest paths, and traveling salesperson computations executed directly in the database via SQL.

## Use cases
- compute shortest driving routes between addresses in a PostGIS database
- find service areas and driving distance isochrones from a point
- solve traveling salesperson routes over a set of stops
- run network analysis on road networks stored in PostgreSQL
- calculate k alternative routes between two locations
- apply dynamic cost functions via SQL for time-dependent routing

## When to choose
- your road network data already lives in PostGIS/PostgreSQL and you want routing without exporting it
- you need routing results combined with SQL queries and live data updates without precalculation
- you want network analysis (driving distance, TSP, turn restrictions) inside the database

## When to avoid
- you need turn-by-turn navigation with real-time traffic like a consumer routing engine
- you are not using PostgreSQL/PostGIS
- you need a standalone routing server with a REST API rather than SQL functions

## Facets
- artifact type: library
- maturity: stable
- function: routing, geospatial, database, search-engine
- domain: databases
- platform: windows, cross-platform, self-hosted
- tags: postgresql-extension, postgis, shortest-path, network-analysis, spatial-analysis, dijkstra, osgeo, sql, maps, geospatial, algorithms, linux, macos

## Member repositories
- pgRouting/pgrouting (main) score 84

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:41.702521+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:37:28.222687+00:00, confidence not recorded.
  - readme: https://github.com/pgRouting/pgrouting (fetched 2026-08-28T04:04:41.702521+00:00, sha e8cb308a00ab)
  - homepage: https://pgrouting.org (fetched 2026-08-29T11:49:15.815102+00:00, sha f9c412be1efc)
  - site_page: https://pgrouting.org/documentation.html (fetched 2026-08-29T11:49:15.824632+00:00, sha 80799f53203c)
- Data as of 2026-08-30T08:39:29.467469+00:00.