List view
Clean up the interface. This will include breaking changes.
Overdue by 12 year(s)•Due by March 5, 2014•0/3 issues closedAllow stats by bounding box/polygon or by collector. Doing this well depends on the work in the "response restructuring" milestone.
Overdue by 12 year(s)•Due by February 21, 2014•2/5 issues closedRestructure response objects so that we have at most one object per base feature. An array of entries will account of multiple entries on a base feature. The restructuring will also switch us to index polygons using a 2dsphere index rather than points using a 2d index. These changes will support better stats functionality.
Overdue by 12 year(s)•Due by February 14, 2014•3/3 issues closedClients should be able to CRUD lists of geospatial objects. Lists are very simple: a GeoJSON feature collection object with the properties ```name``` (a String) and ```users``` (a list of user IDs who can edit the object). List items are geoJSON objects with the properties ```humanReadableName``` (usually the street address), ```created``` (datetime created) and ```objectId``` (id of the object, usually a parcelId. The feature collections should be stored as objects in an appropriately named mongodb collection.
Overdue by 12 year(s)•Due by September 27, 2013•0/6 issues closed