JupyterGIS sync meeting - GeoJupyter Team Compass

🙏 Our apologies, there’s no time for introductions!
We’re excited for you to join us, but this meeting is short and task-focused. 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-05-06)¶

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

Attendees¶

Your name / GitHub ID / affiliation

Matt Fisher / @mfisher87 / DSE
Arjun Verma / @arjxn-py / QuantStack
Martin Renou / @martinRenou / QuantStack
Greg Mooney / @gjmooney / QuantStack

Status reports¶

Matt: CNG went well! Prepping for a workshop next week, won’t be doing much dev.
Arjun:
- Settings PR: geojupyter/jupytergis#619
- Schema version PR: geojupyter/jupytergis#590
  - Should the field be under “metadata” or at the root?
  - ipynb has “nbformat” and “nbformat_minor” both at the root.
    - Notebook metadata has information about the kernel, that’s it.
    - Maybe JGIS projects have “author”, “last_edited” as metadata. What else?
    - What about viewport location? Currently in options, which we think makes sense. That’s the project data.
    - Decision: Keep schema_version at the root!
  - What about annotations? Should they be metadata or top-level?
    - Matt/Greg: Gut says top-level, but we can leave as-is for now.
- Annotation UX improvements: geojupyter/jupytergis#650 , geojupyter/jupytergis#640
David:
- TiTiler extension: https://github.com/geojupyter/jupytergis-tiler
  - Serve zarr file examples/xarray.ipynb
  - Does this enable collaboration on a Xarray DataArray?
    - Depends. if the Kernel is shared by everyone, it should work!
    - If JupyterLite, no go.
  - Adds new dependency, makes the doc a bit more complex.
  - Not sure whether this belongs in core yet. David feels strongly not to! Martin feels adding to core could be nice.
  - Serve non-optimized GeoTIFFs from kernel.

Requests for help¶

None today!