Hello Josh!
Le 28/06/2021 à 22:18, Joshua Lieberman a écrit :
This is Josh Lieberman, on the staff of the OGC. I’ve been interested
for a while in helping to standardize geospatial data types for
various python packages and other mainstream computing tools. The goal
is to help base these on common, valid geospatial models in order to
make data sharing across tools and platforms more reliable.
I'm very interested in that! Actually OGC GeoAPI [1] is trying to do
exactly that and contains a Python packages [2] in addition of Java [3],
with only metadata and CRS stuff for now. Those Python interfaces have
never been formally released yet, so the floor is open for feedback,
changes, etc.
We did not had a GeoAPI SWG meeting at OGC for a while, in part because
I'm hoping for face-to-face meetings to resume and in part because I
have difficulty to put enough time in it. If someone is interested in
being GeoAPI chair or co-chair, I think it would help a lot.
Outside OGC, the OpenEO effort [4] has a similar goal. In my
understanding of the presentation they did a few years ago, the two
projects differ by their approach. GeoAPI has a more "bottom to top"
approach, trying to secure foundation (CRS, metadata, features, etc.)
before to move to the next level, while OpenEO focuses more directly on
top-level services.
Another goal is to help avoid reinventing wheels. For example, PostGIS
supports EWKT and EWKB which already include SRID’s.
Yes, but I think that those SRID can not really be used outside the
context of the PostGIS database that contains the EWKT or EWKB. It seems
to me (I may be wrong) that they are just integer codes without
authority names. Peoples often assume that they are EPSG codes, but this
is not necessarily the case; we have to check in the "spatial_ref_sys"
table for the actual definition. So if a geometry encoded in EWKB needs
to be used by a process outside the PostGIS database, the SRID may need
to be resolved to a full CRS definition if we want to be unambiguous.
We (OGC) are specifically interested in working with our partners,
such as Apache, to host an “Encoding Summit” at our September or
December Member Meeting. A principle focus will be JSON encodings, but
data type encodings for other environments are also of interest. One
outcome could be an Encodings working group that targets “round trip”
interoperability between various encodings. Another could simply be
joint work items to further these objectives. Let me know if you might
be interested in participating.
I'm interested on the assumption that, in the context of Python or Java,
we interpret "encodings" as "interfaces" with data structures left to
implementers. There is a "round trip" interoperability between Python
and Java in GeoAPI (still in development) that I would like to continue.
Regards,
Martin
[1] http://www.geoapi.org/
[2] http://www.geoapi.org/snapshot/python/index.html
[3] http://www.geoapi.org/3.0/javadoc/index.html
[4] https://github.com/Open-EO
