What is everybody going to be working on?

[ghobona]

Post a comment letting us know what you are going to be working on.

[chris-little]

I am keen that EDR API SWG members get involved. I will ask at the SWG meeting on Thursday 28 Jan 2021.
Probably:

1. Metadata responses, along with API-Records;
2. Experimenting with EDR API and mainstream geospatial software.

[tomkralidis]

From the geopython stack, I will be working on updating pygeoapi and OWSLib to the latest OGC API - Records draft, as well as starting to plan the same in pycsw.

[ShaneMill1]

From the geopython stack, I will be working on updating pygeoapi and OWSLib to the latest OGC API - Records draft, as well as starting to plan the same in pycsw.

I am interested in looking into OWSLib with regards to incorporating the latest OGC API - EDR. I have not worked with OWSLib so I will need to get acquainted with this software and then tag up with @tomkralidis for some direction.

[desruisseaux]

If there is volunteers whiling to help with the following tasks, they are things I would like to see done:

• Submit PROJ-JNI as an OSGeo project. This is a wrapper making the PROJ library accessible as an OGC GeoAPI 3.0.1 implementation. This task is discussed at Submit as an OSGeo project? OSGeo/PROJ-JNI#33.
• Get peoples from the Python community (@tomkralidis ?) review the GeoAPI Python abstract classes for metadata and referencing by coordinates. Those abstract classes have never been formally released by OGC yet, so they are pretty much open for changes based on Python experts feedback. In particular, how to represent features is an open question.
• Continue the writing of GeoAPI 3.1 / 4.0 specification. This would require feedback from Java and Python users.
• (Possible, may depends on IOGP acceptance) continue the development of GIGS tests.

The above are related to OGC GeoAPI project. They benefit indirectly to Apache Spatial Information System (SIS) since Apache SIS depends on GeoAPI. Some possible tasks more specific to Apache SIS could be:

• Help migrating the web site to a new (to be determined) Content Management System and take this opportunity for making it better.
• Starts implementing a prototype of OGC Gridded Geodetic data eXchange Format (GGXF) - will depend on the advancement of that working group.

[aaime]

Add an implementation of OGC API - Maps to GeoServer. Also code clean ups, and increase test coverage.

[cportele]

Not sure how much time I will have during the three days, but the goal would be to add support for OGC API Records in ldproxy.

[justb4]

Will work on stuff in the GeoPython stack: https://geopython.github.io/ no specific plan yet.

[cehbrecht]

I'm interested in improving OWSLib:

• improving test-suite
• using notebooks for documentation?
• maybe start with the rest-api for WPS

I'm in contact with @tomkralidis.

[pvgenuchten]

At GeoNetwork we're going to impove the ogc-api-records implementation, a sprint planning page has been prepared at https://github.com/geonetwork/core-geonetwork/wiki/GeoNetwork-OGC-API-Records-codesprint-February-2021

[ShaneMill1]

Just a quick update on what I will be working on. After coordination with the OGC MetOcean DWG, I along with other colleagues from the US National Weather Service will be working on the following:

• Using a template @tomkralidis provided, create additional examples using OGC API - Records Core likely referencing BUFR Table A for model data and aviation usecases.
• Synergy between OGC API - EDR and other OGC API's. A starting point would be interacting OGC API - Processes with the OGC API - EDR likely using pygeoapi as a framework.
• Additional discrete sampling geometry for NWS EDR-API implementation (trajectory or corridor)

If time permits, I may start to modify the US NWS EDR-API's collection based search engine to use OGC API - Records rather than CSW records.

Also, if time permits, I may work on what was stated in my original message:

I am interested in looking into OWSLib with regards to incorporating the latest OGC API - EDR. I have not worked with OWSLib so I will need to get acquainted with this software and then tag up with @tomkralidis for some direction.

[fmigneault]

I'm interested to participate in WPS-REST (OGC API - Processes) integration and testing within OWSLib and pywps. I can synchronize with @cehbrecht

[epifanio]

Hi, I will try to work on pycsw - I will focus on customization of the pycsw queriable model, add new profiles and/or modify existing ones.

[gannebamm]

I will take a look at GeoNodes current CSW implementation.

[francbartoli]

I'm going to work with the GeoPython stack, specifically pygeoapi and GeoNode which are related at some point.
On pygeoapi side, I'll work on geopython/pygeoapi#586 while on GeoNode I'll try to start the previous integration, following GeoNode/geonode#6706.

Any help is welcome!

[jodygarnett]

Add an implementation of OGC API - Maps to GeoServer. Also code clean ups, and increase test coverage.

I will be working on GeoServer also

[cvvergara]

Will be working on OSGeoLive and on pgRouting

[prushforth]

I will work on the GeoServer MapML Community Module, adding tests and hopefully also adding bit of functionality, while learning more about the GeoServer API in the process. @ahmadayubi will be working on upgrading the version of the mapml-viewer (Web-Map-Custom-Element is the repo name), which is built into the MapML Community module, and which allows layer previews similar in function to the OpenLayers / KML preview function.

The overall goal of our project is to specify, design and implement an extended subset of HTML that enables browsers to natively 'understand' maps and location. The name of the specification is "Map Markup Language" (MapML), and it has been built into server side components such as GeoServer, MapServer and GDAL. It is not really trying to do anything different from what is already capably done by JavaScript and the many server side projects and geospatial formats, but we are trying to distill the "minimum viable product" of Web maps into an accessibility-centric form suitable for native browser implementation. We believe that will give us a solid foundation on top of which the community can define advanced (yet standard!) client side APIs. We also hope to be able to apply CSS directly to features in the browser, potentially pushing the CSS envelope and map rendering performance at the same time.

Really looking forward to learning a bit from the pros. See you next week!

[allixender]

I'd be keen to do something with pygeoapi or QGIS for/with the OGC DGGS SWG. Alternatively, I'd be happy to help out in owslib, pywps, pygeoapi or QGIS. Would I look for open issues/low hanging fruits :-) ?

Update: I am in touch with DGGS SWG and we will discuss achievable items.
Todo: Read the ER 😄 http://docs.opengeospatial.org/per/20-039r2.html

[kinow]

Will try to join the sprint and help Apache Sis with its new site/CMS, and see what other projects need help, or have something interesting I can help with (and learn!).

[MichelGabriel]

Add an implementation of OGC API - Maps to GeoServer. Also code clean ups, and increase test coverage.

I will be working on the styling of the OGC API for GeoServer

[skyNacho]

I do not have a specific goal for this sprint and I am open and available to help if someone needs a hand from a Python developer. Both pygeoapi and OWSLib are of interest for me. I would also be interested in collaborating with pgRouting.

[pvgenuchten]

Hi @skyNacho, welcome. Check https://gitter.im/geopython/pygeoapi or https://gitter.im/geopython/owslib. I also added a list of tasks to get inspired about the type of things to pick up (alternative is to check the relevant issue trackers)

[cvvergara]

Hi @skyNacho
We need to review this PR it is in python,
Now you have a couple of options :-)
you decide

[skyNacho]

Thanks a lot! I joined the conversation in Gitter and also had a look at the pgRouting PR. We can discuss during the sprint which tasks to prioritize. And in any case I can continue contributing after the sprint :-)

[chris-little]

Refining what I might do, besides capture use cases, document issues, advertise the EDR API, and editorial fixes, I would like to gather feedback on how easy the EDR API is perceived to be among mainstream open source geospatial developers. (I am not mainstream geospatial in any sense!)

[gardengeek99]

I plan on attempting to get an OGC API - Processes server implementation (JAVA based) stood up for eventual use within the Hexagon Geospatial product line.

[KoalaGeo]

With the web site migration @desruisseaux what where the group thinking? Something like https://www.docsy.dev/ which could be hosted via GitHub Pages....?

[desruisseaux]

Hello @KoalaGeo . The web site of Apache projects are hosted on Apache server, so in my understanding GitHub pages are not yet supported. However the ASF let each project choose the tools they want as long as the result is static pages hosted on ASF servers. We can talk more about that in the SIS channel later today.

[wenzeslaus]

Hi, I'm working on OSGeo GRASS GIS, specifically applying more coding standards and their checks to make contributing more streamlined (e.g., Black formatting for Python code).

[lucadelu]

Hi, I'm going to work into a set of modules for GRASS GIS to import OGC API Features, Coverages and Records using owslib

[kinow]

Hello @KoalaGeo . The web site of Apache projects are hosted on Apache server, so in my understanding GitHub pages are not yet supported. However the ASF let each project choose the tools they want as long as the result is static pages hosted on ASF servers. We can talk more about that in the SIS channel later today.

@KoalaGeo I'm keen to help with this task too. In case you have Slack, I believe this link will take you to the SIS channel: https://the-asf.slack.com/archives/C0186JS78SK 👋

[KoalaGeo]

Hello @KoalaGeo . The web site of Apache projects are hosted on Apache server, so in my understanding GitHub pages are not yet supported. However the ASF let each project choose the tools they want as long as the result is static pages hosted on ASF servers. We can talk more about that in the SIS channel later today.

@KoalaGeo I'm keen to help with this task too. In case you have Slack, I believe this link will take you to the SIS channel: https://the-asf.slack.com/archives/C0186JS78SK 👋

I don't seem to be able to get into that slack workspace, but I'm a bit tight for time for the next few weeks with day job deadlines.