Digital Building Surface Model (MDSE) of LIDAR of 1 meter resolution of the province of Alicante 2016

Open data API in a single place

Provided by Generalitat Valenciana

Get early access to Digital Building Surface Model (MDSE) of LIDAR of 1 meter resolution of the province of Alicante 2016 API!

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

Dataset information

Catalog

Generalitat Valenciana catalog

Country of origin

Spain

Updated

2025.09.18 22:00

Created

2024.07.08

Available languages

English

Keywords

España, Año 2016, Edificios, ICV, Datos abiertos, IDEV, Comunitat Valenciana, MDS, PNOA-LiDAR, Relieve

Datasource

Official portal for European data link

Quality scoring

Dataset description

Digital Model of Building Class Surfaces (MDSE) mesh step raster 1 meter pixel of the province of Alicante. Model made up of the LIDAR classes of 2016: soil (class 2), constructions (class 6), electrical towers (class 15) and bridge boards (class 17).The distribution format of the files is 32-bit GeoTIFF. The discharge unit is by MTN50 sheets. Geodetic reference system ETRS89 and UTM projection at spindle 30. Orthometric heights. Product derived from LIDAR-PNOA 2016 CC-BY 4.0 scne.es

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

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

About api.storePrivacy Terms of Service