JupyterGIS sync meeting 2025-06-24

JupyterGIS notes

A weekly gathering of JupyterGIS team to discuss our progress and help each other out. Open to all, but this meeting is short and task-focused, so there will not be time for introductions. Please join a core meeting!

Author

The GeoJupyter community

Published

June 24, 2025

:::info {.callout-info} 🔍 This meeting is short and task-focused. Unfortunately, we won’t have time to introduce every new person to the team. Please attend core community meetings (see GeoJupyter calendar) to meet the team and add your own agenda items, and/or introduce yourself on Zulip! :::

JupyterGIS sync meeting 2025-06-24

Please add new agenda items under the New agenda items heading!

Attendees

Your name / GitHub ID / affiliation

  • Martin Renou / @martinRenou / QuantStack
  • Matt Fisher / @mfisher87 / DSE

Agenda

  • Review our project board
    • What items should be added?
    • Are there stale items that are no longer urgent?
    • Are there things we can change about the project board to make it more useful? Add more information? Remove steps?
  • Please add more items if you have them!

Status reports

  • STAC browser PR
    • The hardcoded API (geodes) is down, should be back in 2 days
    • Greg tested some other STAC endpoints, and some worked, some didn’t
  • Processing toolbox refactor by Guy
    • How to validate the JSON data? Take this on in another PR.
    • Matt to give final review today!
  • Symbology overhaul:
    • No significant progress since last hackathon
    • Going to try to make progress today in preparation for hackathon tomorrow
  • Draw vector features on the map:
    • Matt to review this week!
    • Should we keep this PR open until we can do the vector sub-type development? We don’t want to introduce a new feature and then revoke it. This PR should be easy to rebase if the trunk changes.
  • Should we have a 2nd trunk branch to help use release features more selectively?
    • Increases maintenance burden and contributor complexity
    • We don’t have enough maintainers right now for this
    • We think we will probably reach a point where this is necessary as the project’s scope grows.