Flight paths for flying squirrels in Espoo

Open data API in a single place

Provided by Espoon kaupungin kaupunkiympäristön toimiala

Get early access to Flight paths for flying squirrels in Espoo API!

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

Dataset information

Country of origin
Updated
Created
2016.01.18
Available languages
English
Keywords
flygekorre, luonnonsuojelu, flying squirrels, nature protection, naturskydd, nature, natur, liito-oravat, luonto
Quality scoring

Dataset description

The points where flying squirrels could fly over the main roads of Espoo have been investigated with the help of a point cloud. The end result is a set of lines in raster format (TIF, bitmap). The plane coordinate system is ETRS-GK25FIN (epsg:3879) and the vertical coordinate reference system N2000. When calculating the lines, the height has been calculated for each laser point. All trees over 2 m in height have been taken into account because they can be flown into. At the top and bottom of the trees, 0.5 m has been removed. The ratio of the tree level difference to the gliding distance is 1:3, so when the height difference in the trees is 10 m, the maximum flight distance is 30 m. The analysis does not take into account all terrain barriers, such as noise barriers. Possible structures should be checked in the terrain. The scanning data is from 2013.
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