Known Issues

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 is an error that 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) see talk page

• There is a small bias towards the pole side of the graticule. The graticules are 1 degree longitude by 1 degree lattitude, but 1 degree longitude is smaller near the poles than near the equator. Since the algorithm does not use/know this information, a point at the pole side of the graticule has more chance of becoming a geogash location than a point at the equator side. In other words and more general: a square (kilo)meter near the pole has more chance of 'hosting' a geohash location than a square (kilo)meter near the equator.