it would be cool if the location feature would be enhanced by
i am writing a map application and this is how it would look like:

From Conversations point of view, this feature requires:
I've seen some discussions on this topic recently, so explore existing issues.
Also consider if your use-case could not be handled using Osmand or some small extension for it.
no, all this is not required. the current design is to have a plugin. my app already implements the API for this plugin but the intent does neither contain the jid nor the real name. the "movement" of the position is a bit more complicated but also achievable. you just see the "share location" as a "start sharing" and add a "stop sharing location". either conversations polls the location from the plugin or the plugin sends the location continusly.
osmand has no de-centralized communication with my friends, how would that fit?
my idea is even to have chatroom where you have all participant on a map, maybe even with their avatar moving around accordingly...
Ah, it looks like that the plugin is already implemented... didn't notice that :)
osmand has no de-centralized communication with my friends, how would that fit?
Osmand as a map app, not for communication. Osmand is advanced, fully featured map & navigation open-source app. It is worth a look.
my idea is even to have chatroom where you have all participant on a map, maybe even with their avatar moving around accordingly...
Yes, that matches my expectation.
yes, there is even an official conversation plugin which shows the location via google api. my app is just starting to implement it and there may be more.
so why look at osmand if the same problem persists: the communication? i know osmand and use it alot but it's a different thing: it's a navigation app, not something where you want to watch tracks, pois and persons moving around you. it may be a candidate if you want to navigate to a persion known in conversations but that is not my usecase. it must be implemented in osmand and the necesary part in conversations for that usecase is already there.
my intention is more outdoor sports where you need to know where people are around you when in the wilderness where navigation won't work anyway.
Osmand is not navigation only - the navigation is just one feature of many. Actually, there is similar plugin to what you are doing, but it uses proprietary service - Osmo plugin. It would be nice to have fully open-source alternative to that. I see an opportunity in combining Osmand's Osmo plugin with Conversation's ShareLocation plugin.
osmo is why i said "de-centralized" in the beginning. that's why i don't use this feature. track support in osmand is poor as well in my opinion. there may be many features in osmand which are near to unusable so for me it boils down to navigation.
(btw: the last update looks increadible good and i have to check about the features again)
Yes, Osmo plugin's communication part is ugly, but that is the part you want to replace with Conversation's ShareLocation plugin. Everything else should be fine (or at least good enough for a start; I haven't seen its code tho).
no, i do not want to replace anything in osmand, i develop a different map app. ;) i ask for improvement of conversations to allow better usecases.
I'm talking about forking and reusing relevant part of Osmand's Osmo plugin, and connecting it to Conversations (instead to proprietary service), so you don't have to write entire map app. But if you want to write it... ok :)
as i said: i already have. it's a fork of RMaps which seemed to be abandoned. you can see the screenshot... so forking osmand isn't my business but feel free...
I similar mature service is
I refer to this category as Social GPS (as GNSS is not a term many would use. Both GPS and GLONASS are GNS Systems)
Glympse does not require the receiving party to have an app (or plugin)
@emdete
Is the location available from PEP to contacts in my roster?
Also please employ the
Open Source Location API
https://github.com/microg/android_packages_apps_UnifiedNlp/issues/36#issuecomment-86744484
and not the proprietary Play Services Location API.
@TameOfGroans : i do not understand both of your points.
the roaster is not part of the idea, and the XEP about the location is a nightmare (it doesn not allow encryption). i like Conversations aproach better here. the enhancement just asks for steady updates of my location to a friend i am chatting with.
which geo location provider is used in android is not the decision of an app but of the one installing (or deinstalling) apps on his device (and yes, i do NOT use any gapps on my phone and it works fine so far).
@Emdete are you sure there is no way the pep messages can be encrypted?
@emdete @miighty Are not PEP entries stanzas? Does not OTR/OMEMO encrypt stanzas?
What is the status related to https://bitbucket.org/SamWhited/opensharelocationplugin/src ?
What is the status related to https://bitbucket.org/SamWhited/opensharelocationplugin/src ?
This is just a fun little thing I built; feel free to use it (or not); it still has only the data Conversations sends to it, so it's not likely to get either of the requested features soon.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
@emdete
Is the location available from PEP to contacts in my roster?
Also please employ the
Open Source Location API
https://github.com/microg/android_packages_apps_UnifiedNlp/issues/36#issuecomment-86744484
and not the proprietary Play Services Location API.