Hello
I don't know if this is a bug: when I compose manual a track by pointing on the map (vector, germany) and if I have enabled the "COMPUTE ROUTE" Icon (either with MapQuest or with BRouter) often I get an error:
QuoteSelect at least two objects
and:
QuoteTrack cannot be computed
this error pops up mostly if the next track-point is not very far from the previous.
But it is not only if it is just 10 m beside, also when the points are some streets away it could happen, which is sometimes neccessary to get the exact route I want.
I am on SGS4 (OS 4.4.2 Omega v40) with actual Locus version and BRouter 1.1
Thank's
frank
Quote from: franc on February 10, 2015, 00:09:13
...either with MapQuest or with BRouter...
and Google and GraphHopper.
(http://s4.postimg.org/m22nzvth5/2015_02_10_215333_cr.jpg) (http://postimg.org/image/m22nzvth5/) (http://s4.postimg.org/62k0gbxfd/2015_02_10_215304_cr.jpg) (http://postimg.org/image/62k0gbxfd/)
In addition:
This happens also if you try to join two paths wich have no logical connection.
BRouter doesn't have data for every cm but depending on turns, crossings, etc.only in certain minimum distance. I assume BRouter takes the next point in its database according to the distance to the actual selected point by the user. If the user selects two points they can be projected on the same point in the database -> no calculation possible due to seemingly distance=0m.
In addition it can also happen that for the selected profile (e.g. car!) there is no possible connection between the two points. Assume one point in a street, the other one in a pedestrian area, blocked by a pole, ...
QuoteBRouter
Same message with all other services.
Quotetakes the next point
(screenshot) there is a path from junction to junction.
QuoteIn addition it can also happen that for the selected profile
always with "foot"-profile.
hi, I'll check it more precisely home but this problem only happen when you try to compute really short track right?
Quote from: menion on February 11, 2015, 17:29:32
... this problem only happen when you try to compute really short track right?
No, could be 100 meter or more.
And if once this error came, it likes to show up again and again.
I guess it's a matter of non-exact mapping of cursor to an object on the map.
Quote from: Christian on February 11, 2015, 22:30:13
I guess it's a matter of non-exact mapping of cursor to an object on the map.
I disbelieve this. Then it would be independent of the nearess of the two points.
In fact it happens to me only if the two points are not too far from each other, but this is often neccessary to select the exact route, so that the engine (BRouter, Google or Grasshopser etc.) doesnt route otherwise and to be fast in setting the points.
Any news about this issue?
Is it a Locus bug?
Ah sorry, thanks for reminder.
I'm checking problem and found in code very simple condition ... "if new point is not far then 100 metres from previous, do not add it to compute". That is all.
I've changed it to 10 metres too keep at least a very simply check for double points and changed notification to be more clear ("points are too close").
Quote from: menion on February 20, 2015, 15:55:05
I'm checking problem and found in code very simple condition ... "if new point is not far then 100 metres from previous, do not add it to compute". That is all.
I've changed it to 10 metres too keep at least a very simply check for double points and changed notification to be more clear ("points are too close").
Very good, thank you for this !
Great!
It works with the update of today, it is fixed!
This the little things this app makes so great, apart from all functions :D
Over 10 meter:
(http://tapatalk.imageshack.com/v2/15/03/09/4d4eca260f46040ef94bb533d2ef2444.jpg)
Under 10 meter error with clear message, which is ok:
(http://tapatalk.imageshack.com/v2/15/03/09/9dfa3ec2f7781151b60b6dd8bc2c68ea.jpg)
EDIT: reduced the huge Tapatalk images to 400 px width (IMG width=400)
glad to hear, next trouble solved. Thanks for confirmation.
Confirmed.
Thanx :)