The current methodology for adding incidents to the map is rather slow when presented with more than a handful of incidents at a time. I.e., rendering the entire dataset as it currently exists (only about 1000 items) takes a few seconds. It might be possible to speed this up in a few different ways:
[ ] Break the single AJAX boundary search call into smaller chunks, processing each subset individually, allowing the map to refresh before handling the next chunk.
[ ] Cull already handled markers from the incoming result set; these markers have already been processed on previous calls, so no need to waste extra cycles processing them again. Note, this probably will not work too well with the previous option.
The current methodology for adding incidents to the map is rather slow when presented with more than a handful of incidents at a time. I.e., rendering the entire dataset as it currently exists (only about 1000 items) takes a few seconds. It might be possible to speed this up in a few different ways: