Initial commit.

Author: Karn

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,9 @@
+## Code of Conduct
+We like to keep things simple here.
+
+- **Be courteous** in your interactions with others; we'd like to remain as laid back as possible and build cool things. If you think Trump would tweet it, then it may not be the way you want to get your message across.
+- **Value opinions** -- disagreements can be a great tool to reason about your ideas and to get an glimpse into the ideas of others. Let's work to understand where others are coming from and reach productive conclusions.
+- **Don't discriminate** -- everyone who writes code is welcome to do so.
+- Finally, **be awesome**! It is a great thing to be able to write code, it can be difficult to share code with the world. We respect that, and hope there's something that you learn, and perhaps can teach us on the way.
+
+This code of conduct is a short adaptation of the [Open Code of Conduct](http://todogroup.org/opencodeofconduct/).

.github/CONTRIBUTING.md

@@ -0,0 +1,13 @@
+## Contributing.
+
+###### LEGAL FORMALITIES
+By creating a pull request (which may or may not be approved) you are agreeing that you have sole owenership of the intellectual property rights of the submission of code, image assets, data or any variant thereof and that you are not making submissions in the course of work for your employer who may prohibit the sharing of material that is created while under their employment.
+
+Alternatively, if you making a submission during the course of work for your employer for whom submissions must be sanctioned, you agree that you have adequate permission to make submissions and to enter this agreement on behalf of your employer.
+
+###### CREATING A GOOD PULL REQUEST
+It is desirable, thought not absolutely neccessary that the following boxes are checked.
+- Ensure that your code is based on a fairly recent child of the master branch.
+- Have clear commit messages, this makes it easy to identify what changes were made when.
+- Include additional tests if required. This ensures that individual components behave as expected and if there are any future changes, that they do not break your code unknowingly.
+- Ensure that you've read the [code of conduct](./CODE_OF_CONDUCT.md)!

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,10 @@
+**Issue**: #
+
+**Proposed changes**:
+- E.g: Added a new visualization layer for the bicycle paths.
+
+**Notes**:
+- Remove if not-applicable.
+
+**Validation**:
+- [ ] I have read the contribution agreement.

README.md

@@ -0,0 +1,21 @@
+## Visual-UofT
+Visualizing the "University" neighborhood via Kepler.GL
+
+
+![Screenshot of the visualization from Kepler.GL](assets/image.png)
+
+
+#### INSTRUCTIONS
+
+The Kepler Config file can be found under the main repo directory as the file `keplergl.json`. You can feed this json directly into the Kepler.GL site to begin playing around with the data.
+
+1. Navigate to the Kepler.GL demo website: http://kepler.gl/demo
+2. Select the "Load Map using URL" tab.
+3. Enter the following URL: `https://raw.githubusercontent.com/Karn/visual-uoft/master/keplergl.json`
+4. Click/tap "Fetch" to load the map.
+
+#### CONTRIBUTING
+There are many ways to [contribute](./.github/CONTRIBUTING.md), you can
+- submit bugs or improve the visualization,
+- help track issues,
+- review code changes.