You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When routing involves loading places that are located in Switzerland (i.e. the loading place is either origin or destination of a route part), distances are always calculated based on static addresses and associated route revision data. This means, that even when a user selects a Nominatim address (i.e. a non-static addresses), that address gets mapped to the best matching static address. If this mapping is not possible (e.g. if there is no appropriate static address), then the routing will not succeed. Using static addresses only when routing to/from loading places in Switzerland accommodates the [ASTAG](http://www.astag.ch/) requirement: distances to various locations are defined and published by ASTAG. In IRIS these distances are represented as route data revisions.
Contargo uses three regions among other things to assign and store the CO₂-parameter of our barge fleet.
13
13
14
14
15
-
##Seaport
15
+
##Seaport
16
16
Location on a coast where sea vessels and barges can dock and transfer cargo from or to land.
17
17
Container seaports handle cargo in containers by different mechanical means. (crane, AGV, reach stacker)
18
18
19
19
20
-
##Connections
20
+
##Connections
21
21
This shows the possibilities to connect a seaport and an inland terminal.
22
22
Different and multiple connections are possible. For example barge or rail or both.
23
23
@@ -27,11 +27,11 @@ Different and multiple connections are possible. For example barge or rail or bo
27
27
***Subconnections:** Subconnections model parts of connections. Those parts are only relevant if it is a connection of type Barge-Rail.
28
28
29
29
30
-
##Static Addresses
30
+
##Static Addresses
31
31
A static address is a city with its corresponding postal code and country. For example *68159 Mannheim, Germany*.
32
32
33
33
34
-
##Route types
34
+
##Route types
35
35
36
36
***Barge:** Transport of goods / cargo on barge.
37
37
Barge transport only happens between seaports and inland terminals or between inland terminals that are connected by a major river or canals.
@@ -40,7 +40,7 @@ Barge transport only happens between seaports and inland terminals or between in
40
40
***Truck:** Transport of goods / cargo from and to seaports and inland terminals and the loading / unloading site.
41
41
42
42
43
-
##Route Combination
43
+
##Route Combination
44
44
45
45
***Waterway:** Transport per barge between seaport and inland terminal and additional transport per truck to the loading / unloading site.
46
46
***Railway:** Transport per rail between seaport and inland terminal and additional transport per truck to the loading / unloading site.
@@ -49,12 +49,12 @@ Barge transport only happens between seaports and inland terminals or between in
49
49
***Roundtrip:** Waterway, Railway, Waterway-Rail or Direct Truck transport from seaport to loading / unloading site and back to seaports.
50
50
***All:** A list of all the possibilities for transport for a given loading site.
51
51
52
-
##Route Revision
52
+
##Route Revision
53
53
54
54
A Route Revision gives the possibility to override the calculated distances between a geolocation and a terminal given by OSRM.
55
55
It is defined by a Geolocation, the responsible terminal, a radius and the three distances that would replace the distances provided by OSRM - Truckdistance Oneway, Tolldistance Oneway, Airline Distance.
56
56
57
-
###Example
57
+
###Example
58
58
59
59
1. A Route Revision exists with Terminal **Mannheim**, geolocation 49.451369,8.1030178 and radius 100m.
60
60
2. There is a routing between the Terminal **Mannheim** and the geolocation 49.451367,8.1030177.
0 commit comments