We don't want to leave you with uncertainties. Here is a thorough
list of frequently asked question that might be of help.
To register a new GeoDataHub (GDH) account, user needs to enter the following data
Before completing registration, it is required to accept End User Licence Agreement.
A verification link will be sent to the email provided, and after confirmation, user can log in to GDH portal.
As a part of the registration process it is mandatory to sign End User Licence Agreement (EULA) by approving it with a checkmark.
The Agreement remains in force for an unspecified term (indefinite duration).
Nevertheless, it is still possible to end a signed Agreement any time by deleting the GDH account related to it.
It is possible to end a signed Agreement by deleting the GDH account related to it. In this case, the Agreement is terminated at, and the account of the Licensee will remain active until the end of the month (billing period). At the end of that month, the Licensee is invoiced for the Service used in the last month (last billing period).
Without ending the Agreement, it is possible to stop payments by choosing Development pricing plan (free plan).
As long as any of the paid plans is chosen, payments will not be stopped even if all API keys are disabled.
To an account, only one user can be signed in at a time.
When the same username is used to log in during an active session, the previous user is automatically logged out.
GDH administrator has a possibility to suspend users by freezing their accounts. It may happen mainly because of unpaid bills.
With frozen account it is possible to enter the portal and see everything, but change nothing. All API keys are disabled and it’s not possible to activate them.
Frozen account can not be deleted.
If needed, settings of a frozen account can be changed by administrator.
API key is a validation tool that, via unique key token, handles access to GDH services.
Depending on the active pricing plan, it is possible to create either one or many API keys to an account, and each API key can have individual service configuration.
When a new account is created, the system automatically generates an API key to it, and connects it to all services.
On Keys & Services › Key details it is easy to configure which services are linked to API key, and after saving, the changes will be effective immediately.
As statistics can be modulated by API keys, applying different key for each application gives a great possibility to monitor application-based service usage.
Keys can be set inactive and back to active whenever needed. Request with a disabled API key does not return response and an error message is returned instead.
Keys & Services › Create new key
When creating a new API key, a name must be assigned to it. Within an account all API key names must be unique.
Each new key is automatically saved as active (enabled). In case Developer plan is chosen, user gets notified that the currently active key must be set inactive before creating a new one (because in Developer plan it’s allowed to have only one active key at a time).
A unique key token (validation code) is automatically created to each API key. The token is used to authorize and identify service usage by the related API key.
Keys & Services › Key details
Services are divided into thematic groups. Each API key must have at least one service group related to it.
It is possible to modify API key settings (name, related services and status), but the automatically generated unique API key token is unchangeable.
It is not possible to delete any API keys.
To make an API key unusable, simply set its status to “disabled” (Keys & Services › Key details).
All services are monetized based on point system. One point has a fixed price and each service, based on its specifics, has a certain predefined number of requests set for one or more points. So each service is charged according to the combination of points used and the fixed price of one point.
According to expected volume of usage and number of API keys needed, it’s possible to choose between different monthly pricing plans.
Each plan has a certain point limit that can be used within the fixed price. After the point limit is exceeded, you may either suspend services until next billing period or continue using services with Metered plan.
Pricing plan applies to the whole account - to all API keys jointly. To get a complete overview of service usage distribution between your API keys, go to either Keys & Services › All keys or Statistics.
Yes, after signing up and logging in to the GDH portal, you are welcome to choose Free plan.
With Free plan it’s possible to use all services and create an unlimited number of API keys until exceeding monthly point limit of 5000 points.
After exceeding the monthly point limit, all keys are automatically closed and services unusable. With Free plan it is not possible to use Metered system.
Development plan is also for free, but the usage is limited to 100 points per day and only one active key can be used.
When an active plan is switched to a bigger one, the change will be applied immediately and the current billing period will be charged according to the new plan.
When an active plan is switched to a smaller one, the change will be applied at the beginning of the next billing period (month).
With paid plans you may choose what happens after monthly request limit is exhausted. You may either suspend services until the next billing period or continue using services with Metered plan.
With Metered plan all keys and services remain usable and each additional point is charged separately. When billing period ends, the Metered points are summed up and added to the monthly fee.
Cost of a Metered point differs according to the fixed plan chosen.
User can also reject Metered plan, and in that case, after exceeding point limit, all services will be suspended (remain inactive) until the next billing period.
Each billing period runs from the 1st to the last day of each calendar month.
If a paid pricing plan is activated in the middle of a month, the Service is still billed for the whole month (billing period).
When choosing a paid plan, user is asked and obliged to enter contact information and confirm its correctness. All the paid plans are invoiced monthly.
Invoices are composed automatically according to the active plan (plus additional usage volume, if applied), and sent monthly to user’s billing email.
When a paid plan is activated with all API keys disabled, the Service will still be billed, even though the services were not used at all.
After each billing period an invoice is sent to the billing email saved in the Account settings. Payment must be made by bank transfer according to the invoice received.
All received invoices are also listed and downloadable on Plans & Billing › Billing history.
On Plans & Billing › Billing status all the main characteristics about usage and billing of the current billing period are shown, including
When Metered plan is activated and usage has exceeded monthly limit, the billable amount changes on a rolling basis.
On Plans & Billing › Billing history you can find all previous invoices and their status based on either paid or unpaid.
All invoices are downloadable as PDFs.
GeoDataHub is a center of different geoservices that are divided into three thematic groups:
Coloured and grayscale basemaps covering the whole Baltics. The map is rich in details and designed in aesthetic soft colour palette.
Grayscale basemap enjoys all the same perks and treatments as Coloured basemap, but just without colors. Therefore it is ideal for depicting your own thematic layers on top of it, as the basemap itself rather stays in the background.
Geocode API is a service for finding geographical coordinates and structured output for entered addresses. Service analyses the input text and responds by the list of address point candidates, ordered by relevance.
Reverse Geocode API is for finding address for geographical coordinates.
Address component service (Gazetteer) returns address tree, all child nodes of requested address level, and/or detailed information of any existing address. Used mainly for constructing address forms with dropdowns selections.
POI API is a service for finding structured output and geographical coordinates for points of interest.
Routing API is a service for finding the shortest or the fastest route between two or more geographical points. GeoDataHub Routing API is based on OSRM Routing Engine.
Traveling Salesman Problem (TSP) can calculate optimal point sequence for up to 100 points, rearranging all the waypoints between start and end to the most optimal order.
Data of Estonia, Latvia and Lithuania is available in all GDH services.
Overview of vendors by services:
| Estonia | Latvia | Lithuania | |
|---|---|---|---|
| Basemaps | Maa-amet ¹ | Jāņa sēta | Jāņa sēta |
| Locations | Maa-amet + OSM ² | Jāņa sēta + VZD ³ | Jāņa sēta + OSM |
| Directions | OSM | Jāņa sēta | Jāņa sēta |
¹ Maa-amet - Estonian Land Board
² OSM - © OpenStreetMap contributors
³ VZD - Valsts zemes dienests (Latvian State Land Service)
Data layers behind GDH services are updated continuously according to the actual changes in real life. The updates are performed seamlessly and do not cause downtimes.