Hello people,
while i was debugging an application i'm working on, i found a bug (i guess so...)in the distance info in a route segment; you can test it at http://local.live.com/ (using shortest time and miles options). The bug is in the 9th segment between Washington [Washington, D.C.], District of Columbia, United States and Miami, Florida, United States. The total distance of the route is 1062.9mi, but the distance in the previous segment is 794mi!! However, if you query the route between that segment and the next one, the distance is correct...
I hope it helps to correct it.
greetings
Dario Aznar - Argentina
Bug in a Route.Itinerary.Segment.Distance
John Papa
Hi John,
someone out of this forum explained it to me that i was missunderstanding the route info: that not every single point along the route has an indication of distance (they are just milestones). In this example case, the route info indicates that you have to take I-95 for 794 miles (and that points 10 through 16 are just milestones -with a null distance- ). And reading the info like that makes sense in this situation.
Anyway, i think that the sdk info is counfusing , because it states that the Distance property of the VERouteSegment class indicates the distance of a segment of the route; but it isn't true in this kind of cases, (when the endpoint of the segment is a milestone). Maybe i'm still wrong about it. I guess it would be very helpful if Caleb could explain it to us, taking in mind that he worked in the sdk.
Greetings
Dario
gidyeo
Yep i get it now. section 9 is that big. Really need to distingish between route segment and milestones hey
John.
SnakeSV
Yeah that is very wrong hey should be only a few miles.
My understanding is under the covers this is all generated by the map point routing system. It would be interesting to confirm if this same error occurs in mappoint. I would suspect so. Maybe worth sending an email to the map point team asking about this case as i'm sure its not isolated.
John.