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/
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:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m can hear me, something about primal doesn't like my npub.
we're compiling our own list thanks for nostr:npub1u07xw079lxwv24xslarh2eu4v37jtjmwvev0jyk3zjhxg2wnt56seyez97's work. eventually we want to crawl these from nostr relays directly so nip66 will be useful (and also relay lists, forgot the kind)