Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Bad remaining second data in QUERY_STRING mode #3018

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Closed

Bad remaining second data in QUERY_STRING mode #3018

openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Assignees
@openstreetmap-trac
Labels
Component: gosmore Priority: trivial Resolution: wontfix Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: lubos[at]next176.sk
[Submitted to the original trac issue database at 11.11pm, Friday, 28th May 2010]

Installed plain SVN gosmore, imported slovakia OSM. Gosmore works great but
"Fifth field is the estimated number of seconds remaining"
give bad values.. Distance was about 30km..

First line of output has:
motorcar/fast ~2500 Second (this seems good on selected distance)
motorcar ~1700 second (little bit unreal)
bicycle ~120 second (impossible by bike, car)
foot ~40 second (impossible by foot, car)

One of my example (Slovakia)
From 48.39904 17.35825
To 48.89236 18.03937
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: nroets[at]gmail.com
[Added to the original trac issue at 12.38pm, Monday, 31st May 2010]

Seconds remaining is only intended for fastest route.

After generating a shortest route, you can break the route up into segments and call the routing engine once for each segment and add the totals.

@openstreetmap-trac
Copy link
Author

Author: mmd
[Added to the original trac issue at 6.56pm, Tuesday, 19th May 2020]

Gosmore project is no longer active, closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: gosmore Priority: trivial Resolution: wontfix Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac