Difference between revisions of "Setting up walkyourplace"

Revision as of 17:30, 3 April 2014

>> return to Cedeus IDE

Steps to Install the WalkYourPlace tool for Santiago

General prep steps

1. create new Ubuntu 12.04 VM with LA(M)PS ( 7773, lautaro:17022)
2. install tomcat 7 (or jetty)
3. install GeoServer + WPS plugin
4. install Php cURL (http://php.net/curl)
   • geoserver should run on port 8080, otherwise modify "call_wps.php".
5. install OpenTripPlanner (running on GeoNode VM (146.155.17.54:8080) - and compile graph with
   • Santiago OSM data
   • Santiago GTFS data
   • => test if it works
6. install PostgreSQL + PostGIS (17032 : db: wypdb)
   • install PostgreSQL

Install for Calgary

1. Install DBs
   • install crime DB (for the crimes, we considered 12 types of crime as listed in http://crimemap.calgarypolice.ca/ : weighing is in AggregationService.py)
   • install GTFS DB
2. get Browser client code "WPSClient"
   • modify browser client end point (WPS, etc.) in file call_wps.php to http://146.155.17.113:17088/geoserver/
   • put in apache's /var/www/ (i.e. /var/www/wypwps)
   • note: the map tiles, as defined in js/main.js, will still come from http://136.159.122.90/PHPTileServer/CalgaryGrey/{z}/{x}/{y}.png However, in case the TileServer is down its possible to add OSM map with

     var osmmap = L.tileLayer('http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png', {attribution: 'Map data © <a href="http://openstreetmap.org">OpenStreetMap</a> contributors'});

     plus adding this to the layer selection plus as default layer (PS: also remove setting of the map bounds, see map.setMaxBounds(bounds);)
3. get backend code
   • GeoServer WPS servers *.jar files = on for each model => install in GeoServers */WEB-INF/lib folder => restart GeoServer
     • check if it works with http://146.155.17.113:8080/geoserver/ows?service=wps&version=1.0.0&request=GetCapabilities
   • GeoProcessing Engine (access model code in Python) => put in any folder
   • modify the postgres DB access in postgis.conf
   • start each model with "run.py"
   • note, not sure, but in ManagementService.py the GeoServer URL is defined with http://127.0.0.1:8080/geoserver - maybe this needs to be changed (for use in a VM???)
4. test ic Calgary works

Modify code for Santiago

1. install PyCharm to modify client code and backend code
   • GeoServer WPS location (IP/address)
   • Postgres location and access: postgis.conf
   • Tileserver location/code in client
   • remove crime calculation in ManagementService.py
2. deploy code:
   • client side code => install on var/www/ of apache server
   • if there are no changes: GeoProcessing Engine(s) => put in whatever folder and run "run.py"
   • GeoServer WPS servers *.jar files => put in GeoServers */WEB-INF/lib folder (requires restart of GeoServer)
3. Test