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.
Limitation of liability¶
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.
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:
- Disseminating material that is abusive, obscene, pornographic, defamatory, harassing, grossly offensive, vulgar, threatening, or malicious
- Aiding or implementing practices violating basic human rights or civil liberties
- Disseminating or storing material that infringes the copyright, trademark, patent, trade secret, or other intellectual property right of any person
- Creating a false identity or otherwise attempting to mislead others as to the identity or origin of any communication
- 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
- Interfering with or attempting to gain unauthorized access to any computer network
- Transmitting viruses, trojan horses, or any other malicious code or program
- Engaging in any other activity deemed by OpenRouteService to be in conflict with the spirit or intent of these Terms
Terms of Service¶
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.
Commercial usage of the services provided by OpenRouteService does need approval! 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:
- Single End Use
- 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.
- Commercial/ Enterprise Use
- 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 firstname.lastname@example.org to get an individual quote.
- Public funded Institution/ NGO
- 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@example.com to get an individual quote.
Copyright and use of our Services¶
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).
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:
- Sending too many requests per day
- Sending requests too fast, i.e. too many requests per second
- Sending requests too fast for too long or otherwise abusing the web service
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.
Change of terms or services¶
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.
- Cookies (for OpenRouteService.org)
- Location Information
- 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.
- Information Collection
- 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.
Content is available under Creative Commons Attribution-ShareAlike 2.0 license. Version last modified: 11.02.2016