I wonder if #PlusCodes could viably be used as hashtags to generate some sort of geographically #local feed.
The first six characters of a plus code denote an area of roughly 5x5 km², so if I take a full plus code like "9F4MG98H+G3", and then create a hashtag using the first six characters, like #9F4MG9, adding that hashtags to posts would allow others to find activity in a certain region.
Have a look at my use of #geocoding hashtags:
→ https://mastodon.social/@jpreisendoerfer/109727868336726649
I think it'd be better to prefix the respective #geocode with an abbreviation indicating its type.
#HamRadio people will often want to use #Maidenhead (#QTH) locators rather than #OpenLocationCode (#PlusCode).
Plus char can be dropped from OLC, because ›OLC‹ indicates #PlusCode.
For reduced precision, drop trailing OLC letters.
🌺
It also sprang to my mind this second. :))
I removed the middot which I used for better #readability. It's hard to enter on a smartphone, too.
Now I dropped middot as well as underscore, because that saves at least one character in toots with #geocode. :)
A #geocoding #hashtag will be hard to digest for people using #screenreader|s, though.
🌺
🏷️ #QTHJO62 #OLC9F4M #CitizenBand #CiBi #27Mhz #CQ #AFU #CBFunk
After some testing, it would be worth to consider #geocoding of postings as a #FeatureRequest to #Fediverse developers, preferably not as #hashtag but as a separate property of postings, like #ContentWarning:
CW is implemented using the #abstract property of #ActivityPub.
To create a CW when boosting a #Friendica posting on #Mastodon, the author uses [abstract] markup in the Friendica posting.
Similar may be possible for #geocode|s.
The location property of the #ActivityVocabulary does not only support exact locations but also areas in the sense that it allows for ›logical locations‹.
A logical location could be ›near Berlin«, but also a #geocode with reduced precision.
🌺
🏷️ #OLC #QTH #SemanticFediverse #ActivityPub #Mastodon #Friendica #Pixelfed #Fediverse #Geocoding #Georef #Georeferencing #OpenLocationCode #PlusCode #Maidenhead #HamRadio #AFU #CBFunk #CitizenBand #CiBi
Btw, #normalization of #georeference|s is not trivial, because it requires techniques called #InstanceMatching.
It's an entire field of ongoing research.
A search for one of the #Berlin|s should be able to come up with
🌺
🏷️ #OLC #QTH #SemanticFediverse #ActivityPub #Mastodon #Friendica #Pixelfed #Fediverse #Geocode #Georcoding #Georeferencing #OpenLocationCode #PlusCode #Maidenhead #HamRadio #AFU #CBFunk #CitizenBand #CiBi #ActivityVocabulary
@lapingvino @jpreisendoerfer @factotum
Maybe a bit late to the party.
We are doing @redaktor and an awesome Client around Places and to call Bike Couriers, Rikshas, Cabs and such in Germany.
Mapped an Atlas to ActivityVocabulary for this assignment. It is huge and features a near complete mapping from wikidata to geonames to OSM.
The primary mechanism is to use the `describes` property for topic, we spoke a lot about it in last SocialCG meetings.
The primary identifier might be wikidata giving us all knowledge in multilangue.
But I was unsure about hashtags as well. What is the benfit of OpenLocationCode compared to e.g. http://geohash.org/site/tips.html ?
The numerous geocoding systems vary in #granularity (#precision) achieved with a certain amount of letters, & in their audience or #community.
Above, I gave the example of #Maidenhead Locators (#QTH) commonly used by #HamRadio people.
Different cultures use different #geocode|s for reasons.
AFAIC, it would allianate communities to single out a particular system & mark it as ›general‹ by using a prefix like ›#GEO‹.
Platforms should #welcome & represent a variety of cultures.
🏷️ #OLC
factotum
LaPingvino 🟙 
Jörg Preisendörfer
Helge
Sebastian Lasse