We use OpenStreetMap - a data commons and open database.
Looking at how we beat marry that with Nostr.
Proof of Place / Attestation will play a role.
nostr:naddr1qq2nya2z2akk6j60w9jz6vpeweg4vn2g8pvrqqgkwaehxw309ash2arg9ehx7um5wgcjucm0d5hsygxy7hn6wk5vud5r655ulurrdppec5572fpudvf9hf583yvcs4k2cupsgqqqw4rsnm4svy
Ok I have a smaller local version of btc map that I'm almost done which basically all I have to do is make it match your submission process/data structure, so if you don't mind directing me to that part of your repo so I can make sure I'm following that and then when I publish I can show you what I'm doing.
That would require API access. Can you share more detail of what your doing?
Oh true, but still would be helpful to point me to the data structure of those requests so I don't have to refactor.
Basically it's a simple form to create a nostr attestation that a business at a certain location accepts bitcoin via on chain or lightning. Then after I publish the event to nostr, make a submission to btc map. The btc map is rendered right below our little list of vendors on the site too.
