are you using NIP66 for this? it has geo tags.. you can find them on monitorlizard.nostr1.com and relaypag.es
anyone can publish these, with a monitoring tool like https://github.com/relaytools/monitorlizard
migrating to georelays on bitchat. find the closest relays for any one geohash and use them instead of the big default ones.
https://github.com/permissionlesstech/bitchat/tree/feat/georelay
hopefully this will inspire more relay ops to accept kind 20000 and better distribute relays globally (we need more smaller ones).
Discussion
to clarify my question a bit. I see you have a .csv file of relays and lat/long and im wondering how you generate it.
off topic https://csv-importer.coracle.social/
nostr:nprofile1qqsw8lr88lzln8x92ng073m4v72kglf9edhxvk8eztg3ftny98f46dgpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsk9y93w can chime in
For now, we just ping ipinfo. But the goal is to use an opensource DB of IP range -> location like this one https://github.com/sapics/ip-location-db
does it check that the relay is wide open for kind20000? i am realizing now this will only work on free and open relays. which there are probably very few of these days.. (for spam reasons).
I was thinking about this exactly, nip 66 sounds like the best solution
I dont think nostr:nprofile1qqsgydql3q4ka27d9wnlrmus4tvkrnc8ftc4h8h5fgyln54gl0a7dgsppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytc79p4zh can hear me, something about primal doesn't like my npub.
we're compiling our own list thanks for nostr:nprofile1qqsw8lr88lzln8x92ng073m4v72kglf9edhxvk8eztg3ftny98f46dgpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsk9y93w's work. eventually we want to crawl these from nostr relays directly so nip66 will be useful (and also relay lists, forgot the kind)