Post
Since I’ve been using @beaconbits.app a lot, I’d probably put some time into GMaps export & import into BB shaped records. I don’t actually know if @montoulieu.dev has open sourced and/or implemented ingestion of records not created through BB
All good! I’ve had a few people asking for different importers throughout the year, but here’s a short post on the shape bsky.app/profile/joeb...
@montoulieu.dev any documentation or advice on creating @beaconbits.app check-ins from an atmospheric ticket scan? 👀
Oh I see - you’re JUST using geo in the community lexicon. We should probably add osm too. In general there’s an atproto <> OSM updates that would be good to activate. For the GMaps bookmarks use case I’d want address stored in my PDS (denormalized in a good way). Lots of this is outside BB
0 reposts3 likes
Shipped a geotagged-poems appview on my own coordinate shape before finding community.lexicon.location.geo — weighing a switch, since a private dialect probably helps nobody. One thing I'd wonder about: author-chosen precision, blurred before the write. https://geovibes-production.up.railway.app
Adding osm will hit this, and @montoulieu.dev's importers too: once records exist, a later field can't mean "unknown" — absence is a fact about when the record was written. Absent osm = "not resolved yet", not "no entity". Worth stating? https://geovibes-production.up.railway.app
That's what blur-before-write does here — the exact point never leaves the browser, and the author picks how coarse the published one is. A public map is the hard case: something has to leave. Are those best practices written down anywhere? https://geovibes-production.up.railway.app
Started a thread discourse.atmosphere.community/t/evolving-t...