Ignore Scala artifacts in .lib
Add GTFS route Scala tests
Pass errors from scala to UI
Disable Scala tests in Travis
Switch routes filter to dropdown
Prep for pointing leaflet map to scenario db
Trigger service date validation on load.
Also read service dates as UTC.
Validate sample periods are within date range when checking indicator configuration.

Fixes #452.
Cleanup route-done view

Disable back button on trip create success
Display route long name on success
Test translate attribute directive on route-done view
Add existing stops to trip via utfgrid click

Includes popup to allow the user to verify their choice
with stop name
Update route-edit view with context dependent text
Sort arrivals in headway regularity indicator

Sorts the arrivals in the headway regularity indicator; without this,
the stop arrivals appear to be ordered arbitrarily, leading to problems
such as negative average headways.
Merge pull request #465 from WorldBank-Transport/feature/headway-regularity-fix

Sort arrivals in headway regularity indicator
Fix scenario calculation

Cause indicator calculation to save results in aux database (usually
the primary database.)
Add UPDATEs to reproject the_geom to geom's SRID on scenario save
Merge pull request #469 from WorldBank-Transport/feature/fix-scenario-calculation

Fix scenario calculation
Merge pull request #463 from WorldBank-Transport/feature/add-gtfs-route-tests

Add GTFS route Scala tests
Merge pull request #467 from WorldBank-Transport/feature/disable-scala-travis

Disable Scala tests in Travis
Merge pull request #464 from WorldBank-Transport/feature/pass-errors-from-scala

Pass errors from scala to UI
Fix LengthSpec

This isn't so much a fix as changing the expected values to match what
is occurring. As best we can tell, the current test was written at a
point when ScheduledStops were not being filtered out of TransitSystems
if they fell outside of the SamplePeriod for a given indicator
calculation. Manually disabling the stop filtering fixes the LengthSpec,
but is not expected behavior and causes many other tests to fail.

It appears that the LengthSpec was broken by adding / fixing the stops
pruning functionality, but that in all the confusion around the
refactor, it was missed until later when we thought it was due to the
geometry changes. The indicator has been manually verified to be working
correctly using QGIS, so these values should be correct. If they're not,
then it's most likely a problem relating to how transit systems are
constructed, rather than a problem with the Length indicator.