Difference between revisions of "Known Issues"
From Geohashing
imported>Zigdon (Removed old resolved clicking-adds-0s issue) |
|||
Line 8: | Line 8: | ||
* When using firefox w/ firebug there an error shows up when clicking on a marker on the map. It seems the handler is trying to read a property called 'latlng' which isnt defined when clicking on a marker. Line 81 on xkcd.js. Maybe if latlng == undefined, then either exit ( if nothings supposed to happen ) or use the getLatLng() function on the passed object. | * When using firefox w/ firebug there an error shows up when clicking on a marker on the map. It seems the handler is trying to read a property called 'latlng' which isnt defined when clicking on a marker. Line 81 on xkcd.js. Maybe if latlng == undefined, then either exit ( if nothings supposed to happen ) or use the getLatLng() function on the passed object. | ||
+ | |||
+ | * The algorithm tends to produce points clustered near the graticule origin, though not on it. For a more random result, try ignoring the first digit after converting to decimal (try plotting the points from a whole year's worth of data to see this) |
Revision as of 05:45, 8 July 2008
Please direct all discussion on these issues to Talk:Main Page.
- Due to the relative start locations used, if you happen to live close to a coastal region you may require a boat in order to successfully reach the calculated coordinates.
- In addition, due to the relative start locations used, you may require a passport to successfully reach the calculated coordinates.
- Some of the mapping URLs don't cope with -0 as entry, making this grid (eg London West) difficult to map. See -0 Issue.
- When using firefox w/ firebug there an error shows up when clicking on a marker on the map. It seems the handler is trying to read a property called 'latlng' which isnt defined when clicking on a marker. Line 81 on xkcd.js. Maybe if latlng == undefined, then either exit ( if nothings supposed to happen ) or use the getLatLng() function on the passed object.
- The algorithm tends to produce points clustered near the graticule origin, though not on it. For a more random result, try ignoring the first digit after converting to decimal (try plotting the points from a whole year's worth of data to see this)