@Jan Range just mentioned this: https://en.m.wikipedia.org/wiki/Open_Location_Code
There's a "find your code" button at https://maps.google.com/pluscodes/
Would this be a good identifier for each hub? The good thing is that it enforces geo location and could be re-used for maps to display installations.
For each installation?
But what's the advantage over good old lat/long? :thinking:
I was considering using this approach for the DV-Hub ID you mentioned in the Python channel. Since itβs a single string, it could identify the installation, even if the installationβs name changes.
Hmm, will installations ever move, though. Probably not.
A search for "has a university ever moved" yields some results, I'm afraid. :sweat_smile:
Oh okay, I did not expect them to move :-D
They're all in the US :rolling_eyes:
We are a rootless people
How does a university move? :grinning:
with difficulty
and patience, I guess :grinning:
So you like that it's a single string like 9VGP+7J instead of a messy 42.377813,-71.114812 (and who knows how many significant digits to use).
I feel it qualifies more as an ID than concatenating lon/lat. But I have some doubts now as it is only valid under the assumption that installation stay at the same location and there are no two instances at the same location. I am not sure how common these cases are.
DANS has a few installations. Datastations, I think they call them.
Okay, that would break it already. I think good old UUID or integer are the better choices then :grinning:
still, good to know about this Open Location Code thing, though
might come in handy some day
True, at least learnt something new :smile:
Last updated: Nov 01 2025 at 14:11 UTC