Post

please this. any community-driven application like this is a good candidate for cutting out the monthly subscription middle man holding the data hostage. open map data in general is needed. I've trying to replace google/apple maps with open alts.

openstreetmap's hiking trail coverage is pretty decent, strava has been backing their updates into it for years because they use mapbox so that's where their map data comes from.

oh, and to deliver that data aesthetically and cheaply, protomaps has basically solved that problem, anyone can get great looking maps for very little $ protomaps.com

this is awesome, thanks for sharing! this stuff has come such a long way, it's a viable alternative now

also ATGeo project atprotocol.dev/location-dat...

oh this is sweet, do you know if there's been any news since last march? i've been looking for a geocoding solution to rebuild my trip planning app

you know I was briefly looking into that after I posted and the project sort of seems dead or went incognito :/ Maybe @bmann.ca or @knowtheory.net could provide some additional context?

ah wonderful to hear, it definitely deserves more visibility! I assumed that it died from some quick searching that had a bunch of dead links (e.g. working group repo, open collective) and no recent updates

We iterated on a bunch of stuff for convening. I think we need to recommit to community forum (this is happening), atmosphereconf community site, and just have clear pointers to help community form new groups and collab together.

I've also been thinking about some kind of lexicon similar to standard.site, but for atmosphere/ecosystem announcements. It would help so much with curating the weekly weather reports and archival searching like this!

I was looking at this the other day - is there a the standard way to reference atgeo collection items so they can be indexed across apps? I was considering using a uri field with “https://places.atgeo.org/org.atgeo.places.{collection}/{id}” so backlinks can be queried via constellation

You use the shared lexicon. They are de-normalized to be stored in user PDS across apps and can be re-aggregated. eg every community event uses atgeo, @beaconbits.app uses it for venues / beacons, etc We could run a community aggregator AppView.

Is the reason for de-normalization is for resiliency / isolation from needing a second data source? It does have some nice properties from that perspective. Yeah, an aggregator appview would be nice - I was trying to re-use constellation for that.

I'm a big fan of AT Proto and genuinely interested here, but I'm a little bit confused here. What is the goal for an "AT Proto native geo lexicon" when the data comes from third parties and the website explicitly says don't store this data? Maybe better to ask, what use cases would one use this for?

what i'm trying to build is a trip planner where you plot a bunch of places you want to visit a map. you could imagine this tying into the broader atmosphere, like maybe someone else builds a mobile app that shows a "day view" of your plan and lets you check into each place

or (just spitballing here) an app that lets people create mini guides for cities — one week in new york, two days in lima, four days in singapore, that sort of thing. you could look at all those guides and create a heat map of the most popular neighborhoods in each city.