[mweil]

You got it! No storage costs. We have a soft limit of 20k per object, but I doubt many people are going to come close to brushing that. And it's all free right now anyway.

Someone just tweeted at us earlier about GeoJSON (http://geojson.org/) which looks pretty awesome for storing polygon data. It sparked a conversation internally about a feature like that, especially since SimpleGeo (which offered that, I believe) is gone.

That point aside, geofencing queries are coming soon. That means that instead of just giving a center point and radius in your query, you can query with a polygon defined by arbitrary points and we will return your objects that exist inside that shape. Perhaps that could hold you over for the time being?

[epaulson]

I want to do intersections of polygons - think "what neighborhoods have overlap with this political district." Many systems seem to have one but not the other, i.e. "store points, query by polygon", or "store polygons, query by point(and maybe radius)".

Storing polygons is probably key - if there's a query-by-radius or bounding box I can make an enclosing circle for my query and then do my own intersection tests with my query polygon.