search

codeforkansascity / Neighborhood-Dashboard

We're working to help neighborhoods help themselves by giving them easy access to useful data to allow them to identify and track problem areas in their neighborhood.
https://neighborhood-dashboard.codeforkc.org/
MIT License
18 stars 9 forks source link

Attempting to view vacancies does not render correctly #121

Closed nerdenator closed 7 years ago

nerdenator commented 7 years ago

Problem: If you just select a neighborhood and "view vacancies", no markers are placed on the map. If you then set a filter of showing all vacant properties and click "Done", the markers again fail to show. However, if you then select another neighborhood, and set a filter of showing all vacant properties and click "Done", the markers appear... not in the currently selected neighborhood, but in the neighborhood that you tried to see vacancies in before. It is not known if selecting a number of neighborhoods before attempting to view the vacancies on a neighborhood has an impact on this bug.

This was experienced on Wednesday, July 19th, 2017 in production on a machine running Google Chrome Version 59.0.3071.115 (Official Build) (64-bit) on Apple Mac OS X El Capitan Version 10.11.6. No attempt has been made to duplicate this bug in other web browsers or operating systems.

nerdenator commented 7 years ago

Closing because the issue doesn't seem to be that some vacancy reports don't render... it's just that they don't render quickly. You can go in and select another neighborhood in the time it takes to render, which creates the illusion that you get the old neighborhood when you want to view the vacancies for the current neighborhood.

It may be worth investigating how to speed up the marker rendering.