Hello pgRouting community,
As a part of the FOSS4G 2022 Firenze (Italy) Codesprint,
The pgRouting Team is pleased to announce the release of pgRouting version 3.3.2
The latest release is available at [1]
For discussions on the release, go to [2]
To see all issues & pull requests closed by this release, see the Git closed milestone for 3.3.2 on Github. [3]
Revised documentation
-
Simplifying table names and table columns, for example:
-
edges instead of edge_table
-
Removing unused columns category_id and reverse_category_id.- combinations instead of combinations_table
-
Using PostGIS standard for geometry column.
-
geom instead of the_geom- Avoiding usage of functions that modify indexes, columns etc on tables.
-
Using pgr_extractVertices to create a routing topology- Restructure of the pgRouting concepts page.
Issue fixes
-
#2276: edgeDisjointPaths issues with start_vid and combinations
-
#2312: pgr_extractVertices error when target is not BIGINT
-
#2357: Apply clang-tidy performance
To update your database
Download the packaged version from your operating system, and use this command in the database:
ALTER EXTENSION pgrouting UPDATE TO “3.3.2”;
[1]. https://github.com/pgRouting/pgrouting/releases/latest
[2]. https://github.com/pgRouting/pgrouting/discussions/2359
[3]. https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%203.3.2%22
Regards,
pgRouting Team.
That’s amazing news. Congratulations to the pgRouting community.
Best regards,
Rajat
On Sun, Aug 28, 2022 at 8:50 AM Ashish Kumar <ashishkr23438@gmail.com> wrote:
Hello pgRouting community,
As a part of the FOSS4G 2022 Firenze (Italy) Codesprint,
The pgRouting Team is pleased to announce the release of pgRouting version 3.3.2
The latest release is available at [1]
For discussions on the release, go to [2]
To see all issues & pull requests closed by this release, see the Git closed milestone for 3.3.2 on Github. [3]
Revised documentation
-
Simplifying table names and table columns, for example:
-
edges instead of edge_table
-
Removing unused columns category_id and reverse_category_id.- combinations instead of combinations_table
-
Using PostGIS standard for geometry column.
-
geom instead of the_geom- Avoiding usage of functions that modify indexes, columns etc on tables.
-
Using pgr_extractVertices to create a routing topology- Restructure of the pgRouting concepts page.
Issue fixes
-
#2276: edgeDisjointPaths issues with start_vid and combinations
-
#2312: pgr_extractVertices error when target is not BIGINT
-
#2357: Apply clang-tidy performance
To update your database
Download the packaged version from your operating system, and use this command in the database:
ALTER EXTENSION pgrouting UPDATE TO “3.3.2”;
[1]. https://github.com/pgRouting/pgrouting/releases/latest
[2]. https://github.com/pgRouting/pgrouting/discussions/2359
[3]. https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%203.3.2%22
Regards,
pgRouting Team.
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/pgrouting-dev