For a -point tracklog, the tileserver approach takes about 140 ms
per tile to render. When it needs to download a tracklog that it's
never seen before, that takes about 800ms. Tiles that don't intersect
with the tracklog bounding box (completely transparent ones) take
3-4ms.
Timings
On Fri, May 23, 2008 00:02, OJ W wrote:
Sorry, example URL should be:
http://dev.openstreetmap.org/~ojw/gpx/?gpx=112168zoom=10lat=52.08314lo
n=-0.71864
Really nice, how about adding a link to that page from the overview of the
trace itself? Maybe next to of (map / edit) a overlaid on map?
Nice indeed, i just wonder if it wouldn't be easier (on the server) to
show it using openlayers - it can handle KMLs, and will handle GPXs in
version 2.7
http://trac.openlayers.org/ticket/1272
and some older support:
http://www.gnunux.info/projets/openlayers-gpx/
Now, a GPX slippy map image layer
As a side-effect of some routing stuff I'm looking at, we have this little tool:
http://dev.openstreetmap.org/~ojw/route/?gpx=112168zoom=10lat=52.08314lon=-0.71864
which should be able to display any public GPX trace (just replace the
gpx= number)
___
4 matches
Mail list logo
