Messages

@tapio
1) Folder required - Good finding! I was expecting that user firstly syncs folders from his device. I will improve this and at least add some info text.
2) Locked Chrome - This should not happen. At least within company no one reported this behavior, yet. In order to investigate I would need steps how to reproduce it.
3) Smartphone usage - Web planner is mainly dedicated for usage on big screens (desktop). We try to make web planner usable also on mobile phone but to be honest it is not the top priority for us right now. You will always have better experience using dedicated LocusMap app for planning on mobile phone (Android).
4) Properties in URL - This is high priority for us, too. You can expect this soon in V1/V2. For now you can use "Share" button to generate planner input URL for you.

@jajaballard
1) Elevation chart - High priority, comming soon
2) Additional maps - AFAIK currently not on our roadmap for V2 (we need to check licensing terms)

@freischneider
1) Drag&drop segment editing - Yes, this is
2) Additional maps - see few lines above (@jajaballard)

@Andrew
1) SSO - Please, could you send me exact version of your browser so I can try reproduce it? Btw is this happening also in private mode (I can think of some plugin doing this)?
2) Default geo location - Actually web planner should ask you for the permission to use geolocation service. If you grant it then web planner should automatically change map to you coordinates.

Thanks everyone for your time to give us valuable feedback. Most of your points are already on our roadmap. Currently, our priority is to release V1, fix/improve most critical findings and then summarize and prioritize our list for V2 (marking as v2 but we will deploy features continuously as they are tested and ready to use).

@WujTom
1) Additional types of map are planned but we have no ETA right now
2) Stat stone - this is a good idea. Not planned in the nearest future but we would like to cover this topic more generally and also introduce this not only to web but also into the app.
3) Related to previous point
4) Route points - V2
5) Elevation chart - V1(depending on time)/V2, in V2 other types of charts
6) I can not answer this - @menion?

@Andrew
1) Popup login - I am not sure if I understand correctly. SSO login screen and login dialog should automatically close after succesfull login. Is this working differently or you would prefer some "Logged in succesfully" message displayd?
2) Restoring last location - we have discussed this internally and we have mostly agreed that almost each time we plan route in different location thus remembering last location is not really a benefit. If there is enough votes we can add this as optional settings.
3) Reverse lookup - we know, this is not the best behavior and should be improved in V2
4) Search - again, we are not 100% happy with current behavior but we use external service and do not have much control here. I hope we can also improve this by deploying our own service (hopefully V2)
5) Shaping point - this is technical debt which should be improved as first things within V2
6) Changing profile - you can combine multiple routing profiles within one route, thus no automatic recalculation should happen on profile change. What is missing right now is possibility to change profile of already routed segment (start of V2)

@didado
Thanks for reporting! I will try to fix this ASAP but we have limited possibility of testing on iOS so for some time you will probably need to use Chrome :-/

@lor74cas
1) Point deleting - should be implemented most probably as context action on right click
2) Nogo circle - not planned right now and we will need to discuss this internally (V2/V3)
3) Planner stats - we will definitely improve here in V2
4) Modifying track on web - this is definitely on of the first tasks for V2 ;-)

@michaelbechtold, thanks a lot for your idea regarding generating UUID based on the object hash. This won't work in all cases (e.g. object modified on one device) but should be good enough solution for most cases . We will definitely discuss it with @Menion during this week.

I can not tell you details about complexity on the client because I am implementing only server side. Keeping older versions in the cloud was my initial idea. I wanted to have periodical job cleaning old object versions but I was convinced by team not to do it. Several reasons (I probably do not remember all of them):

• Main concern -  we could accidentally mess up versions and expose something obsolete
• Additional complexity - clean up made asynchronously (implement task manager, cleanup logic located away from sync code)
• Increased storage requirements that you need to handle history
• We agreed that we don't want to offer versioning functionality to user thus keeping history would be more or less for support and emergency situations (something would go terribly wrong).

.

If you have some thoughts why we should reconsider current logic (not keeping history), please, share it with us. I am sure we will have some time to open this discussion within the team once more .

Hi michaelbechtold,
thanks for your time, testing sync and giving us feedback.I would like to reveal a little bit of technical side of sync algorithm and explain why sync is not working as you would expect.

Each object in device database (point, track) has to be uniquely identified. We use unique numeric ID for this purpose. If you have multiple devices (e.g. D1, D2) there is absolutely no guarantee that point[#1] (point with id=1) in D1 is the same as point[#1] in D2. This is true in the case when you transfer DB from D1 to D2 but in general we can not assume this.

Possibly, we could try to match objects by all properties but it is not correct, in my opinion, too. Let's imagine, that we have exactly the same point[#1] on D1 and D2. When you make minor modification to point[#1] on D1 then point[#1] on D2, which was previously the same, is now different one.

In order to match objects server side we added another ID to client DB -  UUID (example: 162d3708-b2d1-458d-8054-d8e866fb9b10) which is used as unique identification of object across all your devices (as explained, simple numeric ID can not be used for this).

After rolling out new Locus version including synchronization (UUIDs will be automatically generated) then you should be able copy and paste objects between devices and sync should have no issue with it (objects will be correctly paired using UUID) and synced correctly - no duplicates should occur.

Unfortunately, in your case, each device will generate different UUIDs on every device thus you will need to sync these changes manually, once. I will discuss this scenario with @Menion. Hopefully, we will by able to come up with some idea to make this merge easier .

I hope that my explanation is good enough for you and understandable. If not, do not hesitate to ask me .

Hi lega4,
first of all, thanks. Implementation took some time but our resources are limited and we want to deliver quality over quantity . But hopefully we are finally having right direction to do public release!

Cloud sync is exactly what you expect but we implement it in steps thus not everything is implemented - ready for public testing. I will try to briefly summarize our cloud roadmap:

• Implement synchronization solution - sync cloud and multiple devices
• Web planner - something similar to http://www.brouter.de/brouter-web integrating user content synced t cloud (tracks, points)
   
  
   
  • View cloud content on the map + stats
  • Plan track - save to cloud (new item synced to your devices) or export
  • Share track with your friends (only when item marked public, sharing via dedicated url)
• Social network - this is not yet decided if we will do it. First of all cloud sync and web planner have to be finished.

When cloud sync and web planner is finished I believe that your trip planning workflow should be fully supported . I am already looking forward for it!

Hi Andrew,
thanks for sharing your experience. Regarding the offline state, this is really good finding! I guess that it would make sense to disable "Sync button" + show some warning that you need connection for this operation. But let's wait for @menion, maybe this is already on the TODO list

Another benefit of sync (other than backup) is actually possibility to keep multiple devices in sync. You just need to sign in with the same user on a different device (e.g. tablet or even emulator). All changes on both devices should be synced. If you modify same item in parallel then newest change wins. You can definitely test this scenario.

Be aware that right now, you have to pull new changes to your device manually ("Cloud sync" screen > "Quick sync"). We plan to add instant notifications about changes in cloud, soon. This notification should then automatically start sync which should keep your device fully synced with cloud without any extra effort.

Sharing data with other people using cloud is on our roadmap but not implemented right now. We need to finish web planner first which should be used to visualize your shared track (using dedicated url).

[@tapio]

@tapio

Thx for explaining. Don't get me wrong, I trust you, my basic concern usually is, services get exploited and at some point we may find big data dumps available publicly - it always happens here and there... Well it's all about risk management

You are absolutely right. It is up to you if you decide to sync your data into cloud or not (do data backup on your own). Sync is and always will be opt-in service. When using synchronization you will benefit from integration with our web planner (work in progress).

Thanks for your time and checking/testing synchronization and your feedback . We have already found some bugs that somehow passed during our internal testing round.

And let me add: congrats for going public after probably a lot of hard work.

Yes, we have spent a lot of time researching and designing this solution. Thanks a lot . Hopefully no serious issue will be discovered  and we will go public soon and offer this great service to Locus community.

Hi there,
I am main developer of the backend part of synchronization solution. First of all, I would like to thank everyone for participating in the first public test and his/her feedback (positive makes us happy, negative will be pushing us to improve as much as we can ).

@tapio I fully understand your concern. All data are encrypted when transferred between client and server (https, REST API). We use Google Cloud Platform for all our services that are powering synchronization solution (storage encrypted internally by Google). We believe that security provided by Google is good enough. Additionally we try to do our best to have our code as much secure as possible (code review process, up to date libraries, vulnerability scans, ..). Still, no one can guarantee 100% security. Once you upload something to the internet it can be possibly hacked and exposed to third parties ... But again, our biggest concern is keeping your data safe - we are not selling it or sharing with third parties!

Client side encryption/decryption is not possible because we need to have access to it (e.g. web planner - access to your library from web browser, ability to plan track and sync to device, ..).

As already mentioned by Menion, selecting specific folders for sync is not possible (sync all or nothing). If you would like to participate in testing you could

• Make backup, remove sensitive data and try sync, restore backup
• Use Android emulator or another device with different DB. E.g. import points/tracks from public available GPX