Author: smsm1
[Added to the original trac issue at 1.41pm, Saturday, 25th April 2009]

Oh, and I get error messages saying that the server couldn't allocate memory, and to e-mail Richard.

Author: Richard
[Added to the original trac issue at 9.18pm, Saturday, 25th April 2009]

It starts at the level that you were viewing the map at - minimum 13 IIRC. I'm working on making Potlatch's display faster when there's lots of data - have done a lot of work on the relations code but there's a bit still to do, and it doesn't help that Osmosis won't work on this machine (Java 1.5) so there's no easy way of loading a big dataset into it for testing. But may I respectfully suggest that the best way to speed up the download of lots of data is to set POTLATCH_USE_SQL to true? :D

The "server can't allocate memory" thing is interesting. Never had it before today but I've just had three or four people e-mail me with similar reports. It may chime with the random 500s reported on talk@. Evidently it's not an SWF thing, it's an error being reported by Rails - you probably know better than me what might be causing it!

Author: Richard
[Added to the original trac issue at 5.55pm, Tuesday, 4th August 2009]

It starts at z17 for GPXs these days. Being clever and zooming in when the Edit tab is clicked will require someone to write some code for estimating the amount of data in an area.