This repository has been archived by the owner on Feb 2, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 36
/
contact.html
805 lines (794 loc) · 50.3 KB
/
contact.html
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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
<html>
<head>
<title>OpenRouteService.org Contact</title>
<link id="stylesheet" rel="stylesheet" type="text/css" href="css/bootstrap.min.css">
<link id="stylesheet" rel="stylesheet" type="text/css" href="css/contactPage.css">
<link href='https://fonts.googleapis.com/css?family=Source+Sans+Pro' rel='stylesheet' type='text/css'>
</head>
<body data-spy="scroll" data-target=".sidebar">
<div class="navbar navbar-fixed-top" id="navbar">
<a class="brand" href="http://www.openrouteservice.org"> <img src="img/logo_ors.png" class="logo" alt="ORS"/></a>
<a class="brand" id="title" href="http://www.openrouteservice.org">OpenRouteService</a>
<ul id="topMenu">
<li>
<a href="http://www.geog.uni-heidelberg.de/giscience.html" target="_blank"><img src="img/logo_giscience.png" style="width: 45px; height: auto" alt="GIScience" class="links"/></a>
</li>
<li>
<a href="http://www.geog.uni-heidelberg.de/giscience.html" target="_blank"><img src="img/unihd.png" alt="Uni HD" class="links" style="width: 70px; height: auto"/></a>
</li>
<li></li>
</ul>
</div>
<div id="sidebar">
<!-- content menu -->
<ul class="nav nav-list">
<li class="active">
<a href="#home">Home</a>
</li>
<li class="divider">
</li>
<li class="nav-header">
ORS Info
</li>
<li>
<a href="#contact">Contact</a>
</li>
<li>
<a href="#ors">OpenRouteService</a>
</li>
<li>
<a href="#services">OpenLS Services</a>
</li>
<li>
<a href="#help">ORS Help</a>
</li>
<li>
<a href="#data">Data</a>
</li>
<li>
<a href="#libraries">Libraries</a>
</li>
<li>
<a href="#donation">Donate for ORS</a>
</li>
<li class="divider">
</li>
<li class="nav-header">
Acknowledgements
</li>
<li>
<a href="#thanks">Thanks to</a>
</li>
<li>
<a href="#wiki">OpenStreetmap</a>
</li>
<li class="divider">
</li>
<li class="nav-header">
Disclaimer and License
</li>
<li>
<a href="#disclaimer">Disclaimer</a>
</li>
<li>
<a href="#termsOfUse">Terms of Use</a>
</li>
<li>
<a href="#license">License</a>
</li>
</ul>
</div>
<div data-spy="scroll" data-target="#sidebar" data-offset="0" id="pageContent">
<a name="top"></a>
<section id="home">
<h1><a name="home">OpenRouteService.org</a></h1>
<p>
<br>
OpenRouteService.org as offers Routing services by using user-generated, collaboratively collected free geographic data from <a href="http://www.openstreetmap.org" target="_blank">OpenStreetMap.org</a> - Please donate your geographic data to openstreetmap.org!
<br>
The service is based on open standards by the Open Geospatial Consortium (OGC). Currently the following services have been implemented within the frame of OpenRouteService.org, which allow you to include maps, geocoding, directories and other content in your web pages or applications. By accessing, requesting and using OpenRouteService (ORS) and the provided API, you are agreeing to our terms of use.
</p>
<div class="space_small">
</div>
<p>
<h4>We are searching for hardware sponsors, feel free to contact us!</h4>
</p>
<p>
If you intend to use OpenRouteService in your own applications please contact us. We are interested in spreading the usage of OpenRouteService in academic and non-profit projects.
</p>
<p>
<p><h4>Supported Web browsers</h4>
Please note that this project is developed by a small group of individuals. We don't have the man power to guarantee that this client works in all browsers and all operating systems. When accessing OpenRouteService.org as a Web frontend use, we currently provide full support of all provided services for any version of Mozilla Firefox, Google Chrome and Safari browsers. Any other web browser (e.g. Internet Explorer) is currently not supported.<br>
</p>
</p>
<div class="space">
</div>
<div class="space">
</div>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="contact">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="contact">Contact information</a></h2>
<p>
In case you have any further questions, concerns or feedback about this service agreement, please contact us via Email:<br>
<b>openrouteservice at geog.uni-heidelberg.de</b>
</p>
<p><br>
<a href="http://www.geog.uni-heidelberg.de/giscience.html" target="_blank"><img src="img/logo_giscience.png" class="logo_big" alt="logo GIScience" />
<img src="img/siegel_uni_hd_mittel.gif" class="logo_big" alt="logo University of Heidelberg" /></a>
</p>
<div class="space_small">
</div>
<dl class="dl-horizontal" id="dl-horizontal_mod">
<dt>
Idea
</dt>
<dd>
Pascal Neis & Alexander Zipf
</dd>
<dt>
Backend Development
</dt>
<dd>
Maxim Rylov, Enrico Steiger & Timothy Ellersiek
</dd>
<dt>
Website
</dt>
<dd>
Timothy Ellersiek, Enrico Steiger, Maxim Rylov & Oliver Roick
</dd>
<dt>
Web Mapping Service (WMS) & TileCache
</dt>
<dd>
Pascal Neis, Michael Auer & Steffen Neubauer
</dd>
<dt>
OpenMapSurfer Tiles
</dt>
<dd>
<a href="http://openmapsurfer.uni-hd.de/" target="_blank">Maxim Rylov</a>
</dd>
<dt>
Hillshade processing
</dt>
<dd>
Michael Auer & Magnus Fees
</dd>
</dl>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="ors">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="ors">Open Route Service</a></h2>
<div class="space_small">
</div>
<h3>Intro</h3>
<p>
Routing services are probably the most important application for street data - apart from visualizing them on a map. While there are a range of desktop (or even mobile) applications that can provide such functionalities also in combination with OSM data, we focus here on an approach based on the concept of interoperable Service Oriented Architectures (SOA). These are regarded as an important concept for forthcoming software architectures in general, and more and more being applied also in the GI (geographic information) sector. While SOA offer many benefits they are not the solution to all problems.
<br />
A remaining issue is the question of interoperability between different web services from different vendors offering the same or similar services but with different technical programming interfaces. This is the reason why standards are becoming more and more important for a range of applications - in particular in the institutional and governmental sector, but also beyond. Within the geographical information community here the Open Geospatial Consortium (OGC) has developed a range of standards for different GI related functionalities. This is why we choose to develop and set up a routing service that uses OSM data and provides those through the standardized interface specified by the OGC within the Open Location Services initiative (OpenLS or OLS) as one of 5 services:
</p>
<ul>
<li>
The <b>Route Service [RS]</b> determines travel routes and navigation information according to diverse criteria.
</li>
<li>
The <b>Directory Service [DS]</b> is a service that provides access to an online directory (e.g., Yellow Pages) to find the location of a specific or nearest place, product or service.
</li>
<li>
The <b>Location Utility Service [LUS]</b> provides a Geocoder/Reverse Geocoder; the Geocoder transforms a description of a location, such as a place name, street address or postal code, into a normalized description of the location with a Point geometry usually placed using Cartesian coordinates, often latitude and longitude.
</li>
<!-- <li>
The <b>Presentation Service [PS]</b> portrays a map made up of a base map derived from any geospatial data and a set of Abstract Data Types as overlays.
</li>-->
<li>
The <b>Accessibility Analysis Service [AAS]</b> provides a maximum reachability service from any given point or route for a set time duration.
</li>
</ul>
<p>
The Route Service offers a broad range of possibilities, among them several parameters that determine the result, e.g.:
</p>
<ol>
<li>
<i>RouteSummary</i> — gives meta information about the requested route, e.g.: overall distance, units, overall needed time...
</li>
<li>
<i>RouteGeometry</i> — requests the routes geometry (line string containing all waypoints of the route). It is possible to define a maximum number of waypoints.
</li>
<li>
<i>RouteInstruction</i> — these are "step by step" driving instructions of the calculated route. We realized this for various languages (e.g. German, English, Italian, ...). <br> Your language is missing? Please add your language to ORS via github <a href="https://github.com/GIScience/openrouteservice/tree/master/js/lang" target="_blank" >here</a>
</li>
<li>
<i>RouteMaps</i> — The calculated route is displayed on a route map. Amongst other possibilities an overview map as well as detailed maps of the start- and destination can be requested.
</li>
</ol>
<p>
Currently openrouteservice.org offers a end-user oriented website with an interactive map , but soon we will also make the route service available as OGC-web service, that can be used through http-based xml-requestes as specified in the OGC OpenLS Route Service specification. This will allow developers to use this servide in an open and interoperable way easily within their own applications.
</p>
<h3>OpenRouteService Coverage</h3>
<p>
OpenRouteService APIs and services are currently available worldwide, except for North- and South America (see <a href="http://wiki.openstreetmap.org/wiki/File:ORS_Coverage.png" target="_blank">Figure</a> of current coverage), due to our limited server capacities. We are planning on providing ORS also worldwide in the future but cannot provide any timeline at the moment.
</p>
<p>
<section id="services">
<div class="space">
</div>
<div class="space">
</div>
<table style="width:90%" style="dotted" border="0">
<tr>
<td width="50%"><h3>OpenLS Services</h3>(Status 01.09.2015)</td>
</tr>
<tr>
<td>Description: Through the OpenLS interface requests can be generated to the appropriate services without further query limitations. The offered API's are valid for <b> one </b> year.<br>
<br>In case you plan a long-term use of the interfaces within your projects , please contact us via Email</td>
</tr>
<tr>
<td><h4>Routing Services [RS]*</h4></td>
</tr>
<tr>
<td>Restful Webservice route request:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/routing" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/routing</a></td>
</tr>
<tr>
<td>testclient with meta information and schema file for routing service:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/routing&help" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/routing&help</td>
</tr>
<tr>
<td> direct route request via URL + parameter:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/route" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/route</td>
</tr>
<tr>
<td> graph routing profile update information:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/routing?info" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/routing?info</td>
</tr>
<tr>
<td><font size="-1">*currently the maximum request limitation is 1000/hour and user. We kindly ask you to not use the service excessively. In case the server performance will be affected we reserve us the right to block individual service user.</font></td>
</tr>
<tr>
<td><h4>Geocoding Service [LUS]</h4></td>
</tr>
<tr>
<td>Restful Webservice geocode request:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/geocoding" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/geocoding</td>
</tr>
<tr>
<td>testclient with meta information and schema file for geocoding service:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/geocoding&help" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/geocoding&help<td>
</tr>
<tr>
<td>testclient with meta information and schema file for reverse geocoding service:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/reversegeocoding&help" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/reversegeocoding&help<td>
</tr>
<tr>
<td>direct geocoding route request via URL + parameter:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/geocode" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/geocode</td>
</tr>
<tr>
<td><h4>Directory (POI Search) Service [DS]</h4></td>
</tr>
<tr>
<td>Restful Webservice directory request:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/directory" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/directory</td>
</tr>
<tr>
<td>testclient with meta information and schema file for directory service:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/directory&help" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/directory&help</td>
</tr>
<tr>
<td>direct directory request via URL + parameter:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/direct" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/direct
</tr>
<tr>
<td><h4>OpenLS Acessbility Analysis service [AAS]*</h4></td>
</tr>
<tr>
<td>Restful Webservice accessbility analysis request:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/analysis" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/analysis</td>
</tr>
<tr>
<td>testclient with meta information and schema file for analysis service:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/analysis&help" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/analysis&help<td>
</tr>
<tr>
<td>direct accesbility analysis request via URL + parameter:</td>
<td><a href="http://openls.geog.uni-heidelberg.de/testing2015/analyse" target="_blank">http://openls.geog.uni-heidelberg.de/testing2015/analyse</td>
</tr>
<tr>
<td><font size="-1">*for performance reasons only 30 minutes are currently supported</font></td>
</tr>
</table>
</p><p>
<table style="width:90%" style="dotted" border="0">
<tr>
<td><h4>Direct Routing Request (via GET)</h4></td>
</tr>
<tr>
<td style="width:50%"><b>Parameters</b></td>
<td>*start = longitude and latitude of the start position, e.g. '7.0892567,50.7265543'
<br>*via (optional) = longitudes and latitudes of the via positions separated by blank, e.g. '7.0920891,50.7295968 7.1044487,50.7247613'
<br>*end = longitude and latitude of the end position, e.g. '7.0986258,50.7323634'
<br>*routepref = the preference of the routing: 'Car', 'Pedestrian', 'Bicycle', 'HeavyVehicle
<br>*weighting = the preference of the routing method: 'Fastest', 'Shortest', 'Recommended'
<br>*distunit = distance unit of route calculation (default in kilometer 'KM', meters 'M', miles 'MI')
<br>*noMotorways = Avoid Motorways? e.g. 'noMotorways=false' OR 'noMotorways=true'
<br>*noTollways = Avoid Tollways? e.g. 'noTollways=false' OR 'noTollways=true'
<br>*noFerries = Avoid Ferrys? e.g. 'noFerries=false' OR 'noFerries=true'
<br>*noUnpavedroads (only for Bicycle profile) = Avoid unpaved Roads? e.g. 'noUnpavedroads=false' OR 'noUnpavedroads=true'
<br>*noSteps (only for Bicycle profile) = Avoid Steps? e.g. 'noSteps=false' OR 'noSteps=true'
<br>*maxspeed specify the maximum speed in km/h for the selected route profile e.g. 'maxspeed=10' see <a href="http://wiki.openstreetmap.org/wiki/Key:maxspeed" target="_blank">here</a>
<br>*instructions = Route instructions 'instructions=true' or 'instructions=false'
<br>*lang = language of routeinstructions: 'de' (Deutsch), 'en' (English), etc., all supported languagse see <a href="https://github.com/GIScience/openrouteservice/blob/master/js/lang/RouteService.languages.xml" target="_blank">here</a></td>
</tr>
<tr><td><br></td></tr><br>
<td ><b>optional Parameters</b><br>(only HeavyVehicle route profile)</td>
<td>
*hazardous = hazardous material? e.g. 'hazardous=false' OR 'hazardous=true', further info see <a href="[http://wiki.openstreetmap.org/wiki/EN:Key:hazmat" target="_blank">here</a>
<br>*value_weight = maximum weight restriction in tons
<br>*value_height = maximum height restriction in meter
<br>*value_width = maximum width restriction in meter
<br>*value_length = maximum length restriction in meter
<br>*value_axleload = maximum axleload restriction in tons
</td>
<tr><td><br></td></tr><br>
<tr>
<td ><b>optional Parameters</b><br>(only Bicycle route profile)</td>
<td>
*elevation = retrieve elevation information for each waypoint (in meters above NHN)? e.g. 'elevation=true' OR 'elevation=false'
<br>*surface = retrieve way surface information? e.g. 'surface=true' OR 'surface=false' -> requires 'instruction=true'
<br>Response surface list {Unknown = 0, Paved = 1, Unpaved = 2, Asphalt = 3, Concrete = 4, Cobblestone = 5, Metal = 6, Wood = 7, CompactedGravel = 8, FineGravel = 9, Gravel = 10, Dirt = 11, Ground = 12, Ice = 13, Salt = 14, Sand = 15, Woodchips = 16, Grass = 17, GrassPavel = 18 }
<br>Response waytype list {Unknown = 0, StateRoad = 1, Road = 2, Street = 3, Path = 4, Track = 5, Cycleway = 6, Footway = 7, Steps = 8, Ferry = 9, Construction = 10}
</td>
</tr>
</tr>
<tr><td><br></td></tr><br>
<tr>
<td><b>Example URL</b></td>
<td>
<a href="http://openls.geog.uni-heidelberg.de/route?start=9.256506,49.240011&end=9.156506,49.230011&via=&lang=de&distunit=KM&routepref=Bicycle&weighting=Shortest&avoidAreas=&useTMC=false&noMotorways=false&noTollways=false&noUnpavedroads=false&noSteps=false&noFerries=false&instructions=false" target="_blank">Bicycle & Shortest path</a><br>
<a href="http://openls.geog.uni-heidelberg.de/route?start=9.256506,49.240011&end=9.156506,49.230011&via=&lang=de&distunit=KM&routepref=Bicycle&weighting=Shortest&avoidAreas=&useTMC=false&noMotorways=false&noTollways=false&noUnpavedroads=false&noSteps=false&noFerries=false&elevation=true&surface=true&instructions=true" target="_blank">Bicycle & Shortest path & Elevation (optional) & Surface information (optional)</a><br>
<a href="http://openls.geog.uni-heidelberg.de/route?start=9.256506,49.240011&end=9.156506,49.230011&via=&lang=de&distunit=KM&routepref=Car&weighting=Fastest&avoidAreas=&useTMC=false&noMotorways=false&noTollways=false&noUnpavedroads=false&noSteps=false&noFerries=false&instructions=false" target="_blank">Car & Fastest path</a><br>
<a href="http://openls.geog.uni-heidelberg.de/route?start=9.256506,49.240011&end=9.156506,49.230011&via=&lang=de&distunit=KM&routepref=HeavyVehicle&weighting=Fastest&noMotorways=false&noTollways=false&noUnpavedroads=false&noSteps=false&noFerries=false&instructions=false&value_length=15&value_height=4&value_weight=7&value_width=4&value_axleload=2&hazardous=true" target="_blank">Heavy Vehicle & Fastest path</a><br>
</td>
</tr>
</table></p>
<table style="width:90%" style="dotted" border="0">
<tr>
<td><h4>Direct Geocoding Request (via GET)</h4></td>
</tr>
<tr>
<td style="width:50%"><b>Parameters</b></td>
<td>*FreeFormAdress = free text search of adress
<br>*MaxResponse = maximum amount of search results
<br>*lang = language (optional only for free form adress search default is 'de', e.g.'de' (Deutsch), 'en' (English), etc., all supported languagse see <a href="https://github.com/GIScience/openrouteservice/blob/master/js/lang/RouteService.languages.xml" target="_blank">here</a>)
<br>*lon = longitude
<br>*lat = latitude
</td>
</tr>
<tr><td></td></tr>
<tr>
<td><b>Example URL</b></td>
<td>
<a href="http://openls.geog.uni-heidelberg.de/geocode?FreeFormAdress=Bonn,%20Meckenheimer%20Allee&MaxResponse=20&lang=de" target="_blank">Free form Adress Geocoding Search + Language</a><br>
<a href="http://openls.geog.uni-heidelberg.de/geocode?FreeFormAdress=Bonn,%20Meckenheimer%20Allee&MaxResponse=20" target="_blank">Free form Adress Geocoding Search</a><br>
<a href="http://openls.geog.uni-heidelberg.de/geocode?FreeFormAdress=Bonn,%20Meckenheimer%20Allee&MaxResponse=20" target="_blank">Reverse Geocoding Search</a><br>
</td>
</tr>
</table></p>
<table style="width:90%" style="dotted" border="0">
<tr>
<td><h4>Direct Accesibility Analysis Request (via GET)</h4></td>
</tr>
<tr>
<td style="width:50%"><b>Parameters</b></td>
<td>*position (lon/lat) = longitude and latitude of the position marker, e.g. '-0.12772,51.50715'
<br>*routePreference = preferred route profile: 'Car', 'Bicycle', 'Pedestrian', 'HeavyVehicle'
<br>*method = method of isochrones generation: 'RecursiveGrid', 'TIN'
<br>*interval= intervall of isochrones generation (in minutes): '180'
</td>
</tr>
<tr><td></td></tr>
<tr>
<td><b>Example URL</b></td>
<td>
<a href="http://openls.geog.uni-heidelberg.de/analyse?position=8.661367306640742,49.42859632294706&minutes=1&routePreference=Car&method=RecursiveGrid&interval=180" target="_blank">Accessbility Car</a><br>
<a href="http://openls.geog.uni-heidelberg.de/analyse?position=8.661367306640742,49.42859632294706&minutes=1&routePreference=Bicycle&method=TIN&interval=180" target="_blank">Accessbility Bicycle</a><br>
</td>
</tr>
</table></p>
<table style="width:90%" style="dotted" border="0">
<tr>
<td><h4>PositionLink</h4><br>In order to show the map in a certain position and zoom level use these permalink parameters. </td>
</tr>
<tr>
<td style="width:50%"><b>Parameters</b></td>
<td>*pos (lon/lat) = longitude (centre of the map),latitude (centre of the map)
<br>*zoom = zoom level
<br>*layer(optional) = default background layer (OpenMapsurfer=B000, OSM-WMS worldwide=0B000, OSM Mapnik=00B00, Stamen Map=0000B, OpenCycleMap=000B0)
</td>
</tr>
<tr><td></td></tr>
<tr>
<td><b>Example URL</b></td>
<td>
<a href="http://www.openrouteservice.org/?pos=9.004861721924154,52.27606884292058&zoom=13&layer=B000" target="_blank">PositionLink Example</a><br>
</td>
</tr>
</table></p>
<table style="width:90%" style="dotted" border="0">
<tr>
<td><h4>RouteLink</h4><br>In order to show the map with a calculated route result use the same parameters then for routing.</td>
</tr>
<tr>
<td style="width:50%"><b>Parameters</b></td>
<td>*pos (lon/lat) = longitude and latitude of the position marker, e.g. '-0.12772,51.50715'
<br>*zoom = zoom level
<br>*layer(optional) = default background layer (OpenMapsurfer=B000, OSM-WMS worldwide=0B000, OSM Mapnik=00B00, Stamen Map=0000B, OpenCycleMap=000B0)
<br>*routeWeigh = weighting method of routing: 'Fastest', 'Shortest','Recommended'
<br>*routeOpt = preferred route profile: 'Car', 'Bicycle','Pedestrian','HeavyVehicle'
<br>*routeLang = language of route instructions: 'de' (Deutsch), 'en' (English) etc., all supported languages see <a href="https://github.com/GIScience/openrouteservice/blob/master/js/lang/RouteService.languages.xml" target="_blank">here</a>
<br>*lang = language of ORS menu: 'de' (Deutsch), 'en' (English) etc., all supported menu languages see <a href="https://github.com/GIScience/openrouteservice/tree/master/js/lang" target="_blank">here</a>
<br>*distUnit = distance unit of route calculations, default meters (m)
</td>
</tr>
<tr><td></td></tr>
<tr>
<td><b>Example URL</b></td>
<td>
<a href="http://www.openrouteservice.org/?pos=8.925670599999979,52.28150333376007&zoom=14&layer=B000&routeOpt=Car&wp=8.959028134277718,52.29129590915816,8.892766842773657,52.272392560153&lang=en&routeLang=en&distUnit=m&routeWeight=Fastest" target="_blank">RouteLink Example</a><br>
<a href="http://www.openrouteservice.org/?pos=8.925670599999979,52.28150333376007&zoom=14&layer=B000&routeOpt=Car&wp=8.959028134277718,52.29129590915816,8.89039418703606,52.28759404123498,8.910135245385733,52.29588865807109,8.892766842773657,52.2723925601532&lang=en&routeLang=en&distUnit=m&routeWeight=Fastest">RouteLink Example with Via Points</a><br>
</td>
</tr>
</table></p>
<div class="space_small">
</div>
<h3>OpenGIS Location Services (OpenLS or OLS)</h3>
<p>
For further information see <a href="http://www.opengeospatial.org/standards/ols" target="_blank">specification of OpenLS v1.1</a>.
</p>
<div class="space_small">
</div>
<h3>Publications</h3>
<p>
Related Publications where our OpenLS Route Service has been applied
(e.g. in the following projects: <a href="http://www.gdi-3d.de" target="_blank" >http://www.gdi-3d.de</a> (<a href="http://www.heidelberg-3d.de" target="_blank" >http://www.heidelberg-3d.de)</a>, <a href="http://www.ok-gis.de" target="_blank" >http://www.ok-gis.de</a>, <a href="http://www.mona3d.de" target="_blank" >http://www.mona3d.de</a> etc.).
</p>
<ul class="unstyled references">
<li>Steiger, E. Zipf, A.(2015): <a href="http://k1z.blog.uni-heidelberg.de/files/2015/06/agile_2015_osm_tmc_lcl_submission.pdf" target="_blank" >Enriching OSM road networks with TMC LCL information.</a> RICH-VGI: enRICHment of volunteered geographic information (VGI): Techniques, practices and current state of knowledge. 18th AGILE Conference on Geographic Information Science. Lisbon, Portugal. </li>
<li>Steiger, E. Zipf, A.(2015): <a href="http://k1z.blog.uni-heidelberg.de/files/2015/06/osm_tmc_erstellung-eines-osm-strasengraphen-mit-tmc-lcl-informationen_agit.pdf" target="_blank" >Erstellung eines OSM Straßengraphen mit TMC LCL Informationen.</a> In: Strobl, J., Blaschke, T., Griesebner, G. (Hrsg.): Angewandte Geoinformatik 2015. Berlin</li>
<li>Neis, P. (2008): Location Based Servies mit OpenStreetMap Daten. Masterthesis</li>
<li>Schmitz,S., Zipf A. and Neis, P. (2008): New Applications based on Collaborative Geodata - the Case of Routing. XXVIII INCA International Congress on Collaborative Mapping and SpaceTechnology, Gandhinagar, Gujarat, India.</li>
<li>Neis P. und A. Zipf (2008): LBS_2.0 - Realisierung von Location Based Services mit
user-generated, collaborative erhobenen freien Geodata In: J. Roth (Hrsg.): 5. GI/ITG
KuVS Fachgespräch Ortsbezogene Anwendungen und Dienste, 4.-5. September 2008, Nürnberg.
Sonderdruck Schriftenreihe der Georg-Simon-Ohm-Hochschule Nürnberg Nr. 42, ISSN 1867-5433</li>
<li>Neis, P., Zipf, A (2008): OpenRouteService.org is three times "Open": Combining OpenSource, OpenLS and OpenStreetMaps.
GIS Research UK (GISRUK 08). Manchester.</li>
<li>Neis, P. and Zipf, A. (2007): .
<a href="http://koenigstuhl.geog.uni-heidelberg.de/publications/bonn/LBSTelecarto2007.FocusMapsWithOpenLS.last.pdf" target="_blank" >Realizing Focus Maps with Landmarks using OpenLS Services</a>.
4th International Symposium on LBS and Telecartography 2007. Hongkong.</li>
<li>
Neis, P., A. Schilling, A. Zipf (2007):
<a href="http://koenigstuhl.geog.uni-heidelberg.de/publications/bonn/GI4D2007.3DEmergencyRouteService.pdf" target="_blank" >3D Emergency Route Service (3D-ERS) based on OpenLS Specifications</a>.
GI4DM 2007. 3rd International Symposium on Geoinformation for Disaster Management. Toronto, Canada.
</li>
<li>
Zipf, A., J. Basanow, P. Neis, S. Neubauer, A. Schilling (2007):
<a href="http://koenigstuhl.geog.uni-heidelberg.de/publications/bonn/3DGeoinfo07.hd3d.final.pdf" target="_blank" >Towards 3D Spatial Data Infrastructures (3D-SDI) based on Open Standards -
experiences, results and future issues</a>.
In: "3D GeoInfo07". ISPRS WG IV/8 International Workshop on 3D Geo-Information: Requirements, Acquisition, Modelling, Analysis, Visualisation. Delft, NETHERLANDS
</li>
<li>
Neis, P., A. Zipf (2007):
< <a href="http://koenigstuhl.geog.uni-heidelberg.de/publications/bonn/97_PDF.neis.zipf.AAS.Agile07.pdf" target="_blank" >A Web Accessibility Analysis Service based on the OpenLS Route Service</a>.
AGILE 2007. International Conference on Geographic Information Science of the Association of Geograpic Information Laboratories for Europe (AGILE). Aalborg, Denmark.
</li>
<li>
Neis, P., A. Schilling, A. Zipf (2007):
<a href="http://koenigstuhl.geog.uni-heidelberg.de/publications/bonn/Neis-Schilling-Zipf-EmergencyRouteService3D-AGIT2007.final.pdf" target="_blank" >Interoperables 3D Routing auf Basis von OpenLS - Ein 3D Emergency Route Service (3DERS) als Aggregation eines Emergency Route Service (ERS) und eines 3D Route Service (3DRS)</a>.
AGIT 2007. Symposium für angewandte Geoinformatik. Salzburg. Austria.
</li>
<li>
Neis, P., A. Zipf, R. Helsper, Kehl, A. (2007):
< <a href="http://koenigstuhl.geog.uni-heidelberg.de/publications/bonn/CORP07-AAS-pn-az-final.pdf" target="_blank" >Webbasierte Erreichbarkeitsanalyse - Vorschläge zur Definition eines Accessibility
Analsysis Service (AAS) auf Basis des OpenLS Route Service</a>.
REAL CORP 2007. Wien, Austria.
</li>
<li>
Weiser, A., P. Neis, A. Zipf (2006):
<a href="http://koenigstuhl.geog.uni-heidelberg.de/publications/bonn/WSO-ERS.GISSCience.09.2006.pdf" target="_blank" >Orchestrierung von OGC Web Diensten im Katastrophenmanagement - am Beispiel eines Emergency Route Service auf Basis der OpenLS Spezifikation</a>.
In: <a href="http://www.geopoint.de/gis/" target="_blank" >GIS - Zeitschrift für Geoinformatik.</a>. 09/2006. pp. 35-41.
</li>
</ul>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="help">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="help">ORS Help</a></h2>
OpenRouteService help page: <a href="http://wiki.openstreetmap.org/wiki/ORS_Help" target="_blank">OpenRouteService Wiki</a>
<br>
OpenRouteService cares about your inquiries, problems, questions etc. As there will always be a stream of inquiries, we take strong responsibility to respond to you in short time. After you have received our automatic response email to let you know we have received your inquiry, we will usually respond shortly. Please give us time to look into your reported issue properly before getting back.
<br>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="data">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="data">ORS Data</a></h2>
OpenRouteService does use open geographic data for providing routing services, offering real time traffic information and services and depends on open source third-party libraries. These are listed below.
<ul>
<li>
Routing & Geocoding: <a href="http://www.openstreetmap.org" target="_blank">OpenStreetMap</a>
</li>
<li>
Map Background Layer: <a href="http://openmapsurfer.uni-hd.de/" target="_blank">OpenMapSurfer Tiles & WMS </a>
</li>
<li>Hillshade Layer: <a href="http://srtm.csi.cgiar.org" target="_blank">CIAT-CSI SRTM</a>. Users are prohibited from any commercial, non-free resale, or redistribution without explicit written permission from CIAT.
<br>Original data by Jarvis A., H.I. Reuter, A. Nelson, E. Guevara, 2008, Hole-filled seamless SRTM data V4, International Centre for Tropical Agriculture (CIAT)
</li>
<li>
TMC traffic Messages: <a href="http://www.bast.de/" target="_blank">BASt</a>
</li>
<li>
ORS WebFrontend: <a href="https://github.com/GIScience/openrouteservice" target="_blank">https://github.com/GIScience/openrouteservice</a> -->
Please report & fix any issues <a href="https://github.com/GIScience/openrouteservice/issues" target="_blank">here</a>
</li>
</ul><br>
<h4>OpenStreetMap use in OpenRouteService - Safety disclaimer</h4>
In order to provide OpenRouteService and all related APIs, OpenRouteService uses OpenStreetMap as a free editable geographic dataset, to derive and process a routable graph for all currently offered modes of transportation.
OpenStreetMap is not a complete or accurate map of the world and should not be used in such a manner that deficiencies, omissions, inaccuracies or errors could result in death, loss or injury. It is particularly important to realize that the maps might not be reliable. The maps are an iterative ongoing work-in-progress. OpenRouteService aims to provide maps, which can be relied upon, equally well, or better than other maps. The openly-editable wiki nature of the OpenStreetMap mapping system may help towards this goal, however it may also mean that there will always be some inaccuracies. You should make your own judgement about the accuracy of our maps. Always use our maps in conjunction with your senses, official sources and your common sense.
<h4>Route results</h4>
While OpenRouteService attempts to convey accurate route and direction information, the information contained may contain errors. OpenRouteService disclaims any and all liability for the adequacy, completeness, timeliness or accuracy of information and routing results and disclaims liability for errors or omissions in the information.
You are strongly advised not to use OpenStreetMap as your primary or sole information source for crucial and data quality dependent routing and navigation applications, such as emergency and rescue, flying, inland navigation, marine navigation, military, whitewater sports, flood prone objects and winter sports. As always, make sure you have all the necessary equipment and training, take all sensible precautions, and be aware of the risks. As stated above, we will not be held responsible.
<h4>TMC traffic information</h4>
To integrate current traffic information in OpenRouteService, a road graph with TMC LCL information based on OpenStreetMap is used. To enable this service <a href="http://www.bast.de/" target="_blank">BASt</a> (German Federal Highway Research Institute) offers an up to date Location Code List (LCL) for Germany and provides TMC real time traffic information messages. OpenRouteService does not warrant the accuracy of the traffic data used for the OpenRouteService and APIs. Such data may not always reflect reality due to, among other things, road closures, construction, weather, new roads and other changing conditions. There is no guarantee of the given accuracy of any of the visualized and for the dynamic routing used traffic messages.<br>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="libraries">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="data">JavaScript libraries</a></h2>
<ul>
<li>
<a href="https://github.com/Leaflet/Leaflet" target="_blank">Leaflet</a>
</li>
<li>
<a href="https://github.com/Leaflet/Leaflet.Editable" target="_blank">Leaflet Editable by Yohan Boniface</a>
</li>
<li>
<a href="https://github.com/MrMufflon/Leaflet.Elevation" target="_blank">Leaflet Elevation by Felix Bache</a>
</li>
<li>
<a href="https://github.com/jseppi/Leaflet.MakiMarkers" target="_blank">Leaflet MakiMarkers by James Seppi</a>
</li>
<li>
<a href="https://github.com/ardhi/Leaflet.MousePosition" target="_blank">Leaflet MousePosition by Ardhi Lukianto</a>
</li>
<li>
<a href="https://github.com/tyrasd/togpx" target="_blank">ToGPX by Martin Raifer</a>
</li>
<li>
<a href="https://github.com/mapbox/togeojson/" target="_blank">ToGeoJSON by Mapbox</a>
</li>
<li>
<a href="https://github.com/twbs/bootstrap" target="_blank">Bootstrap by Twitter</a>
</li>
<li>
<a href="https://github.com/mbostock/d3" target="_blank">d3.js by Mike Bostock</a>
</li>
<li>
<a href="https://github.com/sstephenson/prototype" target="_blank">prototype.js by Sam Stephenson</a>
</li>
<li>
<a href="https://github.com/jquery/jquery" target="_blank">jQuery by the jQuery Foundation</a>
</li>
</ul>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="thanks">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="thanks">Thanks to...</a></h2>
<ul>
<li>
<a href="http://www.openstreetmap.org" target="_blank">http://www.openstreetmap.org</a>
</li>
<li>
<a href="http://www.opengeospatial.org" target="_blank">http://www.opengeospatial.org</a>
</li>
<li>
Frederik Ramm & Jochen Topf from (<a href="http://www.geofabrik.de" target="_blank">http://www.geofabrik.de</a>) for supporting by extracting the new raw areas out of the OSM-dataset.
</li>
</ul>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="donation">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="donation">Donate for ORS</a></h2>
<p>
Help us keeping our services up to date and to be able to further improve in the future. 100% of your donation will used for the OpenRouteService project and any amount will help us!<br><br>
Heidelberg University<br>
Bank: Baden-Württembergische Bank<br>
IBAN: DE69600501017421500436<br>
SWIFT/BIC: SOLADEST<br>
Subject/Reference: "SpendenKonto OpenRouteService Abt. Geoinformatik, Prof. Zipf" <br>
</p>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="wiki">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="wiki">OpenStreetmap (OSM)</a></h2>
<p>
<a href="http://www.openstreetmap.org" target="_blank">http://www.openstreetmap.org</a>
</p>
<p>
"OpenStreetMap is an editable map of the whole world, which is being built largely from scratch using GPS traces, and released with an open content license. The OpenStreetMap License allows free (or almost free) access to our map images and all of our underlying map data, and the project aims to promote new and interesting uses of this data ..." Read more on: <a href="http://wiki.openstreetmap.org" target="_blank">http://wiki.openstreetmap.org</a>.
</p>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="disclaimer">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="disclaimer">Disclaimer</a></h2>
<p>
The data sources for routing and mapping are based on free and open and even collaborative volunteered data collection efforts. Therefore we cannot guarantee any quality of the displayed data and the routing results. We are not responsible for any errors, mistakes, omissions or other problems with the used data and occurring from using this service.
</p>
<p><h4>Limitation of liability</h4>
Under no circumstances, and under no legal theory, including negligence, shall OpenRouteService or its affiliates, contractors, employees, agents, or third party partners or suppliers, be liable for any special, indirect, incidental, consequential, or exemplary damages (including loss of profits, data, or use or cost of cover) arising out of or relating to these terms or that result from your use or the inability to use the site, including software, services, maps, content, user submissions, or any third party sites referred to on or by the site, even if OpenRouteService or a OpenRouteService authorized representative has been advised of the possibility of such damages.
OpenRouteService ensures to have technological and operational security policies and procedures to protect your information from loss, misuse, alteration, or unintentional destruction, but the OpenRouteService makes no representations or warranties regarding the security of the OpenRouteService or the transmission of data or information to and from OpenRouteService and your accessed device. OpenRouteService will not be liable to you or anyone else in the event of any unauthorized infiltration of any of its systems.
</p>
<p><h4>Prohibited Conduct</h4>
You may not use the Services for any unlawful purpose. Your use of the Services must comply with all local rules regarding online conduct and acceptable content.
You may not use the Services in any manner that could damage or overburden the Services or interfere with any other party's use of the Services.
You may not engage in other unacceptable use of the Services, which includes:
<li>Disseminating material that is abusive, obscene, pornographic, defamatory, harassing, grossly offensive, vulgar, threatening, or malicious;</li>
<li>Aiding or implementing practices violating basic human rights or civil liberties;</li>
<li>Disseminating or storing material that infringes the copyright, trademark, patent, trade secret, or other intellectual property right of any person;</li>
<li>Creating a false identity or otherwise attempting to mislead others as to the identity or origin of any communication;</li>
<li>Exporting, re-exporting, or permitting downloading of any content in violation of any export or import law, regulation, or restriction of the European Union and its agencies or authorities, or without all required approvals, licenses, or exemptions;</li>
<li>Interfering with or attempting to gain unauthorized access to any computer network;</li>
<li>Transmitting viruses, trojan horses, or any other malicious code or program; or</li>
<li>Engaging in any other activity deemed by OpenRouteService to be in conflict with the spirit or intent of these Terms.</li>
</p>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="termsOfUse">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="termsOfUse">Terms of Use</a></h2>
<p>
If you intend to use OpenRouteService in your own applications please contact us. We are interested in spreading the usage of OpenRouteService in academic and non-profit projects. <br><b>Commercial usage of the services provided by OpenRouteService does need approval!</b><br>
When accessing, requesting and using OpenRouteService and the provided APIs, depending on your daily amount of API requests and regardless of the consumer's legal entity or legal body, we distinguish between three different types of usage:
<li><b>Single End Use.</b> You are distinct single end user, i.e., an actual human being that can access OpenRouteService and the provided web services with up to 2500 requests per day free of charge. In case the server performance will be affected, we reserve us the right to limit individual service user. You may not redistribute hosted API services, nor may you permit your end user to redistribute hosted APIs, including by proxying or any other method to not avoid directly accessing our APIs. If you want to make use of the Services outside this description or should you intend to further use our services commercially (without any limit restriction), please consider a Commercial/ Enterprise Use.</li>
<li><b>Commercial/ Enterprise Use.</b> You are planning a commercial use of OpenRouteService and the provided Routing/Direction and Accessibility API with more than 2500 requests per day in total, either consumed by a single end-user or multiple seats, in a private or commercial application. In order to cover the expenses of used resources and to support further ORS enhancements in the future, we charge you a yearly license service fee. In this case you may redistribute hosted API services, and permit your end user to use and access our hosted APIs in any commercial application. Please contact [email protected] to get an individual quote.</li>
<li><b>Public funded Institution/ NGO.</b> You are planning to use OpenRouteService the provided APIs with more than 2500 requests per day in total, either consumed by a single end-user or multiple seats, in a private or commercial application as a publicly funded institution or NGO. In this case we offer reduced fares and would charge you according to the amount of requests you send to our service in order to cover expenses. Please contact [email protected] to get an individual quote.</li>
</p>
<p><h4>Copyright and use of our Services</h4>
When using the OpenRouteService APIs or using any other service provided by OpenRouteService make sure to have the copyright text "© Powered by OpenRouteService" in your API Implementation, site, or other propert(ies) (either displayed in the map image itself or elsewhere).
</p>
<p><h4>Usage Limits</h4>
If you exceed the usage limits as a free Single End User (2500 requests per day) of a given OpenRouteService API, the API will return an error message. If you repeatedly exceed the limits, your access to the API may be temporarily blocked. In this case we will inform and contact you about our Commercial/Enterprise Use.
You can exceed the usage limits for the OpenRouteService APIs by:
<li>Sending too many requests per day</li>
<li>Sending requests too fast, i.e. too many requests per second</li>
<li>Sending requests too fast for too long or otherwise abusing the web service</li>
</p>
<p><h4>Service Limitations</h4>
OpenRouteService always ensure to only publish stable releases of the provided API services. The chosen parameter, e.g. mode of transportation, avoid features, number of waypoints for Routing and isochrones time and isochrones interval for Accessibility Analysis affect the overall performance and calculation time, which may vary. Due to individual routing graph profiles for every mode of transport, the update process and the performance/computation time of route results also varies.
</p>
<p><h4>Change of terms or services</h4>
We reserve the right to modify these Terms at any time by posting the changed terms on the site. All changes shall be effective immediately upon posting. Please check these Terms periodically for changes. Your continued use of the Services after we post of changes constitutes your binding acceptance of the new terms.
We may change the features and functions of the Services, including APIs, and the terms of this license agreement may change over time. It is your responsibility to ensure that calls or requests you makes to the Services are compatible with then-current OpenRouteService APIs. We will endeavor to avoid changes to our APIs that are not backwards compatible, if any such changes become necessary, we will use reasonable efforts to notify you prior to implementation.
</p>
<p><h4>Privacy</h4>
<b>Cookies.</b> We use cookies, system logs and other data storage technologies to (a) preserve information so you will not have to re-enter it during your visit or in subsequent visits; (b) maintain sessions for authenticated users; and (c) monitor aggregate metrics such as total number of visitors and pages viewed. If you disable cookies parts of OpenRouteService.org main website may not work as intended.<br>
<b>Location Information.</b>
OpenRouteService.org allows you to approximate your geographic location, when accessed via (mobile) browser. To provide service, OpenRouteService must record your route information, including your point of origin, the address of your destination, and the route you are instructed to follow. We do not share this aggregated location information or connect this information with your personal information. Currently HTTPS is not supported.<br>
<b>Information Collection.</b>
We do not collect or store any personal information about you or personally identifiable information about you, except what you voluntarily provide through direct contact. We do not share analytic data with any service providers or partners.
</p>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
<section id="license">
<div class="space">
</div>
<div class="space">
</div>
<h2><a name="license">License</a></h2>
<p>
Content is available under <a href="http://wiki.openstreetmap.org/index.php/OpenStreetMap_License" target="_blank">Creative Commons Attribution-ShareAlike 2.0 license</a>.<br>
Version last modified: 11.02.2016
</p>
<div class="topOfPage">
<a href="#top">Top of page <i class="icon-chevron-up"> </i></a>
</div>
</section>
</div>
<script type="text/javascript" src="lib/jquery-1.7.2.min.js"></script>
<script type="text/javascript" src="lib/bootstrap/bootstrap.min.js"></script>
</body>
</html>