Application deployed at https://citrics.io/.
| Anna Townsend | Daniel Briksza | John Watt | Kevin Nguyen | Michael A Harms | Muamer Kukic | Umeko Walker | Ruth Philips | Luke Townsend | Matthew Sessions | Scott Maxwell |
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
Citrics is an application that analyzes data from cities such as populations, cost of living, crime rates and many other social and economic factors that are important in deciding where someone would like to live. Citrics present such important data in an intuitive and easy to understand interface.
Cities with data are marked on a searchable, indexed map generated from the Mapbox.com API. Selected markers populate navigable data graphs powered by the Chartjs library that indicate important information about the selected city. Graphs are generated dynamically as users adjust their selection of cities to compare.
- Allows users to search city data set without logging in
- Data visualization of city metrics
- Map visualization that allows users to navigate and browse cities
- Autofill search feature to streamline city searching
- Specific city metrics accessible through side navigation
- User account creation
- Quiz users to indicate their priorities in a city. This will power DS prediciton engine
- Allow users to save records of which cities important to them
- Expanded data set - Pending DS completion, this app aims to encompass data from ~30000 US cities
- User-friendly API access to DS model via multiple endpoints (Premium feature)
- React
- Sass
- Chart JS
- Mapbox
- Font Awesome
- React-scroll
- Familiarity with React (lower technical debt)
- Dynamic data rendering
- Web optimized
- Lightweight
MapBox is an open source mapping platform for custom designed maps.
In the root folder, run "yarn"
- yarn start (starts local server)
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct. Please follow it in all your interactions with the project.
If you are having an issue with the existing project code, please submit a bug report under the following guidelines:
- Check first to see if your issue has already been reported.
- Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
- Create a live example of the problem.
- Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes, where you believe the issue is originating from, and any potential solutions you have considered.
We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.
If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project.
Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.
- Ensure any install or build dependencies are removed before the end of the layer when doing a build.
- Update the README.md with details of changes to the interface, including new plist variables, exposed ports, useful file locations and container parameters.
- Ensure that your code conforms to our existing code conventions and test coverage.
- Include the relevant issue number, if applicable.
- You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
These contribution guidelines have been adapted from this good-Contributing.md-template.