Reporting Problems¶

Bugs are reported and managed in an issue tracker. Please follow these steps:

1. Search the tickets to see if your problem has already been reported. If so, add any extra context you might have found, or at least indicate that you too are having the problem. This will help us prioritize common issues.
2. If your problem is unreported, create a new issue for it.
3. In your report include explicit instructions to replicate your issue. The best tickets include the exact SQL necessary to replicate a problem.
4. If you can test older versions of PostGIS for your problem, please do. On your ticket, note the earliest version the problem appears.
5. For the versions where you can replicate the problem, note the operating system and version of pgRouting, PostGIS and PostgreSQL.
6. It is recommended to use the following wrapper on the problem to pin point the step that is causing the problem.

SET client_min_messages TO debug;
  <your code>
SET client_min_messages TO notice;

Mailing List and GIS StackExchange¶

There are two mailing lists for pgRouting hosted on OSGeo mailing list server:

• User mailing list: http://lists.osgeo.org/mailman/listinfo/pgrouting-users
• Developer mailing list: http://lists.osgeo.org/mailman/listinfo/pgrouting-dev

For general questions and topics about how to use pgRouting, please write to the user mailing list.

You can also ask at GIS StackExchange and tag the question with pgrouting. Find all questions tagged with pgrouting under http://gis.stackexchange.com/questions/tagged/pgrouting or subscribe to the pgRouting questions feed.

Commercial Support¶

For users who require professional support, development and consulting services, consider contacting any of the following organizations, which have significantly contributed to the development of pgRouting: