Last modified: 2012-08-03 18:19:38 UTC
When clicking on use my current location in a location where there are few or no monuments (for example Sydney) the map is never loaded. This is due to the fix for bug 38741. Essentially what happens is the map continues to zoom out from zoom level 18 until it finds monuments. When it gets to zoom <11 the api fails to respond possibly due to a throttling constraint the server imposes (as the client at this point would have made about 7 requests). Possibly we want to give up looking at zoom level 10 to prevent this but I suspect the server needs to do something more useful such as refuse requests when such throttling occurs. You can demonstrate this by running WLMMobile.app.showMonumentsForPosition(-33.859972, 151.211111) in your console (you will need to expose showMonumentsForPosition in app.js
Querying an arbitrarily large area is not supported. Because the API installation on TS is also used for stuff other than app, search area restriction is not enforced. However, the standalone API will simply return an error for areas larger than 0.2 x 0.2 degrees (discussable) - the app should enforce this restriction internally.
First stab - https://github.com/jdlrobson/WLMMobile/commit/0c2fb4d7fbcec19cb4f7d1754a5da22518f1c007
Merged in https://github.com/wikimedia/WLMMobile/commit/0c2fb4d7fbcec19cb4f7d1754a5da22518f1c007
