Export of no-go points

Olivier Toulon shared this idea 18 days ago
Declined

Hello.


In the context of disaster relief, I would like to know if it is possible to add an option in the POI groups that will classify the points of this group as an area to avoid.


In case of floods a reconnaissance team will create a group of POIs with the option "to avoid". The other teams would load this group of POIs on their LOCUS applications. Thus to move from one point to another randomly they could build a reliable route, LOCUS will avoid these points automatically by proposing a route. This would save lives and save a lot of time for rescue.


I'm willing to do the beta-test on this option.


Thank you very much

Comments (5)

photo
1

Hello to the community! Today in France we have floods in the neighbouring department. Some roads are flooded. As usual, I go as a backup to do reconnaissance with locus map. He will follow my route and I will make quick POIs with pictures. The "to avoid" option will no longer be missing and this will be the best option for colleagues. GPX file sending by Whatsapp and any reinforcements who are unfamiliar with the area could come and go from one point to another by creating routes in locus without engaging in flooded roads. I can't wait to test it! Would anyone be willing to work on it? Thank you in advance friends!!!!! Friendships from France!


Translated with http://www.DeepL.com/Translator

photo
2

Hi Olivier,

Locus route planner has the option to insert "no-go" points on the map so that the router would bypass such places (see https://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning#define_areas_to_avoid). Unfortunately, sharing such points is not possible.

However, there is a way how to insert a specifically defined no-go points for BRouter. The process is a bit more complicated but maybe it can meet your requirement: https://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning:brouter.

best regards

Michal, Locus team

photo
1

Hello Michel! Thanks for your answer !

I will try the solution "BRouter" but it seems to me compromised in view of the unaccountability of this app on new versions of android ... I will seek to force the install via an old version and follow your tutorial.


However, to stay at the simplest and quickest, I think the solution is in sharing these "no-go" points. Adding a no-go point import / export feature in the trip editor is an option I look forward to. One could consider loading a .gpx file before calculating the route. Is it so difficult in terms of software design?


Thank you

photo
1

Hello. I confirm that I did not manage to use BRouter. The application due to google restrictions can no longer recover LOCUS files as indicated in the tutorial mentioned above.


So, back to square one for me....

photo
2

Hi Olivier,

thank you for the update. I've tested the BRouter method myself (haven't done it for ages) and it doesn't work anymore, you're right. Therefore, I've changed this query to an idea for other users to vote for it. When there is a stronger demand for this option, we'll implement it.

best regards

Michal, Locus team

photo
1

Hello Michal,


Thank you for following up on the subject and re-qualifying it. I hope it will generate interest because for us it would really help us.


How to put the proposal forward for a better readability? A reworking of the text ? Is that clear enough as it is currently worded? A "special rescue" mention to attract firefighters and other services in the process? I imagine that in the context of the huge fires in California this option would be very useful: or and how to avoid the fire?


Thank you for your support. It is rare that a team of developers is so reactive and communicative. Congratulations, I really don't regret the purchase and would continue to make Locus known in France.


Thank you very much.

photo
2

Reading this tread, I remember some +/- similar questions in the help desk.


The available well documented Garmin Gpxx extension probably can be helpfull ?

The gpxx extension already is partly activated in Locus point adress field exchanges


NOT IMPLEMENTED: Waypoint proximity alert, with a settable (circular) area "on map" indication.


Easy gpx waypoint (+ has description field) sharing and import inclusive the most actual updates by changed area info is fast and easy.


(Non local) workers rushing to a rescue can thus either avoid an area or go so the most quickly and efficient way toward affected ones. On the fly decisions (Locus autorerouting to points helps) and simple map reading so avoiding actual danger area's probably are more important than (out of date) planned routing by continuously changing "no go" zones. Adding and removing (timeslot) no go zones is probably a too "sloowish" operation in full action.


* References: How to Add a circular proximity alarm ? NOT implemented !


https://help.locusmap.eu/topic/individual-poi-proximity-alert-distance-tts#comment-53281


https://help.locusmap.eu/topic/add-radius-for-points#comment-60765


https://forum.locusmap.eu/index.php?topic=3777.msg27831#msg27831

photo
1

Hello, 0709,


Thank you for your proposal, but it does not really correspond to the need. In my case, it is not a question of pointing out a danger, but of letting the route editor know that we want to avoid this point. The route must be editable in advance to plan it (mission on the route for example).


My idea is really simple.


During a reconnaissance mission a team creates fast POI points during its patrol everywhere there is a danger or a blockage of the road (tree fall, flood, landslide...) This team at the end of the mission shares by email or other application these points in a file .gpx to other teams.


To move around the affected area, it should then be possible to perform the following manoeuvre without further complication: In the route editing menu, give a starting point and an arrival point, then import a.gpx file considered by LOCUS as points to avoid and finally validate the route calculation. Once calculated, the route should be able to be saved and shared. All the interest is to be able to plan the route in advance!


Technically, in route editing mode, it is already possible to manually create a point to avoid. To the extent that locus keeps in memory these points from one trip to another, in which folder of the application and in which format does it keep them? Wouldn't it be enough to be able to export a.gpx file in this same folder for LOCUS to load it as points to avoid?


Thank you to you!!!!

photo
2

Export of Nogo Points by gpx.

Olivier, understand.

But only 1 + Vote and a lot of development time is not favourable.

So the suggestion should also attract extra general interest. (Sorry I do not need, so no + Vote from me)


Step by step:


1. Short(er) development time by using known gpxx functionality "proximity area". (Proximity area indication could be atractive for other users too)


2. Imported "nogo" gpx wpt points must be recognised for transfer to the Locus nogo list. A marker by <sym>Nogo</sym> ? (Locus only)


3. As I expect frequent updates of the nogo points(list) by fast changing local conditions ..what about liftetime ? Refresh the nogo list after a new import ?


So far my contribution. Anyway succes !

photo
2

Hi Olivier,

from my point of view, your idea is really interesting and seems to be reasonable enough for implementation. Nevertheless, I'm not a developer so I forwarded the idea to the Locus Map creator for evaluation.

best regards

Michal, Locus team

photo
1

HI

Thank you for your feedback and the responsiveness of the community. Thanks Michal for the support of the idea and its transfer to the devellopeurs. To follow then.


Regards,

Theo with my friends from France

photo
1

And the most favourable for a realisation is: An attractive proposal for the developer himself ;-)

By the way.

Locus has a functional poi alert area + (maybe) New, the gpxx proximity alert area ?

Where (when) both area's do touch = generate alert. Attractive ?

photo
1

Hello 0709!


Thank you but an audible warning on a point of interest does not allow the route editor to avoid it. As a result, this option would not allow to edit in advance a safe route, capable of avoiding the time wasted by a U-turn when discovering a blocked road. And when it comes to rescue from a major event, time can be a life.


So this proposal does not meet the demand. However, I like it very much. In post-disaster situations, many road incidents occur and not all of them block roads. In the event of the discovery of a dangerous but not blocking situation (debris on the road, asphalt torn off, light obstacles), a simple audible warning as the point approaches seems to me very relevant and very complementary to my proposal.


Friendships

photo
1

Hi Olivier,

For your idea, an extended Locus poi alert modus as I suggested is not important. (Is just a nice extra)

Important is transfer of the imported gpx (gpxx) area zones to be promoted into the Locus "nogo" system.

No worry Olivier, our developer maybe has even another more optimal idea..so let's be patient.

photo
photo
1

Hello Olivier,

quite a long discussion on this topic. I've talked about this also with Michal and even it does not look, this topic is quite complicated.

There are two main problems. No-go points in Locus Map do not behave like ordinary points and also that GPX does not by default support parameters needed to specify No-go parameters.

Both problems may be solved: No-go points may be converted to basic points (that should solve also another topic here on the help desk) and GPX may be extended. Anyway as 0709 mentioned, it is really really a very time-consuming task we cannot afford now. For me, it also simply looks like a really complicated method of how to share data between users. Unfortunately, I know no better now.

Maybe at least small help. No-go points are stored in Locus/cache/various/nogo_places.lb file. So you may share this file between users (simply copy & paste when the app is closed).

Thanks for understanding,

Menion

photo
1

Hello Mr Menion! :o)


Thank you for the explanation and especially for the nogo file info. Last but not least, is this file openable/editable through an application? In what format are the points written? I tried via a text reader without success. Thank you very much !

photo
1

Hello,

unfortunately this is not possible. No-go points were never planned as editable out of Locus Map so the file is a binary file impossible to edit by any text editor, sorry.

I would really like to help, unfortunately, we are currently in a delay with our long-term plan so it is not an ideal time to do such "minor" tasks.

Menion

photo
1

Okay, I understand! Thanks anyway! Good luck for the rest of the project!

photo