we're actively working on it - give us a few days!

Cheers,

-ark

thanks for your interest!

yeah, we're hearing a lot of requests for sqlite, and it's high on our list!
we're working on this actively, but we're in the middle of re-designing the upload system to handle bluetooth and increased cell data, which is slowing this down.

-ark

you're not doing anything wrong! we're just behind in supporting that format.

There are ways to slice and export the SQLite file in the meantime to upload them as netxml/json/etc.

the counter to the right of BT is your local database - the stacked cylinders are a database symbol.

i'd suggest scaling list size to available memory, but that seems to be the source of a lot of the crashes we get with Google's mapping library, so I'm a little skeptical. The list adapter infra from Android should go a long way toward mitigating that, but a giant hash of objects will get big no mat...

wow, that's bad behavior - sorry. we'll get this sorted out for a fix release.

Good point! Adding to our features list. (and as always, PRs are welcome on github!)

We're building out the server-side functionality as we speak - it's been our policy to front-run web-based publication with data collection for a few months in order to preserve the anonymity of individual discoverers when the data goes live. If you're interesting in using your data, you'll find it ...

there isn't a way right now, but we'll add it to the feature request matrix!
one note: the zoom functionality on your browser should interact safely with this - not a perfect solution, but it might be a practical work-around

oh, awesome note - I think I'd assumed the problem was in show-current only. I'll keep digging (I rarely use show-all because it gets long quickly).
2.38 is fully released now, with the major fixes in. We'll keep digging.

sorry, is this on the webmaps or in the android client?

let us know how it goes - always happy to help!

-ark

Not sure what you're asking, but you can contact us at WiGLE-admin[at]wigle.net over email and we can work to help you.

-ark

It depends on what dimensions you're interested in accuracy. In terms of measurement, we allow you to configure your client to most effectively utilize your device, which can be helpful. In terms of individual measurements, we don't attempt to get into RSSI-based location estimation, instead choosin...

I think we're talking further in private, but as a larger question:

does the WiGLE community have a source of information for free/open SSIDs or other deployment parameters?