[SAC] [OSGeo] #2784: Incubation request: pgRouting
OSGeo
trac_osgeo at osgeo.org
Mon Nov 7 17:14:31 PST 2022
#2784: Incubation request: pgRouting
-----------------------+------------------------
Reporter: cvvergara | Owner: jive
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: Incubator | Resolution:
Keywords: |
-----------------------+------------------------
Description changed by robe:
Old description:
> 1. Please provide the name and email address of the principal Project
> Owner.
> * name: Celia Virginia Vergara Castillo
> * email: vicky at georepublic.de
>
> 2. Please provide the names and emails of co-project owners (if any).
> * name: Daniel Kastl
> * email: daniel at georepublic.de
>
> 3. Please provide the names, emails and entity affiliation of all
> official committers
>
> Daniel Kastl
> * email: daniel at georepublic.de
> * affiliation: Georepublic
>
> Celia Virginia Vergara Castillo
> * email: vicky at georepublic.de
> * affiliation: Georepublic
>
> Rajat Shinde
> * email: rajatshinde2303 at gmail.com
> * Affiliation: PhD Candidate at IIT Bombay
>
> Regina Obe
> * email: lr at corp.us
> * Affiliation: Paragon corporation
>
> Cayetano Benavent
> * email: cayetano at carto.com
> * Affiliation: CARTO
>
> Ashish Kumar
> * email: ashishkr23438 at gmail.com
> * Student, Banaras Hindu University
>
> 4. Please describe your Project.
>
> * name: pgRouting
> * URL: https://pgrouting.org/
> * Description:
>
> pgRouting extends the PostGIS / PostgreSQL geospatial database to
> provide geospatial routing functionality.
>
> * History:
>
> pgRouting is the successor of pgDijkstra, a first routing function
> implementation by Camptocamp, which was extended with additional
> functionality by Orkney and renamed to pgRouting. After moving to Github
> and yearly participation in GSoC the project was steadily growing its
> community and user base.
>
> * Participations:
>
> pgRouting is an active participating organization in the Google Summer
> of Code under the OSGeo umbrella and has mentored multiple contributors
> to commence their open source journey. Some of the contributors
> progressed to accept bigger roles and responsibilities in the OSGeo’s
> GSoC team and in corporate sector. Recently, pgRouting also participated
> as a mentoring organization for the United Nations OSGeo Open Education
> 2021 Initiative under pgRouting Workshop. This initiative lead to
> contribution to the UN SDGs by documenting the applications involoving
> pgRouting.
>
>
> 5. Why is hosting at OSGeo good for your project?
>
> Joining the OSGeo Foundation gives assurance to the users that the
> project will remain with an appropriate license for it to remain Free
> Open Source Software.
>
> It is not that we are looking for the project's code to be hosted, but
> the code is currently on [https://github.com/pgRouting/pgrouting github],
> but there are plans to create a mirror on OSGeo's gitea.
>
> 6. Type of application does this project represent(client, server,
> standalone, library, etc.):
>
> It is a library in form of a postgres extension.
>
> 7. Please describe any relationships to other open source projects.
> * [https://www.postgis.net/ PostGIS] Required by pgRouting to be able to
> use geometries on graph algorithms.
> * [https://www.openstreetmap.org OSM] Open data usable by pgRouting with
> the [https://github.com/pgRouting/osm2pgrouting/wiki osm2pgrouting]
> converter tool.
> * [https://qgis.org QGIS] Visualization of pgRouting results with
> [https://plugins.qgis.org/plugins/pgRoutingLayer/ pgRoutingLayer] plugin.
> * [https://www.mobilitydb.com/ MobilityDB] trajectory data management for
> timed routes
> * [https://vrp.pgrouting.org/v0/ vrpRouting] extends the pgRouting
> geospatial database to provide geospatial routing for vehicle routing
> problems.
> * [https://live.osgeo.org/ OSGeoLive] The pgRouting
> [https://workshop.pgrouting.org/ workshop] is based on OSGeoLive data.
>
> 8. Please describe any relationships with commercial companies or
> products.
> * [https://georepublic.info/en/ Georepublic] Technical and financial
> supporter
> * [https://www.paragoncorporation.com/ Paragon Corporation] Technical
> supporter
>
> 9. Which open source license(s) will the source code be released under?
> * [https://github.com/pgRouting/pgrouting/blob/main/LICENSE GNU GENERAL
> PUBLIC LICENSE Version 2]
> * For documentation: CC BY-SA 3.0
>
> 10. Is there already a beta or official release?
>
> In September 2013 the
> [https://github.com/pgRouting/pgrouting/releases/tag/pgrouting-2.0.0
> v.2.0.0] was considered as the first stable release. There was a two year
> period with little to no visible activity due to the fact that the code
> did not follow specifiic standards, and an action plan was being
> developed. In September 2015,
> [https://github.com/pgRouting/pgrouting/releases/tag/pgrouting-2.1.0
> v2.1.0] was released as the first step of standardizing code. Since then
> normally twice per year there is a new minor version released.
> The policy for releases is in this
> [https://github.com/pgRouting/admin/blob/master/RFC/RFC2.md RFC2] and all
> the [https://github.com/pgRouting/pgrouting/releases releases] can be
> tracked on the pgRouting Github repository.
>
> 11. What is the origin of your project (commercial, experimental, thesis
> or other higher education, government, or some other source)?
>
> pgRouting is the successor of pgDijkstra, a first routing function
> implementation by Camptocamp, which was extended with additional
> functionality by Orkney and renamed to pgRouting. After moving to Github
> and yearly participation in GSoC the project was steadily growing its
> community and user base.
>
> 12. Does the project support open standards? Which ones and to what
> extent? (OGC, w3c, ect.) Has the software been certified to any standard
> (CITE for example)? If not, is it the intention of the project owners to
> seek certification at some point?
>
> No. OGC currently has drafts for the route core:
> https://docs.ogc.org/DRAFTS/21-000.html and the route exchange model
> https://docs.ogc.org/DRAFTS/21-001.html but those are geometry based and
> pgRouting algorithms do not use geometries. pgRouting has utility
> functions that allow geometries to be adjusted to the graph topology
> needed by pgRouting functions.
>
> 13. Is the code free of patents, trademarks, and do you control the
> copyright?
>
> Yes it is free of patents, trademarks, and the copyright is controlled.
>
> 14. How many people actively contribute (code, documentation, other?) to
> the project at this time?
>
> The complete list of contributors can be found:
> * pgRouting: https://github.com/pgRouting/pgrouting/graphs/contributors
>
> Additionally for pgRouting support:
> * osm2pgRouting:
> https://github.com/pgRouting/osm2pgrouting/graphs/contributors
> * pgRoutingLayer:
> https://github.com/pgRouting/pgRoutingLayer/graphs/contributors
> * workshop: https://github.com/pgRouting/workshop/graphs/contributors
> * vrpRouting: https://github.com/pgRouting/vrprouting/graphs/contributors
>
>
> 15. How many people have commit access to the source code respository?
>
> pgRouting has 9 teams, depending on the team the commit access is to
> one or more repositories. For the pgRouting repository there are 24 team
> members: https://github.com/pgRouting/pgrouting/people
>
> 16. Approximately how many users are currently using this project?
>
> The numbers we can find to give an idea are
>
> * 341 forks https://github.com/pgRouting/pgrouting/network/members
> * 69 people are watching the project
> * 916 people have starred the project
> * 301 subscribers on the user’s mailing list
> * 148 subscribers on the developers mailing list
> * Its been (that we know of) packaged for:
> * [https://packages.debian.org/search?keywords=pgrouting debian]
> *
> [https://download.postgresql.org/pub/repos/yum/14/fedora/fedora-36-x86_64/
> fedora]
> *
> [https://download.postgresql.org/pub/repos/yum/14/redhat/rhel-9-x86_64/
> redhat]
> * [https://formulae.brew.sh/formula/pgrouting macos]
> * [https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes
> /postgresql-versions.html#postgresql-versions-version143 Amazon AWS
> PostgreSQL RDS] and
> [https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Extensions.html
> Aurora]
> * [https://cloud.google.com/sql/docs/postgres/extensions Google SQL for
> PostgreSQL include pgRouting 3.3+]
> * [https://techcommunity.microsoft.com/t5/azure-database-for-postgresql
> /introducing-support-for-pgrouting-and-plv8-extensions-in/ba-p/3552072
> Microsoft Azure Flexible Server for PostgreSQL] and
> [https://learn.microsoft.com/en-us/azure/postgresql/single-server
> /concepts-extensions Microsoft Azure for PostgreSQL]
>
> 17. What type of users does your project attract (government, commercial,
> hobby, academic research, etc. )?
>
> pgRouting targets developers and database administrators, many of them
> being users of PostGIS as well. There is no specific industry target.
> pgRouting is used from academia to government, from system integrator to
> cloud providers. pgRouting is also inclined towards the idea of “giving
> it back” by welcoming and mentoring new developers and contributors to
> the project and community in multiple roles and capabilities.
>
> 18. If you do not intend to host any portion of this project using the
> OSGeo infrastructure, why should you be considered a member project of
> the OSGeo Foundation?
>
> About using OSGeo resources, we are using some, like
> [http://download.osgeo.org/pgrouting/ download] and the
> [https://lists.osgeo.org/mailman/listinfo/pgrouting-users user] and
> [https://lists.osgeo.org/mailman/listinfo/pgrouting-dev developers]
> mailing lists.
>
> As mentioned before, the code is currently on
> [https://github.com/pgRouting/pgrouting github], but there are plans to
> create a mirror on OSGeo's gitea.
>
> 19. Does the project include an automated build and test?
> * https://github.com/pgRouting/pgrouting/actions
>
> Tested for:
> * Operative systems:
> * windows
> * Ubuntu
> * macos
> * Compilers & dependencies
> * clang
> * g++
> * boost
> * Check documentation links: Validity of the documentation links
> * update: Update from previous versions within the same mayor
> * [https://github.com/pgRouting/pgrouting/actions/runs/2658249812 check
> files]
> * Signature check: Checks that the signatures of the user-facing
> functions remain stable * within the same mayor.
> * News check: Chacks that the news are updated accordingly
> * License check: checks that the code has the license.
> * Shell check & style check: Verify that the code follows a basic
> coding standard.
>
> 20. What language(s) are used in this project? (C/Java/perl/etc)
>
> * Main: C, C++, SQL
> * For some tasks: python, perl
>
> 30. What is the dominant written language (i.e. English, French, Spanish,
> German, etc) of the core developers?
>
> Communication takes place in English
>
> 31. What is the (estimated) size of a full release of this project?
>
> From [https://packages.debian.org/bullseye/postgresql-13-pgrouting
> debian]:
>
> * Architecture amd64
> * Package Size 711.3 kB
> * Installed Size 2,978.0 kB
>
> 32. How many users do you expect to download the project when it is
> released?
>
> It's already released, but I would think that with each next release,
> the number of users would increase.
New description:
1. Please provide the name and email address of the principal Project
Owner.
* name: Celia Virginia Vergara Castillo
* email: vicky at georepublic.de
2. Please provide the names and emails of co-project owners (if any).
* name: Daniel Kastl
* email: daniel at georepublic.de
3. Please provide the names, emails and entity affiliation of all official
committers
Daniel Kastl
* email: daniel at georepublic.de
* affiliation: Georepublic
Celia Virginia Vergara Castillo
* email: vicky at georepublic.de
* affiliation: Georepublic
Rajat Shinde
* email: rajatshinde2303 at gmail.com
* Affiliation: PhD Candidate at IIT Bombay
Regina Obe
* email: lr at corp.us
* Affiliation: Paragon corporation
Cayetano Benavent
* email: cayetano at carto.com
* Affiliation: CARTO
Ashish Kumar
* email: ashishkr23438 at gmail.com
* Student, Banaras Hindu University
4. Please describe your Project.
* name: pgRouting
* URL: https://pgrouting.org/
* Description:
pgRouting extends the PostGIS / PostgreSQL geospatial database to
provide geospatial routing functionality.
* History:
pgRouting is the successor of pgDijkstra, a first routing function
implementation by Camptocamp, which was extended with additional
functionality by Orkney and renamed to pgRouting. After moving to Github
and yearly participation in GSoC the project was steadily growing its
community and user base.
* Participations:
pgRouting is an active participating organization in the Google Summer
of Code under the OSGeo umbrella and has mentored multiple contributors to
commence their open source journey. Some of the contributors progressed to
accept bigger roles and responsibilities in the OSGeo’s GSoC team and in
corporate sector. Recently, pgRouting also participated as a mentoring
organization for the United Nations OSGeo Open Education 2021 Initiative
under pgRouting Workshop. This initiative lead to contribution to the UN
SDGs by documenting the applications involoving pgRouting.
5. Why is hosting at OSGeo good for your project?
Joining the OSGeo Foundation gives assurance to the users that the
project will remain with an appropriate license for it to remain Free Open
Source Software.
It is not that we are looking for the project's code to be hosted, but
the code is currently on [https://github.com/pgRouting/pgrouting github],
but there are plans to create a mirror on OSGeo's gitea.
6. Type of application does this project represent(client, server,
standalone, library, etc.):
It is a library in form of a postgres extension.
7. Please describe any relationships to other open source projects.
* [https://www.postgis.net/ PostGIS] Required by pgRouting to be able to
use geometries on graph algorithms.
* [https://www.openstreetmap.org OSM] Open data usable by pgRouting with
the [https://github.com/pgRouting/osm2pgrouting/wiki osm2pgrouting]
converter tool.
* [https://qgis.org QGIS] Visualization of pgRouting results with
[https://plugins.qgis.org/plugins/pgRoutingLayer/ pgRoutingLayer] plugin.
* [https://www.mobilitydb.com/ MobilityDB] trajectory data management for
timed routes
* [https://vrp.pgrouting.org/v0/ vrpRouting] extends the pgRouting
geospatial database to provide geospatial routing for vehicle routing
problems.
* [https://live.osgeo.org/ OSGeoLive] The pgRouting
[https://workshop.pgrouting.org/ workshop] is based on OSGeoLive data.
8. Please describe any relationships with commercial companies or
products.
* [https://georepublic.info/en/ Georepublic] Technical and financial
supporter
* [https://www.paragoncorporation.com/ Paragon Corporation] Technical
supporter
9. Which open source license(s) will the source code be released under?
* [https://github.com/pgRouting/pgrouting/blob/main/LICENSE GNU GENERAL
PUBLIC LICENSE Version 2]
* For documentation: CC BY-SA 3.0
10. Is there already a beta or official release?
In September 2013 the
[https://github.com/pgRouting/pgrouting/releases/tag/pgrouting-2.0.0
v.2.0.0] was considered as the first stable release. There was a two year
period with little to no visible activity due to the fact that the code
did not follow specifiic standards, and an action plan was being
developed. In September 2015,
[https://github.com/pgRouting/pgrouting/releases/tag/pgrouting-2.1.0
v2.1.0] was released as the first step of standardizing code. Since then
normally twice per year there is a new minor version released.
The policy for releases is in this
[https://github.com/pgRouting/admin/blob/master/RFC/RFC2.md RFC2] and all
the [https://github.com/pgRouting/pgrouting/releases releases] can be
tracked on the pgRouting Github repository.
11. What is the origin of your project (commercial, experimental, thesis
or other higher education, government, or some other source)?
pgRouting is the successor of pgDijkstra, a first routing function
implementation by Camptocamp, which was extended with additional
functionality by Orkney and renamed to pgRouting. After moving to Github
and yearly participation in GSoC the project was steadily growing its
community and user base.
12. Does the project support open standards? Which ones and to what
extent? (OGC, w3c, ect.) Has the software been certified to any standard
(CITE for example)? If not, is it the intention of the project owners to
seek certification at some point?
No. OGC currently has drafts for the route core:
https://docs.ogc.org/DRAFTS/21-000.html and the route exchange model
https://docs.ogc.org/DRAFTS/21-001.html but those are geometry based and
pgRouting algorithms do not use geometries. pgRouting has utility
functions that allow geometries to be adjusted to the graph topology
needed by pgRouting functions.
13. Is the code free of patents, trademarks, and do you control the
copyright?
Yes it is free of patents, trademarks, and the copyright is controlled.
14. How many people actively contribute (code, documentation, other?) to
the project at this time?
The complete list of contributors can be found:
* pgRouting: https://github.com/pgRouting/pgrouting/graphs/contributors
Additionally for pgRouting support:
* osm2pgRouting:
https://github.com/pgRouting/osm2pgrouting/graphs/contributors
* pgRoutingLayer:
https://github.com/pgRouting/pgRoutingLayer/graphs/contributors
* workshop: https://github.com/pgRouting/workshop/graphs/contributors
* vrpRouting: https://github.com/pgRouting/vrprouting/graphs/contributors
15. How many people have commit access to the source code respository?
pgRouting has 9 teams, depending on the team the commit access is to one
or more repositories. For the pgRouting repository there are 24 team
members: https://github.com/pgRouting/pgrouting/people
16. Approximately how many users are currently using this project?
The numbers we can find to give an idea are
* 341 forks https://github.com/pgRouting/pgrouting/network/members
* 69 people are watching the project
* 916 people have starred the project
* 301 subscribers on the user’s mailing list
* 148 subscribers on the developers mailing list
* Its been (that we know of) packaged for:
* [https://packages.debian.org/search?keywords=pgrouting debian]
* [https://apt.postgresql.org PostgreSQL PGDG distribution for debian
and Ubuntu]
* [https://yum.postgresql.org PostgreSQL PGDG redhat, centos,
scientificlinux, fedora (basically any yum distribution)]
* [https://www.freshports.org/databases/pgrouting Free BSD]
* [https://formulae.brew.sh/formula/pgrouting macos]
* [https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes
/postgresql-versions.html#postgresql-versions-version143 Amazon AWS
PostgreSQL RDS] and
[https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Extensions.html
Aurora]
* [https://cloud.google.com/sql/docs/postgres/extensions Google SQL for
PostgreSQL include pgRouting 3.3+]
* [https://techcommunity.microsoft.com/t5/azure-database-for-postgresql
/introducing-support-for-pgrouting-and-plv8-extensions-in/ba-p/3552072
Microsoft Azure Flexible Server for PostgreSQL] and
[https://learn.microsoft.com/en-us/azure/postgresql/single-server
/concepts-extensions Microsoft Azure for PostgreSQL]
17. What type of users does your project attract (government, commercial,
hobby, academic research, etc. )?
pgRouting targets developers and database administrators, many of them
being users of PostGIS as well. There is no specific industry target.
pgRouting is used from academia to government, from system integrator to
cloud providers. pgRouting is also inclined towards the idea of “giving it
back” by welcoming and mentoring new developers and contributors to the
project and community in multiple roles and capabilities.
18. If you do not intend to host any portion of this project using the
OSGeo infrastructure, why should you be considered a member project of the
OSGeo Foundation?
About using OSGeo resources, we are using some, like
[http://download.osgeo.org/pgrouting/ download] and the
[https://lists.osgeo.org/mailman/listinfo/pgrouting-users user] and
[https://lists.osgeo.org/mailman/listinfo/pgrouting-dev developers]
mailing lists.
As mentioned before, the code is currently on
[https://github.com/pgRouting/pgrouting github], but there are plans to
create a mirror on OSGeo's gitea.
19. Does the project include an automated build and test?
* https://github.com/pgRouting/pgrouting/actions
Tested for:
* Operative systems:
* windows
* Ubuntu
* macos
* Compilers & dependencies
* clang
* g++
* boost
* Check documentation links: Validity of the documentation links
* update: Update from previous versions within the same mayor
* [https://github.com/pgRouting/pgrouting/actions/runs/2658249812 check
files]
* Signature check: Checks that the signatures of the user-facing
functions remain stable * within the same mayor.
* News check: Chacks that the news are updated accordingly
* License check: checks that the code has the license.
* Shell check & style check: Verify that the code follows a basic coding
standard.
20. What language(s) are used in this project? (C/Java/perl/etc)
* Main: C, C++, SQL
* For some tasks: python, perl
30. What is the dominant written language (i.e. English, French, Spanish,
German, etc) of the core developers?
Communication takes place in English
31. What is the (estimated) size of a full release of this project?
From [https://packages.debian.org/bullseye/postgresql-13-pgrouting
debian]:
* Architecture amd64
* Package Size 711.3 kB
* Installed Size 2,978.0 kB
32. How many users do you expect to download the project when it is
released?
It's already released, but I would think that with each next release,
the number of users would increase.
--
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2784#comment:3>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
More information about the Sac
mailing list