search

OsmSharp / ui

The UI components.
http://osmsharp.com/
GNU General Public License v2.0
138 stars 91 forks source link

Strange pathfinding #208

Closed JoeCooper closed 9 years ago

JoeCooper commented 9 years ago

I'm using the latest from git for both execution and the conversion from xml to the contracted hierarchies routing file. I got something like this:

screen shot 2015-01-21 at 11 15 06 am

The source data (xml) has been used before successfully.

WDYT?

xivk commented 9 years ago

Ok that's not looking very good... I just noticed some test have been failing that checks this stuff.

These are fixed now. Sorry about this, this kind of regression is caught by the unittests, but I overlooked the fact that they failed.

JoeCooper commented 9 years ago

I've pulled the new changes, rebuilt the router file and ran it again (making sure to clean and rebuild everything with newest sources) but it doesn't seem to have solved the problem.

xivk commented 9 years ago

Can you send me a code sample and if possible the area of routing and/or the serialized file?

You can get in touch with me via this form:

http://www.osmsharp.com/contact#overlay-context=contact

I will reply with my private email.

xivk commented 9 years ago

In some cases the shapes of an edge are not copied correctly. Fixed this now... It slipped by the tests because it only occurs in middle to larger networks.

Will close this issue after I have test coverage on the piece of code causing the issue.

I'm updating the odp-tool and things will be back to normal.

JoeCooper commented 9 years ago

In some cases the shapes of an edge are not copied correctly. Fixed this now... It slipped by the tests because it only occurs in middle to larger networks.

Thanks a lot. Will close this issue after I have test coverage on the piece of code causing the issue.

I’ll try it shortly.

– Joe=

xivk commented 9 years ago

One more problem in de odp-tool. Checking now...

xivk commented 9 years ago

I updated everything, tested the entire workflow again. The route you suggested is now calculated correctly:

http://geojson.io/#id=gist:anonymous/2cad6a8e4429816ff7c3&map=14/46.9110/-102.7882

Let me know if you have more problems...

JoeCooper commented 9 years ago

You’re right. It’s working. Thanks a lot.

– Joe

On Jan 26, 2015, at 12:48 PM, Ben Abelshausen notifications@github.com wrote:

I updated everything, tested the entire workflow again. The route you suggested is now calculated correctly:

http://geojson.io/#id=gist:anonymous/2cad6a8e4429816ff7c3&map=14/46.9110/-102.7882 http://geojson.io/#id=gist:anonymous/2cad6a8e4429816ff7c3&map=14/46.9110/-102.7882 Let me know if you have more problems...

— Reply to this email directly or view it on GitHub https://github.com/OsmSharp/OsmSharp/issues/208#issuecomment-71449540.