-
Notifications
You must be signed in to change notification settings - Fork 0
/
build-config.json
87 lines (83 loc) · 4.16 KB
/
build-config.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
// This configuration is based
// on the Finland configuration
// of HSL:
// https://github.com/HSLdevcom/OpenTripPlanner-data-container/blob/v3/router-finland/build-config.json
{
// Generate nice HTML report of Graph errors/warnings.
// "dataImportReport": true,
// OTP attempts to calculate a path straight through an OSM area using the shortest way rather than around the edge of it.
"areaVisibility": true,
// Whether we should create bike P+R stations from OSM data.
"staticBikeParkAndRide": true,
// Whether we should create car P+R stations from OSM data.
"staticParkAndRide": true,
// Visibility calculations for an area will not be done if there are more nodes than this limit.
"maxAreaNodes": 10000,
// Transfers up to this duration with the default walk speed value will be pre-calculated and included in the Graph.
"maxTransferDurationSeconds": 3600,
// This field is used for mapping routes geometry shapes. It determines max distance between shape points and their stop sequence. If mapper cannot find any stops within this radius it will default to simple stop-to-stop geometry instead.
"maxStopToShapeSnapDistance": 300,
// Limit the import of transit services to the given START date.
// Default value: "-P1Y"
"transitServiceStart": "-P2W",
// Limit the import of transit services to the given end date.
"transitServiceEnd": "P3M",
// TODO: Are all times correct without this?
// "transitModelTimeZone": "Europe/Helsinki",
// https://docs.opentripplanner.org/en/dev-2.x/sandbox/Fares/#fares-configuration
// By default OTP will compute fares according to the GTFS specification if fare data is provided in your GTFS input.
// One can disable this by setting "off".
// For more complex scenarios or to handle vehicle rental fares, it is necessary to manually configure fares. You can combine different fares (for example transit and vehicle-rental) by defining a combinationStrategy parameter, and a list of sub-fares to combine.
// TODO: Remove Digitransit-UI tweak and check for server errors
// TODO: Set to "hsl"
"fares": "off",
// Routing requests to use for pre-calculating stop-to-stop transfers.
"transferRequests": [
{
"modes": "WALK"
},
{
"modes": "BICYCLE"
}
],
// https://docs.opentripplanner.org/en/dev-2.x/BoardingLocations/#cross-referencing
// What OSM tags should be looked on for the source of matching stops to platforms and stops.
// Germany: ["ref", "ref:IFOPT"]
// Finland: ["ref", "ref:findt", "ref:findr"]
"boardingLocationTags": [
"ref",
"ref:IFOPT",
"ref:findt",
"ref:findr"
],
"osmDefaults": {
// The timezone used to resolve opening hours in OSM data.
// If this is not specified, the following warning is printed during build:
// WARN (OpenStreetMapProvider.java:134) Missing time zone for OSM source file - time-restricted entities will not be created
"timeZone": "Europe/Berlin",
// TODO: Make this configurable via .env
// The named set of mapping rules applied when parsing OSM tags.
// default | norway | uk | finland | germany | atlanta | houston | portland
"osmTagMapping": "germany"
},
// TODO: add DEM/GeoTIFF to pipeline
// Reusing elevation data from previous builds: Write out precalculated elevation data.
// Over time, various edits to OpenStreetMap will cause this cached data to become stale and not include new OSM ways. Therefore, periodic update of this cached data is recommended.
// "writeCachedElevations": true,
"multiThreadElevationCalculations": true,
// Precompute geoid difference values at a more granular level
// to match end users' intuitive understanding of elevation.
"includeEllipsoidToGeoidDifference": true,
// By default, OTP expects the elevation data to use metres. However, by setting elevationUnitMultiplier in build-config.json, it is possible to define a multiplier that converts the elevation values from some other unit to metres.
// "demDefaults": {
// "elevationUnitMultiplier": 0.1
// }
"transitFeeds": [
{
"type": "gtfs",
"source": "gtfs.zip",
// Overrides any feed ID defined within the GTFS feed itself (feed_info.txt).
"feedId": "1"
}
]
}