| 1 | = About pgRouting = |
|---|
| 2 | |
|---|
| 3 | pgRouting is an extension of PostGIS and adds routing functionality to |
|---|
| 4 | PostGIS/PostgreSQL. pgRouting is a further development of pgDijkstra |
|---|
| 5 | (by Camptocamp). It is currently developed and maintained by Orkney, JAPAN. |
|---|
| 6 | |
|---|
| 7 | === pgRouting provides functions for: === |
|---|
| 8 | |
|---|
| 9 | * Shortest Path Dikstra: routing algorithm without heuristics |
|---|
| 10 | * Shortest Path A-Star: routing for large datasets (with heuristics) |
|---|
| 11 | * Shortest Path Shooting-Star: routing with turn restrictions (with heuristics) |
|---|
| 12 | * Traveling Salesperson Problem (TSP) |
|---|
| 13 | * Driving Distance calculation (Isolines) |
|---|
| 14 | |
|---|
| 15 | === Advantages of the database routing approach are: === |
|---|
| 16 | |
|---|
| 17 | * Accessible by multiple clients through JDBC, ODBC, or directly using Pl/pgSQL. |
|---|
| 18 | The clients can either be PCs or mobile devices. |
|---|
| 19 | * Uses PostGIS for its geographic data format, which in turn uses OGC's data |
|---|
| 20 | format Well Konwn Text (WKT) and Well Known Binary (WKB). This allows usage of |
|---|
| 21 | existing open data converters. |
|---|
| 22 | * Open Source software like qGIS and uDig can modify the data/attributes, |
|---|
| 23 | * Data changes can be reflected instantaneously through the routing engine. |
|---|
| 24 | There is no need for precalculation. |
|---|
| 25 | * The "cost" parameter can be dynamically calculated through SQL and its value |
|---|
| 26 | can come from multiple fields or tables. |
|---|
| 27 | |
|---|
| 28 | === pgRouting project website: === |
|---|
| 29 | |
|---|
| 30 | http://pgrouting.postlbs.org |
|---|
