Evolving the location lexicon to add OSM

Lexicon Community ATGeo
1

Had a thread with @montoulieu.dev looking at the shape of Beacon Bits lexicons.

community. Lexicon. Location. Geo is what he uses, plus the OSM URI in order to “group by”

This is the same use case as the Foursquare ID

Should we look at evolving the lexicon to add an OSM field?

@schuyler.info what are you thinking between atgeo namespace and flows vs location in the community lexicon?

4 Likes
2

I’m really interested in adding OSM place ID in the lexicon. I plan to create an app with a custom lexicon that is just like community.lexicon.location, but with OSM. So we could save existing places. It would be great to rely on an open, community-maintained dataset rather than a proprietary one :slight_smile:

1 Like