WiGLE.net

In writing a client for wigle, what limits should I impose on a user, when the user is selecting an area for downloading data from wigle. I think I should put some limitations on the area size, as it'd be crazy for everybody to be downloading the entire world all the time, but I'm not familiar with what wigle's got for servers, so I figured I'd ask on what limits to set.

there will always be server-side limits on the dataset, just as a practical matter.
they'll probably be foo where foo is some thousands or tens of thousands depending.

we're looking into a wigle.net api that will make this a bit easier to do (currently targeting java/perl and probably c, any other requests?)

as a general rule of thumb, the current county or metro-area sized queries produce enough points to make managing them in the clients.. interesting.

Also, please cache results so you're not downloading the whole area every time. The JiGLE client requests everything after the largest lastupdt from the last time it cached, and integrates the results using the bssid (MAC) as the primary key, then writes out the results into the new cache file.

Alrighty. Yea, I planned on caching stuff anyway. The biggest way I use this stuff is download it, and use it on the road. As a side note, you guys should have a dev forum. As for porting stuff to different languages. . . I use VB. What kind api rig up are you guys cooking? Frankly, I like the simplicity of a simple get query on a web server to get data. It's awesome.