ID/Community Chats/2026

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 4th March 16:00 – 17:00 (UTC)

https://osmcal.org/event/4487/

Attendees

• Martin
• Tobias
• Mateusz
• Tobias Knerr
• fluffycupcakes

Notes

• new iD release out since this week. Martin is working getting regular patch releases out more regularly to get imagery updates out more frequently.
• supports more powerful directional combo field, to support sidewalk field
• idea to enhance the functionality to also do something similar with non-combo fields. directionality would be a new property of the preset fields
• Mateusz has started (paid) working on processing old prs/issues of iD and the tagging schema, first progress was done already
• Tobias Knerr suggested to include osm2world into iD. UI to figure out. Ideally, the library would only be loaded on demand whenever the 3d view is active. Mostly feasible for showing one (or few?) buildings, but not a whole city center, etc.
• How could iD better support copy/pasting of tags of one object to others? -> e.g. hamburger menu at the raw tag editor with options to copy/paste tags
  

Community Chat 4th February 16:00 – 17:00 (UTC)

https://osmcal.org/event/4396/

Attendees

• Martin
• Tobias
• Pierre-Léo
• Mateusz

Notes

• Google Summer of Code ideas welcome
  • opening hours project
  • searchable/interactive presets website
• GSoC students selection:
  • important to look at edits
  • select good PRs for them to do now, e.g. the multiple custom background imagery layers might be a nice feature for a gsoc student
• active PRs:
  • Esri Wayback imagery feature was ported over from Rapid by Tobias, PR is work in progress
  • Presets shortcut: PR work in progress
  • Sidewalk field: PR ready to merge
• Potenial features from rapid to port to iD
  • sidewalk/kerb interaction, see also Kyle's PR
  • sync crossing nodes and crossing ways, but instead of an auto-magic background thing, it should be a validation message instead
  • integration of Maproulette as another QA tool
• Mateusz submitted a proposal to EWG to get some financial support for supporting work in the tagging schema repository
• editor-layer-index could be hosted on npm under the "@openstreetmap" organization namespace
• schema-builder PRs are to be worked

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