{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifanp7v4hwzrrvhv5vtufeigimr4jkukmonclu62gf5b5hukurgrq",
    "uri": "at://did:plc:4tuge3k3comfj4nfvqnwkemn/app.bsky.feed.post/3mghsifhql3w2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreic32gsl7sbgus3l2bmsobh6o745xdy43n6j52w5poqgnwnq6xeee4"
    },
    "mimeType": "image/png",
    "size": 2880988
  },
  "path": "/user/mikelmaron/diary/408323",
  "publishedAt": "2026-03-06T20:06:20.000Z",
  "site": "https://www.openstreetmap.org",
  "tags": [
    "Here’s the chat"
  ],
  "textContent": "From the Build Plan developed with Claude\n\n> Project Purpose A web application enabling mappers and data quality analysts to select a geographic area, fetch Overture Maps POI data and OpenStreetMap data in parallel, algorithmically compare them, and produce two outputs: a reviewed, selective upload to OSM via OAuth2, and an annotated GeoJSON export classifying each Overture POI by assessment category.\n\nNo edits to OSM happen without manual review. Overture is more of an attention guide (at least that’s my hypothesis)\n\nHere’s the chat\n\nLots of UX fine tuning to come. Quick observations:\n\n  * Overture is very noisy, lots that is irrelevant (business mailing addresses in personal houses, mislocated POIs, closed places, duplications with differences across Meta/Microsoft/4SQ sources)\n  * Matching is hard but can be improved\n  * There is useful signal in Overture, places that need addition to OSM in new developments, but you have to have means to easily sort through and keep a record.\n\n\n\nI’m going to work on refining the workflow, add means to link features across Overture, ability to not just add but adjust OSM features, audit trail so it’s possible to share reviews and apply reviews against new releases….",
  "title": "Vibe coding an OSM / Overture conflation tool."
}