Tracks : automatic export directory linked to tracks categories - Same for waypoints
Gathering feedback
Hellooo !
Actually, in Locus general settings, we can define an automatic export to a preset directory for tracks.
Ideas :
1. having this preset directory linked to tracks categories instead of general setting
2. have the same capabilities for waypoints
Results :
If we assign a directory or a sub-directory located in the /Locus/Mapitems for the automatic export, and if this directory or sub-directory is linked with a sync app like Dropbox, Foldersync ... etc, then someone else with another device with Locus (or even a computer) also equiped with sync can have the datas created with Locus "in live", display them and use them ! Yoouhooouu !
Possible ? Not possible ? Good idea ? Bad idea ?
Fifi
I'm usually not the one to give -1 for an idea, but I'm already working with exports and FolderSyncs, and it's all a hassle, and another sidetracking feature that keeps Menion from finally implementing http://help.locusmap.eu/topic/cloud_map_and_data_storage_sync is not what I'm looking for.
In principal, I wouldn't mind it - but again, it's only one way (export, no automativ import), which doesn't really make things so much easier (you'd still have to actively import stuff).
I'm usually not the one to give -1 for an idea, but I'm already working with exports and FolderSyncs, and it's all a hassle, and another sidetracking feature that keeps Menion from finally implementing http://help.locusmap.eu/topic/cloud_map_and_data_storage_sync is not what I'm looking for.
In principal, I wouldn't mind it - but again, it's only one way (export, no automativ import), which doesn't really make things so much easier (you'd still have to actively import stuff).
So simple, so powerful, so unlikely :-)
So simple, so powerful, so unlikely :-)
Obviously file sync sucks in case of databases.
But looking at what database sync in Locus context and Joeloc really means, is: sharing transactions. And those can be represented by files, and such need to be synched by some tools from earlier discussion (this networking stuff cannot be Locus job, to be fair).
It requires exporting to a file, which exists for recorded tracks, but it does not for POIs, nor for New Route&Measure. It would be easy for Menion to include (i.e. inherit) the export mechanics for those kind if things.
And what is also missing is the ListenToSynch mode inside Locus, or at least a button to eat all the new transactions from this synch Android folder.
So far my 2c.
Obviously file sync sucks in case of databases.
But looking at what database sync in Locus context and Joeloc really means, is: sharing transactions. And those can be represented by files, and such need to be synched by some tools from earlier discussion (this networking stuff cannot be Locus job, to be fair).
It requires exporting to a file, which exists for recorded tracks, but it does not for POIs, nor for New Route&Measure. It would be easy for Menion to include (i.e. inherit) the export mechanics for those kind if things.
And what is also missing is the ListenToSynch mode inside Locus, or at least a button to eat all the new transactions from this synch Android folder.
So far my 2c.
Lugging around an additional access point and keeping it charged... no way in hell that is a "tool"... I'd call it a major nuisance. Especially since we have all these nifty things like Bluetooth, nfc and WiFi direct. Its only a matter of proper software... which doesnt exist yet, apparently. Neither on Locus side, nor on file sync side.
Lugging around an additional access point and keeping it charged... no way in hell that is a "tool"... I'd call it a major nuisance. Especially since we have all these nifty things like Bluetooth, nfc and WiFi direct. Its only a matter of proper software... which doesnt exist yet, apparently. Neither on Locus side, nor on file sync side.
I agree with the second part.
But as you have to bring so many ducks into a row, which may take ages, you have a choice: either have and do nothing, or start with some compromise. While hammering on the parties to move into the row for a proper solution.
I agree with the second part.
But as you have to bring so many ducks into a row, which may take ages, you have a choice: either have and do nothing, or start with some compromise. While hammering on the parties to move into the row for a proper solution.
Speaking of "transactions" and since the file based ideas suffer from bad sync tools: Locus already communicates with a wide range of bluetooth devices anyway. Based on this, maybe speaking directly with another Locus would be a rather simple thing to implement. Keeping waypoint folders in sync doesn't exactly sound like rocket science.
Speaking of "transactions" and since the file based ideas suffer from bad sync tools: Locus already communicates with a wide range of bluetooth devices anyway. Based on this, maybe speaking directly with another Locus would be a rather simple thing to implement. Keeping waypoint folders in sync doesn't exactly sound like rocket science.
Agree - this would shortcut all other dependencies. Except the MAJOR one :-)
Agree - this would shortcut all other dependencies. Except the MAJOR one :-)
The MAJOR DEPENDENCY needs a holiday... with buddies... with campfires... without pre-planning every step... and without LTE. Then he might fall in love with bluetooth sync himself :-).
The MAJOR DEPENDENCY needs a holiday... with buddies... with campfires... without pre-planning every step... and without LTE. Then he might fall in love with bluetooth sync himself :-).
Sharing over BT works quite fine for me, thanks for asking. Simply "export data" as usually with checked "Share data" checkbox. Then pick a SuperBeam app to share data, scan QR code on second device and import result. Easy, fast, no problem. Tested many times ... and believe me, even without internet connection. Just a small temporary tip for now ....
Sharing over BT works quite fine for me, thanks for asking. Simply "export data" as usually with checked "Share data" checkbox. Then pick a SuperBeam app to share data, scan QR code on second device and import result. Easy, fast, no problem. Tested many times ... and believe me, even without internet connection. Just a small temporary tip for now ....
Hi every bodies,
In fact, i realize, there's two different ideas / wishes :
1. Synchronize several devices that are close (campfire case)
2. Synchronize several devices that can be long range distant (two peoples that are far away from each others for example in my case)
Then :
1. Campfire case :
We can distinguish two sub-categories :
1.a. Users doesn't have any access to a data network (2G - 3G - 4G) : it could be very cool to find a solution for directly sync datas between the devices seated around the campfire. Resilio app seems to be an answer.
1.b. Users have the access to a data network (2G - 3G - 4G) or a Wifi network : sync through an existing external sync app could be actually possible
2. Long range distant case :
Users must have the access to a data network (2G - 3G - 4G) or a Wifi network : sync through an existing external sync app could be actually possible
That being said, what about the original question ?
1. having the preset directory linked to tracks categories instead of general setting
2. have the same capabilities for waypoints
Menion ? :)
Hi every bodies,
In fact, i realize, there's two different ideas / wishes :
1. Synchronize several devices that are close (campfire case)
2. Synchronize several devices that can be long range distant (two peoples that are far away from each others for example in my case)
Then :
1. Campfire case :
We can distinguish two sub-categories :
1.a. Users doesn't have any access to a data network (2G - 3G - 4G) : it could be very cool to find a solution for directly sync datas between the devices seated around the campfire. Resilio app seems to be an answer.
1.b. Users have the access to a data network (2G - 3G - 4G) or a Wifi network : sync through an existing external sync app could be actually possible
2. Long range distant case :
Users must have the access to a data network (2G - 3G - 4G) or a Wifi network : sync through an existing external sync app could be actually possible
That being said, what about the original question ?
1. having the preset directory linked to tracks categories instead of general setting
2. have the same capabilities for waypoints
Menion ? :)
NFC & WiFi direct might be a little overkill for campfire sync. The amount of data is usually quite minimalistic... one new point... a drawn track... really not much. Bluetooth file transfer is fast enough for that I think... even 1MB go through in a few seconds if necessary... but usually it will only be a tiny packet with maybe 1kb.
Bluetooth also connects quicker and with less troubles, might have an easier API, doesn't interfere with data connections and firewalls, uses less battery.
Bluetooth simply sounds like less trouble. I could always send files to another Android via bluetooth, no problems whatsoever. NFC and Wifi direct were more of a gamble.
NFC & WiFi direct might be a little overkill for campfire sync. The amount of data is usually quite minimalistic... one new point... a drawn track... really not much. Bluetooth file transfer is fast enough for that I think... even 1MB go through in a few seconds if necessary... but usually it will only be a tiny packet with maybe 1kb.
Bluetooth also connects quicker and with less troubles, might have an easier API, doesn't interfere with data connections and firewalls, uses less battery.
Bluetooth simply sounds like less trouble. I could always send files to another Android via bluetooth, no problems whatsoever. NFC and Wifi direct were more of a gamble.
Replies have been locked on this page!