Terms of service

Client identification

The service requires no registration, but each request need to identify the app that is making the request.

We identify requests using one of two http request headers:

• Origin
• User-Agent

If you use our service directly from the browser, we will check the Origin header set by the browser.

If you use our service from a backend service, you must set the User-Agent request header to something specific and recognizable. E.g on a format like <Name of app>/<company-email-address>.

In cases where the client do not identify itself in the above mentioned way, it can be heavily rate-limited or even blocked.

Personal data

We log all requests to our service, which includes the IP address of each request. We use these logs only for the purpose of:

• Usage statistics.
• Traffic management.

These logs are short-lived and are not archived. This might change in the future, and if so we will notify our users via yr-maps-users@lists.met.no.

Company email addresses (used in User-Agent headers) are not considered personal information for GDPR and other privacy purposes. For more information, see our Privacy Policy Statement.

Usage limits

The service has no strict limit on usage, but traffic from a client application should stay below 80 requests pr. second on average. That is, high temporary peaks is expected and fine, as a lot of requests are needed to access all tiles for a given map presentation.

Avoid unnecessary usage by making use of response cache-headers to cache data locally.

Please note that usage limits might change without notice if its needed to protect the stability of the service.

Versioning

When the service is no longer in beta, and major changes are required, we will version by adding a version number in the url path, e.g /api/v2.

If this happens will notify users in advance through our mailinglist.

Conditions for data use

Unless specified otherwise, all data and products are licensed under Creative Commons 4.0 BY International licence.