Opened 2 years ago

Last modified 2 years ago

#2784 new task

Incubation request: pgRouting

Reported by: cvvergara Owned by: jive
Priority: normal Milestone: Unplanned
Component: Incubator Keywords:
Cc:

Description (last modified by robe)

  1. Please provide the name and email address of the principal Project Owner.
  • name: Celia Virginia Vergara Castillo
  • email: vicky at georepublic.de
  1. Please provide the names and emails of co-project owners (if any).
  • name: Daniel Kastl
  • email: daniel at georepublic.de
  1. 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
  1. Please describe your Project.

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.

  1. 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 ​github, but there are plans to create a mirror on OSGeo's gitea.

  1. Type of application does this project represent(client, server, standalone, library, etc.):

It is a library in form of a postgres extension.

  1. Please describe any relationships to other open source projects.
  1. Please describe any relationships with commercial companies or products.
  1. Which open source license(s) will the source code be released under?
  1. Is there already a beta or official release?

In September 2013 the ​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, ​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 ​RFC2 and all the ​releases can be tracked on the pgRouting Github repository.

  1. 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.

  1. 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.

  1. 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.

  1. How many people actively contribute (code, documentation, other?) to the project at this time?

The complete list of contributors can be found:

Additionally for pgRouting support:

  1. 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

  1. Approximately how many users are currently using this project?

The numbers we can find to give an idea are

  1. 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.

  1. 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 ​download and the ​user and ​developers mailing lists.

As mentioned before, the code is currently on ​github, but there are plans to create a mirror on OSGeo's gitea.

  1. Does the project include an automated build and test?

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
  • ​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.
  1. What language(s) are used in this project? (C/Java/perl/etc)
  • Main: C, C++, SQL
  • For some tasks: python, perl
  1. What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers?

Communication takes place in English

  1. What is the (estimated) size of a full release of this project?

From ​debian:

  • Architecture amd64
  • Package Size 711.3 kB
  • Installed Size 2,978.0 kB
  1. 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.

Change History (3)

comment:1 by robe, 2 years ago

Description: modified (diff)

comment:2 by robe, 2 years ago

Description: modified (diff)

comment:3 by robe, 2 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.