I just gave Gosmore a whirl. Downloaded the latest exceprt of the Netherlands, built gosmore-20080521, rebuilt the pak file and ran a test command:
QUERY_STRING='flat=5.65922&flon=53.04821&tlat=5.66875&tlon=53.02616&fastest=1&v=motorcar' ./gosmore Now Gosmore returns: No segment nearby Content-Type: text/text I don't know exactly what that means but I made sure to use the lat/lon coordinates while hovering the mouse pointer over two streets in the same city on http://tile.openstreetmap.nl Do you have any idea about what might be wrong? Perhaps a difference in projection? I tried some other coordinate combinations as well, with the same results. Also, I wonder about the list of coordinates in you example. Are those coordinates of junctions? How would one use those coordinates to e.g. plot a route on an OpenLayers map? ----- Original Message ----- > gosmore is once again able to rapidly calculate routes between two > points on the map. I added a Common Gateway Interface (CGI) compatible > routing interface : If the QUERY_STRING environment variable is set, > it will not go interactive, but answer the query instead. For example, > executing > > QUERY_STRING='flat=-25.778618&flon=28.290682&tlat=-25.768199&tlon=28.270595&fastest=1&v=motorcar' > ./gosmore > > will yield > > Content-Type: text/text > > -25.778618,28.290682 > -25.778765,28.294502 > -25.779473,28.294473 > -25.779826,28.293441 > ... > > gosmore will work well under normal CGI, because it has a fast start > up time, does not write to files and when one query gets interrupted > by a page fault, Linux may continue another query. > > So if anyone wants to slap a web interface on it (e.g. export to GPX > and / or plot result on slippy map and / or convert to instructions > for humans), please let me know what you need. AFAIK OJW was > interested in such a project last year. > > The current source is at http://www.rational.co.za/gosmore and it is > nearly mature enough for public consumption. A rebuild > of the complete planet currently takes about 3 hours on a dual core 64 > bit machine with 2 GB RAM. (thanks to FR) (No bad considering how long > it took us to import just the TIGER data). The resultant pak file is > too large for the address space of 32 bit machines, but they will > happily run excerpts such as 'germany'. > > It's not designed for routing from New York to LA, but in my > experience you will run into malformed junctions long before you run > out of memory or CPU power. > > There is now also a HEADLESS switch if you only want to rebuild and / > or use the above mentioned CGI. > > The one feature that I still need to implement is low-zoom rendering. > > Regards, > Nic > > _______________________________________________ > Routing mailing list > [email protected] > http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/routing > _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/routing
