ID/Community Chats/2026

From OpenStreetMap Wiki
Jump to navigation Jump to search

General

  • Location: BigBlueButton
  • Format for Agenda suggestions: "(AddedByUserName) Title, Link"

Some meeting were listed only in https://osmcal.org/ and were missing from that page.

Community Chat 7th January 16:00 – 17:00 (UTC)

https://osmcal.org/event/4279/

Attendees

  • Martin
  • Gregory
  • Tobias
  • Pierre-Leo

Notes

  • iD's NPM package
    • Who can release? A: @openstreetmap orga -> reach out to owner of the npm/@openstreetmap orga to get Minh also included as a secondary person
  • open PRs from contributors
    • preset shortcuts PR -> how can we collaborate best on that new feature?
    • generally: a step by step roll out approach might make sense: e.g. minimal viable product first, then adapt to more and more features over time
  • education tag (see discussion on community thread)
    • will be fixed in upcoming version of the tagging schema
    • schema could/should separate addTags from suggestTags in future version
  • outline for iD development in the upcoming months
    • short term goals
      • get almost done PRs finished. e.g. lifecycle tagging, preferences synchronization, rectilinear shapes "building" tool
      • preset favourites / "shortcuts" (see above)
    • mid term
      • aerial imagery -> more than one custom layer, integration of openaerialmap (and maybe other STAC or WMS/WMTS based sources)
      • custom styling of OSM data, to make enhancing specific OSM data more easily possible; (similarly: maybe also custom styling of custom data overlays)
      • more settings in general to customize the behaviour and appearance of iD, e.g. custom keyboard shortcuts
      • more powerful Notes integration (e.g. filtering by date and user; search functionality, etc.)
    • longer term
      • make keeping the map up to date easier
      • direct user to user interaction in the editor (e.g. GeoChat, or a way to see nearby mapper's changes "pop up" live)
  • idea: possibility to share settings between editor
    • through standardized entries in the preferences endpoint of the OSM API
    • 255 character limit of preferences API call is a bit limiting