Development of the National Altitude Transformation Model between SVS2000/Trieste and SVS2010/Koper (ŠTUDIJA)

Open data API in a single place

Provided by MINISTRSTVO ZA NARAVNE VIRE IN PROSTOR, GEODETSKA UPRAVA REPUBLIKE SLOVENIJE

Get early access to Development of the National Altitude Transformation Model between SVS2000/Trieste and SVS2010/Koper (ŠTUDIJA) API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
državni koordinatni sistem, SVS2010, višinski sistem, mareograf Koper
Quality scoring

Dataset description

In Slovenia, at the end of 2018 (Decree determining the parameters of the vertical part of the vertical component of the national spatial coordinate system, 2018) we moved to a new elevation system with the designation SVS2010 (EPSG 8690) with an elevation date of 2010 (Koper), which replaces the old elevation system with the designation SVS2000 (EPSG 5779) with an elevation date of 2000 (Trieste). The study developed a single elevation transformation model for the territory of Slovenia, consisting of the elevation transformation surface - SLO-VTP2024, the elevation transformation programme - ViTra and the surface to assess the accuracy of the elevation transformation surface. The elevation transformation model will allow different spatial data managers to easily transition from the old to the new elevation system.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks