Hi Marcus
Hello Juan,
a)
I'm not sure what the purpose of this plugin is.
Could you elaborate some more on it's use-case?
As JOSM holds everything in memory and gets
terribly slow in painting when really large areas
are loaded (iterating over all the is loading as
there is no 2D-index).
I guess it could be useful for checking the
behvior of restrictions while mapping an area.
I have used it to check the behavior of routing while mapping an area,
it can detect problems when someone doesn't connect properly ways
(crossing ways, potlach editing, etc.). Sure that many problems can be
detected using the validator, but some others cannot, i.e., paths inside
a park not being connected with the rest of the network.
Restrictions aren't currently processed by the plugin, which is at an
early development stage. That would be of course valuable, as other
algorithms we are considering to introduce, i.e. traveling salesman or
chinese postman, which could be useful to plan each individual path in a
mapping party to traverse all ways of a certain area.
b)
Perhaps it would be better to name your "route nodes"
as "destinations". That could be more intuitive.
That sounds reasonable, we are Spaniards so please consider correcting
any strange words that you may find :-) .
c)
http://svn.openstreetmap.org/applications/editors/josm/plugins/routing/src/com/innovant/josm/jrt/core/RoutingGraph.java
I see that you guild a complete second graph for routing.
As the OSM-data already occupies much memory, what was
the largest map you have been routing on and what was
the refresh-rate while driving?
The largest one was a complete city -Valencia- of around 8-10 km
diameter. You aren't expected to use it while driving, it's purpose is
not navigating, so it doesn't refresh automatically with GPS position.
The route gets refreshed when you add, remove or move destinations, and
the process is quite fast if you don't change routing criteria
(shortest, fastest, ignore oneways). When changing criteria the whole
graph is regenerated. We're planning to fix this problem.
PS:
You can go the other way and click "edit in JOSM"
in Traveling Salesman to export the currently visible area
(a size JOSM could handle) and re-import it once
JOSM is finished. That would be the inverse use-case.
Not testing routing while mapping but correcting the map
after finding a bug while routing.
Great, even though I haven't been able to use Traveling Salesman on it's
latest releases, I always get a lot of exceptions (both in Windows and
Linux) :-( .
Marcus
_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/routing
