Page 1 of 1

Badly joined routes

Posted: Mon Dec 01, 2014 12:34 pm
by KZsolt
Helo guys!

During an xRoute planning I've noticed a "badly" positioned road segment.
If I plan between the mentioned 2 points I receive a wrong distance value and that comes from the fact that the roads on the 2 border sides are not joined together.

StartLocation.Latitude = 54.270711;
StartLocation.Longitude = 25.375725;
EndLocation.Latitude = 54.274811;
EndLocation.Longitude = 25.378034;
teszt.JPG
Currently that problem doesn't affect my work much but I wanted to point you out that problematic part.
Oh and the map data is: EuropePremium_2014_2H.geo

Thanks,
K. Zsolt

Re: Badly joined routes

Posted: Mon Dec 01, 2014 2:38 pm
by KZsolt
Hey!

There is a second example for the same issue:
start: 53.520969498, 23.658575337
end: 53.521946668, 23.66047848
test.JPG
Hope that helps!

Thanks,
Zs.

Re: Badly joined routes

Posted: Mon Dec 01, 2014 2:53 pm
by Bernd Welter
Hello KZsolt,

thanks for the info - I forwarded it to some colleagues of the data department.

Usually such data corrections have to be forwarded to the data providers themselves, so it might take some time to be taken into account.

Regards from Germany,
Bernd

Re: Badly joined routes

Posted: Wed Dec 03, 2014 1:29 pm
by Bernd Welter
Hello KZsolt,

meanwhile I've been in contact with our data experts ad they mentioned that we depend on our providers. Though the map you refer to is not proper we expect this effect to disappear in the upcoming versions. In the meantime the maps image might look suboptimal but the routing itself should work. See attached screenshot...
Malicious provider geometry with teleported street connections at border crossing
Malicious provider geometry with teleported street connections at border crossing
Best regards from Germany,

Bernd

Re: Badly joined routes

Posted: Fri Dec 05, 2014 12:23 pm
by KZsolt
Helo!

Yes that doesn't affect the routing at all, just the calculated distance values. The difference is minimal (couple of hundred meters). Thanks for the reply, I'll check the fix in future versions.

Regards,
Zsolt