Yes, the Gosmore update process failed because of the API upgrade (and planet dumps that got broken because of that). Unfortunately this caused the existing Gosmore database files to be deleted. I’m already trying to build new databases but this will take a few days… Sorry about that.
In the Wiki, you said you’d be supporting route via’s in a couple of weeks. When will this be available ? Since I’m presently just prototyping things, I’d also be glad to help with testing and alpha versions.
I have been working on via’s and directions and a complete website makeover but it all has stalled when the routable Garmin maps service took off and now because I’m in the process of moving to my new house. The code of this new version is a mess and not functional (but you can see where I’m going).
Thanks for reporting this. The echobig thing was hearsay and I just copied it… Anyway, I replaced the whole echobig thing with just ‘echo $kml;’. I also enabled standard gzip compression to the .htaccess file and confirmed that the output is now gzipped when the client requests it.
I always thought that, when you ‘open’ the PHP code with ‘<?php' you'd always have to add the 'close' as well ('?>’). But I searched it up and found this. So, yes, you actually have to omit the closing php tag.
There is a limit of about 1280 usable byte per packet most of the time, however the TCP stack/NIC deals with this just fine all on it’s own you don’t need to do a thing about it.
As the link says, it’s optional if you have a closing tag or not, but they said the same thing I did, you don’t end up with problems of trailing white spaces which can cause issues if you don’t have the closing tag.
I finally fixed the GPX export function so that it uses a HTTP POST query instead of HTTP GET. This makes the export function to work even with long routes.
The Gosmore database update for this week has been reversed because of weird routing results (at least in Europe): Gosmore seemed more interested in very small roads then motorways.
Possibly no database updates in the coming two weeks while trying to sort the problem.
Someone from a server in Denmark was hammering the API for days (or weeks, who knows) with about 20 requests per second on an automated manner. This interfered with normal users requests so I’ve blocked the source IP.