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. b) Perhaps it would be better to name your "route nodes" as "destinations". That could be more intuitive. 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? 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. Marcus On Tue, 31 Mar 2009 11:40:30 +0200, Juan Guillermo Jordán Aldasoro <[email protected]> wrote: > Hi, a new routing plugin [1] for JOSM has been just released. It can be > used with the last revisions of JOSM. > > Features: > > * Multidestination routing. > * Reverse route. > * Routing criteria > o Shortest > o Fastest > o Ignore oneway (yes/no) > * Setting weights for highway tags > > Cheers > Juangui > > [1] http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Routing > > > _______________________________________________ > Routing mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/routing > _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
