chouette-core/lib, branch ie-fixes Chouette manage transport static data Refs #6426; Disable "Create opposite route" action instead of hiding it 2018-04-11T06:28:47+00:00 Zog 2018-04-06T12:46:19+00:00 03b4010981f5d47fbd8dd468bbe5fc320fd7a9e4 






Merge pull request #460 from af83/6360-workbenchimport-display
2018-04-10T15:40:17+00:00

Luc Donnet

2018-04-10T15:40:17+00:00

b40a3e02db22762931a7e8e12187d5ba5bbc5618

6360 Add checks on calendars during WorkbenchImport




6360 Add checks on calendars during WorkbenchImport






Merge pull request #438 from af83/6368-gtfs-import
2018-04-10T15:30:55+00:00

Luc Donnet

2018-04-10T15:30:55+00:00

537a5078657ead0b89aa5220c05dfbc01ae94dca

GTFS import (first step)




GTFS import (first step)






Keep ci database.yml in ci:docker:clean. Refs #6047
2018-04-10T10:02:13+00:00

Alban Peignier

2018-04-10T10:02:02+00:00

dad504f5794a36be8dac97a257cdecd87704763b












Merge pull request #450 from af83/6404-way-costs--snap-distance-and-time-to-1-when-between-0-a
2018-04-10T09:04:44+00:00

Luc Donnet

2018-04-10T09:04:44+00:00

f627d82ce180fb0e487195485402d3278c03d2ef

6404: RouteWayCostUnitConverter: Snap values between 0–1 to 1




6404: RouteWayCostUnitConverter: Snap values between 0–1 to 1






Refs #6360; Add checks on calendars during WorkbenchImport
2018-04-09T09:22:40+00:00

Zog

2018-04-09T09:20:56+00:00

27442a9ffe40d0f548b1dc99ab917a8d8b0a02a2












Restore project config/database.yml in ci:docker:clean task. Refs #6047
2018-04-08T17:18:49+00:00

Alban Peignier

2018-04-08T17:18:49+00:00

03ea6bb7b8ac1cd97ec48a33d2297385cdf27b66












Update ci task to avoid problem with CHOUETTE_DEPLOY_DISABLED variable is used.  Refs #6047
2018-04-08T17:17:03+00:00

Alban Peignier

2018-04-08T17:17:03+00:00

682ea7b50124763b4c70e3a37bad1e3555698ff4












RouteWayCostUnitConverter: Snap values between 0–1 to 1
2018-04-05T13:37:42+00:00

Teddy Wing

2018-04-05T13:37:42+00:00

bfb194c5294c583dbf0bc0bef78b67d64a3a4f4c

We use integer values for distance (kilometres) and time (minutes). If
the values aren't very big, like bus stops inside a city for example,
the integer conversion will put distance and time at `0`, which isn't
correct.

To continue to use our chosen measurement units while still displaying
something that makes sense to users, snap any values >0 and <=1 to `1`.

Refs #6404





We use integer values for distance (kilometres) and time (minutes). If
the values aren't very big, like bus stops inside a city for example,
the integer conversion will put distance and time at `0`, which isn't
correct.

To continue to use our chosen measurement units while still displaying
something that makes sense to users, snap any values >0 and <=1 to `1`.

Refs #6404







Add a small log message for each TomTom invocation. Refs #6222
2018-04-04T08:02:53+00:00

Alban Peignier

2018-04-04T08:02:53+00:00

2cb5225efbb080707c060e4038ae6d48612515f0