thomaslorincz / trip-cluster-tool Goto Github PK

Add a label property to the Feature interface. Use the label if it is available, or use District/Zone ${id} if not.

A loading spinner will improve user experience when the data is initially being loaded.

The current clustering visualization that displays flow lines is cluttered, unnatural, and unhelpful. To improve the visualization in all aspects a choropleth scheme will be pursued. Under this new scheme, clicking on any destination geography will color the surrounding geographies based on the magnitude of trips originating from them.

Currently, there is no way to see the information specific to the selected geography. It would be helpful to display somewhere the total trips to/from the selected geography.

Add a time section to the filter control. This will require some data format restructuring to ensure downloading and parsing are performed quickly.

Add a license to the project so viewers are aware of how they are allowed to use it.

Adding a tooltip on hover will allow users to easily see information about a particular geography. Currently, the selection control displays information related to the current selection. However, this is not as intuitive or natural as a hover interaction.

Adding a test suite will improve the maintainability and stability of this project. Testing will most likely be implemented with Jest. Once testing is implemented, a CI pipeline can be configured.

To improve the maintainability of this project, the custom MVP components that are currently implemented will be converted to React components.

Investigate service worker caching using Webpack Workbox plugin. Ensure the implementation makes it easy to clear the service worker cache when running in development mode.

Dockerize the app so that it can be easily deployed to a new cloud vendor if needed.

Implement some kind of legend display that shows the range of values (corresponding to the choropleth colours). As well, perhaps there should be a blue outline with a label that is updated between "origin" and "destination" depending on the flow direction.

Add a command to prune dev dependencies after the code is built in Docker. Currently, all node modules are kept in the container when it is deployed.