OpenTripPlanner instance for Montréal

This page is based on the work done to setup an OpenTripPlanner instance for the region of Montréal, Canada. This is based on the work done by Guillaume B arreau and Nicolas Saunier. 90% of the work is detailed in the OTP wiki, but some specific steps needed some precision.

##Custom Graph##

The build of the graph is based on the Custom Graph section of 5 minutes introduction from OTP wiki.

Here are the specific elements:

###Open Street Map### In order to get the Open Street Map data, the simplest option is to download a metropolitan area file. For example Teczno provide a Metro Extract containing most of the north american metropolitan areas (and others).

###Elevation Data ### For the elevation data, OTP usually works with NED data in the US but this dataset does not cover Canada. In order to get elevation data (which is useful for biking), the Reverb ASTER data are needed.

The data portal is here and there is a howto document. The important step is to use the map in the left panel to select a geographical area needed to cover the graph.

For example, to cover the Montréal metro area, the following files were needed:

• ASTGTM2_N45W073.zip
• ASTGTM2_N45W074.zip
• ASTGTM2_N45W075.zip
• ASTGTM2_N46W073.zip
• ASTGTM2_N46W074.zip
• ASTGTM2_N46W075.zip

The OTP graph builder is only able to process single files, so the gdal-bin package is needed to merge the DEM files with a commande like:

	gdal_merge.py ASTGTM2_N4*_dem.tif mtl.tif

Which will result in a geotiff file ready to be processed by graph builder.

The builder configuration item for elevation looks like that:

    <bean id="nedBuilder" class="org.opentripplanner.graph_builder.impl.ned.NEDGraphBuilderImpl">
        <property name="gridCoverageFactory">
                <bean class="org.opentripplanner.graph_builder.impl.ned.GeotiffGridCoverageFactoryImpl">
                    <property name="cacheDirectory" value="/otp/cache/ned/mtl.tif" />
                </bean>
        </property>
    </bean>

###GTFS###

GTFS files have to be located where available. The graph builder is able to download them if an URL is provided.

###Auto-build of the Graph###

In order to detect changes in GTFS files and build when needed, we use the script developed for Transport Montreal

##Language##

For Montreal, we wanted the default language to be french, which can be set in the config.js file:

	otp.config.locale = otp.locale.French;

This will also have the consequence of setting the metric system to 'international'.

Note: In the version used, the french.js file (and several other languages) were invalid, resulting in an awkward javascript error when trying to use the language file. This can be solved by downloading the last language file on the GitHub repository.

##Bikeshare data##

Since Open Trip Planner supports Bixi bikesharing system and Bixi is available in Montreal, some lines of configuration will make it available.

First, a little tweak. In order to have the bike sharing system visible in french, we had to add line in an obscure file. In file "webapps/opentripplanner-webapp/js/otp/application/Controller.js", add the following line under line 40:

otp.locale.French.tripPlanner.mode = otp.locale.French.tripPlanner.with_bikeshare_mode;

Then, configure the data in "webapps/opentripplanner-api-webapp/WEB-INF/classes/org/opentripplanner/api/application-context.xml" (in this case, with a refresh of the data every 5 minutes.)

<bean id="periodicGraphUpdater" class="org.opentripplanner.api.servlet.PeriodicGraphUpdater">
    <property name="updateFrequency" value="300000" />
    <property name="updaters">
        <list>
            <bean class="org.opentripplanner.updater.bike_rental.BikeRentalUpdater">
                <property name="bikeRentalDataSource">
                    <bean class="org.opentripplanner.updater.bike_rental.BixiBikeRentalDataSource">
                        <property name="url" value="https://montreal.bixi.com/data/bikeStations.xml" />
                    </bean>
                </property>
                <property name="routerId" value="mtl" />
            </bean>
         </list>
     </property>
</bean>