Thanks for finding the source of that. Probably a reasonable concern back in 2012 - maybe less so now. Maybe someone will see this and think it could be updated (or reverted! ;) ). As I said earlier, I'll give it a couple of days, then implement some logic using continue if it looks like it will stay as is.

Thanks for the reply. It does seem consistent, and I noticed that for London too (another big city with 33 articles) there were a few missing too. It's a little unfortunate that it doesn't continue to load the extract for the rest of them, as it is already loading plenty of other useful data for me. But I can only assume that there must be a good reason to stop at 20.

Yeah, so I tested it with New York, where there are ~55 articles nearby. I had ggslimit set to 50 (where it always was, so a few were always not returned) and colimit set to 50, as suggested recently above. I increased ggslimit to 70, but left colimit. 55 articles were loaded, and the last 5 had no coordinates. So I simply increased climit to 70, and all was fine again.

The fix of using colimt=50 does work for me, so happy to use that. I must test it for cases where there might be more than 50 articles within 20km just in case I need to increase that limit (I've no idea if that would solve it, but I can test!).