Desktop Interface: Canvassing Map

The primary purposes of a Canvassing Record are: 1. to identify the areas that 
have been canvassed. 2. Help identify areas that need additional action because 
they need follow-up, or because the data is old.

Displaying canvassing presents the following challenges:
1. There may be one or two orders of magnitude more canvassing records than 
Work Order records.
2. Canvassing Records should be displayed in a way that conveys 
geography/location, whether action is necessary, and age of data/ staleness.
3. Conveying canvassing of an apartment complex can be difficult, since the GPS 
coordinates are more or less identical for every apartment.
4. A mobile device may not always have internet connectivity (in which case 
they may have to enter the information later, at a different physical location) 
and/or GPS capabilities.  Some user-prompted validation will be required if the 
Google Maps API and phone GPS coordinates are drastically different from one 
another.

I'm not 100% sure exactly how the map interface should look, but it should 
illustrate what roads have been canvassed, and which homes need additional 
attention.  It would also be good if "older" canvass records are de-emphasized 
somehow.

I know that's a tall order, which is why I don't have a good/easy solution.

Note: Issue 114 must be completed first.

Original issue reported on code.google.com by v...@aarontitus.net on 1 Jan 2013 at 10:55

google-code-export / sandy-disaster-recovery

Desktop Interface: Canvassing Map #115