Note: this event immediately follows the 2024 Joint OGC – OSGeo – ASF Code Sprint.

TerraOps - Innovations

Organizations are invited to sponsor the Code Sprint. Please contact the event contacts for more information about sponsorship.

• Tom Kralidis
• Ricardo Garcia Silva
• Joana Simoes ✉️

• Start: Thursday 29 February 2024 9h UTC
• End: Friday 01 March 2024 17h UTC

• Casa Cordovil - Universidade de Évora (Évora, Portugal)
  • Casa Cordovil: R. Dom Augusto Eduardo Nunes 7, 7000-784 Évora
• pygeoapi Jitsi channel
• pygeoapi Gitter/Matrix

Évora is a UNESCO World Heritage Site and was chosen to be European Capital of Culture in 2027.

When arriving in Portugal via airplane to Lisbon, you can reach Évora by public transport, using either train or express bus. In both cases you need to start by coming from the airport to the "Gare do Oriente" transportation hub. Either take a metro from Lisbon airport to the "Oriente" station (three stops from the airport) or take a taxi/uber/bolt (should be about 10 min.) and then either:

• Board the "Intercidades(IC)" train bound for "Évora". The Journey from "Lisboa - Oriente" to "Évora" station is only about 1,5 hours, but we recommend you to check the train times in advance, as there are only a few trains per day - price is around 15 €.

• Take an express bus to "Évora". Journey time is also around 1,5 hours and prices in the 5 - 10 € range. Some reliable operators:

  • Rede expressos
  • Alsa
  • flixbus

If you prefer to drive, Évora is under 1,5 hours from Lisbon on the motorway.

Évora is also reachable from the Faro airport, in the south of Portugal, albeit a bit further, with journey times of about 3,5 hours by either train or bus.

Here is a list of recommended hotels:

• The Noble House: https://thenoblehouse.pt/en/home
• ADC - Albergaria do Calvário - Boutique Hotel: https://adcevora.com/en/home
• Évora Hotel: https://www.evorahotel.pt/en/
• Vila Galé Évora: https://www.vilagale.com/en/hotels/alentejo/vila-gale-evora

Participants should plan for the following costs:

• travel to Évora
• accommodation for 2-3 nights

• bring your own laptop
• bring a power connector adapter as needed. Also see https://www.power-plugs-sockets.com
• come with a working development environment (Git, Docker, Python, editor, etc.)

📣 Note: in-person participation MUST be confirmed below before 10 February 2024, in order to plan for catering 📣

• pygeoapi overview, update and status (@tomkralidis) presentation

  • architecture
  • standards support
  • roadmap
  • summary of issues/PRs
  • API refactor (@tomkralidis/@totycro)

• pygeoapi refactor (@francbartoli/@ricardogsilva)

  • PoC to move pydantic as a data validation plugin
  • use of composition over inheritance
  • dependency injection pattern

• Issue / PR sweep

• Issue / PR sweep

Day 1:

address issues/PRs
- 10 business days (assuming Monday - Friday)

- PR template
 - suggest to open issue
- stale-bot on PRs and issues
 - 90 days autoclose + msg
 - exempt specific labels (blocker)
- monthly open meetings

- CITE GitHub Actions
 - against available ETSs

- api.py refactor
  - agree to implement (Tom/Bernhard)
  - comms: freeze PR merge only on things touching api.py things

- Protocol / duck typing
  - introduce after api.py refactor in core to allows extensibility
  - do not touch plugins atm
- pydantic
  - master is broke because of versionitis
  - p1 PR to downgrade pydantic 2 --> 1
  - release thereafter
  - should NOT affect rebasing during api refactor

- pygeoapi processes and auth

Day 2:

Francesco M - Processing

1. external? context
2. multiple outputs
3. processing / process manager
 - mimetype / outputs


- OAProc CITE P1
 - Ricardo S: give Tom a week, follow up

- plugin discovery?
  - community plugin repository

  - we have https://docs.pygeoapi.io/en/latest/plugins.html
   - problems
   - legal implications
   - docs are versioned; could be risky
  - proposal 
   - move to wiki page

  - outreach and communication (Krishna)
   - videos
    - target is 01 July 2024

  - /collections/
  - remove type column from HTML
  - group "records" collections after "data" collections