[pygeoapi] Support for CRS - via OGC OAFeat Part 2

[Francesco Bartoli]

Hi Just,

This would be a great addition indeed. Answers in order

• I’m not aware of other activities like this
• I don’t have a clear idea atm of the effort even limited to the only OGR provider
• I plan to start again to contribute more during 2022 but not so extensively to the CRS support
• I can see if some of our clients might be interested to support custom CRSs


Best,
Francesco
Il 17 gen 2022, 18:39 +0100, Just van den Broecke <justb4 at gmail.com>, ha scritto:
> Hi Folks,
>
> This is about Part 2 of OGC API Features [1] implementation in pygeoapi.
> In summary, Part 2 is about:
>
> * How, for each offered feature collection, a server advertises the list
> of supported CRS identifiers;
>
> * How the coordinates of geometry valued feature properties can be
> accessed in one of the supported CRSs;
>
> * How features can be accessed from the server using a bounding box
> specified in one of the supported CRSs; and
>
> * How a server can declare the coordinate reference system used to
> present feature resources.
>
> AFAICS there is no activity yet in pygeoapi. There is interest from a
> Dutch government organization for the EU INSPIRE case to at least serve
> Features in different CRSs as specified in requests. There may be some
> budget for implementation.
> This is a preliminary poll for, especially for PSC:
>
> * is there any planned (CRS-) activity you know of?
> * estimate for a minimal implementation, for example to support only OGR
> provider?
> * who would be interested to perform this (paid) development?
> * other parties who may join funding?
>
> [1] http://docs.opengeospatial.org/is/18-058/18-058.html
>
> Thanks for any insights. Best,
>
> Just van den Broecke
> _______________________________________________
> pygeoapi mailing list
> pygeoapi at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pygeoapi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pygeoapi/attachments/20220117/aa46b94d/attachment.html>