GeoJupyter core community meeting 2025-04-08

Meeting notes

A monthly gathering of the GeoJupyter core community. Open to all!

Author

The GeoJupyter community

Published

April 8, 2025

GeoJupyter core community meeting 2025-04-08

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

Attendees

Your name / GitHub ID / affiliation / favorite flavor of ice cream (or other dessert)?

  • Nicolas Brichet / @brichet / QuantStack / ?
  • Fernando / GitHub ID / affiliation / ?
  • Matt Fisher / @mfisher87 / DSE / adzuki bean (red bean)
  • Greg Mooney / @gjmooney / QuantStack / Cookie Dough

Standing items

    • 🎉 What is working well?
      • Virtual hackathons, of course 😉
      • ?
      • ?
    • 💡 Opportunities for improvement?
      • More virtual hackathon timeslots? What timing would enable you to participate in the hackathon?
      • Building more energy in Zulip channel.
      • Building up a larger contributor base.
      • ?
      • ?

Follow-up from previous meeting(s)

New agenda items

    • Planning on a session and a workshop
    • Session: Full day, posters in morning, oral in afternoon.
    • Workshop: 3.5 hours or 7 hours. Not GeoJupyter specific; open source and cloud native tools.
  • EGU in May 2025, anyone in QuantStack going? Ask in Zulip.
    • Super productive!
    • Insights:
      • “No metadata” still very common problem.
        • We can make our interface more usable than QGIS’, take inspiration from epsg.io for example.
      • 😖 Too many data formats!
        • 😭 “I feel despair when opening a NetCDF”
      • 🗨️ “I want my actions in an interface to produce a script to be reproducible.”
      • 🎮 I want to do it multiplayer.
      • “Too much prep work before I can even visualize my input data.”
      • 📈 Lots of R users.
        • :medal: “My favorite tool is R|ggplot|GEE|StoryMaps”
    • ❤️ Awesome work Arjun, Martin, Nicolas!
    • Would love your review on WIP blog post
    • PRs:
      • 🔧 WIP: Add new function geo_debug(my_data) - opens a JGIS panel (new document) to explore my_data (including a basemap).
        • Better name for this function? Proposed:
          • show() - could be confused with other show() functions which open a widget to simply display an object; this function will create a new document and pre-populate it with a layer
          • Nicolas: sandbox() playground()
          • Fernando: geo_explore(), explore()
        • Update path for widget:
          • Filepath passed to model is only informative.
          • sharedModel, not model, is the thing that shares data with the server.
          • No way to update the file target, it’s a read-only property.
          • Better to create a new widget and replace.
          • Nicolas: Maybe we shouldn’t do this; re-running the notebook would replace the widget again
          • Fernando: It’s important that certain patterns of behavior are consistent across Jupyter components. Notebooks are documents, consoles are throwaway environments. Notebooks always live on disk, but if not named have a name slug.
            • Nicolas: What about a file naming convention to indicate that this is a temporary file?
            • Fernando: Untitled1.jGIS!
      • 🔧 WIP: Add “Save as…” to UI
      • ✔️ Add “Save as…” to Python API
      • ✔️ Display toolbar in widget/sidecar views

Pushed to next meeting

  • [ ]