Skip to content

Commit 13e45b4

Browse files
committed
Fix broken markdown titles
1 parent 3fc2c2a commit 13e45b4

File tree

4 files changed

+13
-13
lines changed

4 files changed

+13
-13
lines changed

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
#CONTRIBUTING
1+
# CONTRIBUTING
22

33
We welcome new contributors. Here you can read our guidelines to contribute to the IRIS project.
44

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,13 +28,13 @@ Further documentation about the IRIS-terminology can be found here: [terminology
2828
If you are interested to use IRIS in Switzerland read this: [ASTAG](docs/astag.md)
2929

3030

31-
#Prerequisites
31+
# Prerequisites
3232
- MariaDb 5.5 or higher
3333
- Maven 3 or higher
3434
- JDK 8 or higher
3535

3636

37-
#Getting started
37+
# Getting started
3838

3939
Simply clone this repository
4040
```sh

docs/astag.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
#ASTAG
1+
# ASTAG
22

33
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.

docs/terminology.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
#Terminology
1+
# Terminology
22

3-
##Terminal
3+
## Terminal
44

55
*inland (hinterland) container terminal*
66

@@ -12,12 +12,12 @@ Usually geographical division. (*Oberrhein, Mittelrhein, Niederrhein*) / (*Rhein
1212
Contargo uses three regions among other things to assign and store the CO₂-parameter of our barge fleet.
1313

1414

15-
##Seaport
15+
## Seaport
1616
Location on a coast where sea vessels and barges can dock and transfer cargo from or to land.
1717
Container seaports handle cargo in containers by different mechanical means. (crane, AGV, reach stacker)
1818

1919

20-
##Connections
20+
## Connections
2121
This shows the possibilities to connect a seaport and an inland terminal.
2222
Different and multiple connections are possible. For example barge or rail or both.
2323

@@ -27,11 +27,11 @@ Different and multiple connections are possible. For example barge or rail or bo
2727
* **Subconnections:** Subconnections model parts of connections. Those parts are only relevant if it is a connection of type Barge-Rail.
2828

2929

30-
##Static Addresses
30+
## Static Addresses
3131
A static address is a city with its corresponding postal code and country. For example *68159 Mannheim, Germany*.
3232

3333

34-
##Route types
34+
## Route types
3535

3636
* **Barge:** Transport of goods / cargo on barge.
3737
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
4040
* **Truck:** Transport of goods / cargo from and to seaports and inland terminals and the loading / unloading site.
4141

4242

43-
##Route Combination
43+
## Route Combination
4444

4545
* **Waterway:** Transport per barge between seaport and inland terminal and additional transport per truck to the loading / unloading site.
4646
* **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
4949
* **Roundtrip:** Waterway, Railway, Waterway-Rail or Direct Truck transport from seaport to loading / unloading site and back to seaports.
5050
* **All:** A list of all the possibilities for transport for a given loading site.
5151

52-
##Route Revision
52+
## Route Revision
5353

5454
A Route Revision gives the possibility to override the calculated distances between a geolocation and a terminal given by OSRM.
5555
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.
5656

57-
###Example
57+
### Example
5858

5959
1. A Route Revision exists with Terminal **Mannheim**, geolocation 49.451369,8.1030178 and radius 100m.
6060
2. There is a routing between the Terminal **Mannheim** and the geolocation 49.451367,8.1030177.

0 commit comments

Comments
 (0)