An interactive transit corridor “modifier/builder,” available as a web based tool and intended for use as an interactive, browser-based tool presented in an interactive transit exhibit. Learn more: http://mittransportanalyst.github.io/
Note to users: There are scroll bar issues present. Also, recorded issues of
post fails on retrieving large geoJSONs. For usability, make sure you are running Mozilla FF (latest version). Also, since we have yet to custom remove the scroll bar issue - if you are running a Windows OS, use https://userstyles.org/styles/5449/scrollbar-hidden-hide-scrollbars-totally to deal with the scroll bar situation.
View staging server online
See an online demo at http://mittransportanalyst.github.io/boston/. Due to cross-origin request issues, please be sure that on Heroku you are going to
http and NOT
https. If you type in the address without specifically designating
http, Heroku will route you automatically to
https, so please be aware of that.
How to get this up and running
Node, npm, Bower
You need Node installed on your computer. If you do not have it, go to https://nodejs.org/ and click the green button named "Install".
npm is Node's package manager, and comes bundled. Bower is a package manager for client side libraries. Install it if you don't have it by entering
npm install -g bower in your terminal. More information on Bower can be found at http://bower.io/.
If you don't have the repo cloned already, navigate to a fresh/clean/empty directory in your computer and enter
git clone https://github.com/mitTransportAnalyst/CoAXs.git. Make sure you are in the
master branch (you should be by default), by entering
git status and checking which branch is highlighted.
bower install and
npm install to install dependencies for client and server-side libraries, respectively. You can view the dependencies in
bower.json for Bower and
package.json for Node.
Starting up node
Once all dependencies have been installed, all that's left to do is enter
npm start. Now open a web browser and navigate to
http://127.0.0.1:3000. The app should be up and running there.
(Note: Install Heroku Toolbelt. use foreman start instead of npm start)