Thanks for the feedback.
- The program does seem to require a lot of RAM.
Unfortunately, I believe that much of the RAM is used by google's map component. I hope to get around it by consolidating close addresses on wide zooms, but this will require a lot of coding and won't be done soon.
If one is looking at doing any kind of change of ward boundaries, the entire stake dataset would be required.
Actually, with the way that I intended the program to be used, the wards would make sure their GEO codes are accurate, and then the stake would be able to use MLS directly.
- The red dots can be moved accidentally too easily.
Ok, I'll work on this.
The ability to print reports would be nice.
What kinds of reports?
The alerts and warnings lists.
On my to-do list. Meanwhile, you should be able to highlight, copy, and paste each alert's list (from the "List" button) into any word processor and print it from there.
A summary report, similar to that in MLS, for a proposed region.
If the information were up-to-date in MLS, then you could just use MLS. Is there a particular advantage to having it here? I don't want to duplicate MLS functionality.
And a listing of households with their assigned geocodes to enable manual entry of geocodes into MLS.
This is sort of available. If you draw regions and assign them to GEO codes, then the Alerts window will have a list of addresses that are assigned to the wrong GEO code. This makes it very fast to find the addresses that need updating. Again, you'd have to copy and paste the list into a word processing program.
The map print is of very limited use, as we are spread over a huge area. I'm not sure I have a solution to this???
I fully agree. I have had a few ideas on this, but none that are really good. One possibility is, once GEO codes are up-to-date in MLS, filter by individual GEO codes and then zoom to addresses and print each GEO code separately.
Thanks again for the feedback! Keep it coming!