[SAC] [OSGeo] #2651: Incubation Application: pygeoapi

#2651: Incubation Application: pygeoapi
-------------------------+-------------------------
Reporter: tomkralidis | Owner: jive
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: Incubator | Keywords: application
-------------------------+-------------------------
Dear Incubation Committee,

Please find below the questionnaire for starting the incubation process
for pygeoapi. In case of clarifications/details needed, please contact me
(tomkralidis gmail com).

Questions

*1. Please provide the name and email address of the principal Project
Owner.*

- Tom Kralidis, tomkralidis gmail com

*2. Please provide the names and emails of co-project owners (if any).*

The Project Steering Committee (PSC) is below

- Tom Kralidis, tomkralidis gmail com
- Francesco Bartoli xbartolone gmail com
- Just van den Broecke justb4 gmail com
- Paul van Genuchten paul vangenuchten net
- Jorge Samuel Mendes de Jesus jorge jesus gmail com
- Angelos Tzotsos tzotsos gmail com

*3. Please provide the names, emails and entity affiliation of all
official committers*

- Tom Kralidis, tomkralidis gmail com OSGeo
- Francesco Bartoli xbartolone gmail com GeoBeyond
- Just van den Broecke justb4 gmail com Just Objects
- Paul van Genuchten paul vangenuchten net ISRIC
- Jorge Samuel Mendes de Jesus jorge jesus gmail com ISRIC
- Angelos Tzotsos tzotsos gmail com GeoComvos
- Richard Law New Zealand Landcare Research
- Gregory Petrochenkov USGS
- Sander Schaminee !GeoCat

*4. Please describe your Project.*

pygeoapi is a Python server implementation of the OGC API suite of
standards. The project emerged as part of the next generation OGC API
efforts in 2018 and provides the capability for organizations to deploy a
RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is
open source and released under an MIT license.

*5. Why is hosting at OSGeo good for your project?*

It will improve visibility, usage and provide better integration within
open geospatial community and tools.

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

standalone server and embeddable library

*7. Please describe any relationships to other open source projects.*

pygeoapi leverages numerous open source projects:

upstream
- OWSLib (https://geopython.github.com/OWSLib)
- pyproj (https://pyproj4.github.io/pyproj/stable)
- Shapely (https://shapely.readthedocs.io)
- SQLAlchemy (https://sqlalchemy.org)
- GDAL (https://gdal.org)
- Rasterio (https://rasterio.readthedocs.io)
- Fiona (https://fiona.readthedocs.io)
- pygeometa (https://geopython.github.io/pygeometa)
- netCDF4 (https://github.com/Unidata/netcdf4-python)
- pandas (https://pandas.pydata.org)
- xarray (https://xarray.pydata.org)
- zarr (https://zarr.readthedocs.io)

downstream
- msc-pygeoapi (https://github.com/ECCC-MSC/msc-pygeoapi

*8. Please describe any relationships with commercial companies or
products.*

The following companies provide support for the project:

- !GeoCat
- Geobeyond
- Just Objects
- !GeoComvos

*9. Which open source license(s) will the source code be released under?*

MIT (see https://github.com/geopython/pygeoapi/blob/master/LICENSE.md)

*10. Is there already a beta or official release?*

Yes, 0.10.1 is the latest stable version (https://pygeoapi.io/download)

*11. What is the origin of your project (commercial, experimental, thesis
or other higher education, government, or some other source)?*

Experimental / proof of concept, and initial implementation as part of the
OGC API efforts.

*12. Does the project support open standards? Which ones and to what
extent? (OGC, w3c, etc.) 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?*

pygeoapi supports a number of OGC API standards. The current support can
be found at (https://docs.pygeoapi.io/en/stable/introduction.html
#standards-support), as well as core encoding standards (GeoJSON, HTML) as
well as protocols (HTTP, HTTPS, etc.)

pygeoapi is Compliant to OGC API - Features as well as an official OGC
Reference Implementation.

*13. Is the code free of patents, trademarks, and do you control the
copyright?

Yes, and the code committers have copyright. See
https://github.com/geopython/pygeoapi/blob/master/LICENSE.md

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

5, plus !GitHub contributions/pull requests

*15. How many people have commit access to the source code repository?*

9

*16. Approximately how many users are currently using this project?*

pygeoapi on the Python Package Index (PyPI) shows a current average of
almost 400 downloads per month. More information can be found at
https://pypistats.org/packages/pygeoapi

*17. What type of users does your project attract (government, commercial,
hobby, academic research, etc. )?*

All

*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?*

pygeoapi leverages the OSGeo infrastructure with the following components:

     Mailing List: https://lists.osgeo.org/mailman/listinfo/pygeoapi

Website, demo, VCS, wiki and issue tracker are powered by Git/!GitHub (see
https://github.com/geopython/pygeoapi)

*19. Does the project include an automated build and test?*

Packaging, Automatic Builds:

- PyPI: https://pypi.org/project/pygeoapi
- Docker: https://hub.docker.com/r/geopython/pygeoapi
- Conda: https://anaconda.org/conda-forge/pygeoapi
- UbuntuGIS: (stable)
https://launchpad.net/~ubuntugis/+archive/ubuntu/ppa/+sourcepub/10758317
/+listing-archive-extra (unstable)
https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-
unstable/+sourcepub/10933910/+listing-archive-extra
- FreeBSD: https://www.freshports.org/graphics/py-pygeoapi

pygeoapi is also part of OSGeo-Live
(https://live.osgeo.org/en/quickstart/pygeoapi_quickstart.html)

Tests, which are invoked on every !GitHub commit using !GitHub Actions
(see https://github.com/geopython/pygeoapi/actions)

*20. What language(s) are used in this project? (C/Java/perl/etc)*

Python

*21. What is the dominant written language (i.e. English, French, Spanish,
German, etc) of the core developers?*

English

*22. What is the (estimated) size of a full release of this project? How
many users do you expect to download the project when it is released?*

A library source release is 110 kB (see
https://pypi.org/project/pygeoapi/#files). A Python wheel is 176 kB (see
https://pypi.org/project/pygeoapi/#files for more information).

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2651&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2651: Incubation Application: pygeoapi
-------------------------+------------------------
Reporter: tomkralidis | Owner: jive
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: Incubator | Resolution:
Keywords: application |
-------------------------+------------------------

Comment (by jive):

Thanks for the application pygeoapi team!

Did you have any contacts in the osgeo community who would be in position
to mentor the project?

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2651#comment:1&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2651: Incubation Application: pygeoapi
-------------------------+------------------------
Reporter: tomkralidis | Owner: jive
     Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: Incubator | Resolution:
Keywords: application |
-------------------------+------------------------
Changes (by tomkralidis):

* cc: msmitherdc (added)

Comment:

@msmitherdc has graciously offered to mentor the project -- thank you
Mike!

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2651#comment:2&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.