Closed (fixed)
Project:
Mapping kit
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
16 Aug 2008 at 11:31 UTC
Updated:
22 Sep 2008 at 15:43 UTC
GPS track is generated from a gpx file sitting on the server.
"google" is selected in "baselayers" via "map context->extension" with only "maximum extent" defined.
Problem:
GPS track is only shown on the map when unticking-ticking the option on the map's menu, but not by default
---------------------------------------------
Cheers for your useful module!
Comments
Comment #1
jpulles commentedAt http://parusnik.co.uk/?q=node/26 it shows that the gpx track is not shown at first, but I could not reproduce this outside your page. Other things I noticed: 1) when moving the map, the track is drawn at a different location (only in FF2, not in IE7), and 2) the rendering of your page shows strange +/- buttons in IE6 and a wide box (in FF2) at the right of an opened layer switcher; not yet sure if (either of) these have to do with your problem.
Regards,
John
Comment #2
provod commentedthanks for your reply, John.
strange, as I didn't change any default settings otherwise.
Also, GPS track shows correctly on the "demis.nl" map baselayer specified via the "layers" field.
Comment #3
provod commentedstrange +- box was due to the theme I was using and changing to a more conservative theme seems to have cured that issue. GPS track on the google baselayer is still problematic - doesn't show by default only when unticking-ticking. Also I noticed that the gpx layer option box can only be enabled on certain zoom, otherwise it's greyed out.
Comment #4
jpulles commentedWill be fixed in next release.
Comment #5
dismalhiker commentedJust confirming the above issue... when I set a gpx file as layer "a", the initial display is without the GPX plot.
Then, when I unclick and reclick layer "a", the GPX plot shows up just fine.
Great module!
Comment #6
jpulles commentedIt should work now. Problem was that when overlaying tracks over a google map that map should use spherical mercator (EPSG:900913) instead of lat/lon (EPSG:4326). The latter one is now used as the so-called displayprojection (see coordinates in statusbar) while the internalprojection is spherical.
Note that in case you use a context to define your map, you can still use EPSG:4326 and define your extent in lat/lon coordinates.
Comment #7
provod commentedyes, works as expected now. Thanks again!
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.