---
id: ch4-klatovsko-data
type: spine
title: "What open data says about Klatovsko, and what it cannot say"
readingTime: 3
standalone: true
core: false
teaser: "Seven local questions, seven open layers, each with its scale, date and licence to check before an answer counts."
voice: universal
parent: null
diagram: diagram-klatovsko-map
recallQ: "Why does a local knowledge base combine several open layers instead of relying on one map, and what must it check when it does?"
recallA: "Each layer answers a different question at its own date and scale: imagery shows vegetation, LPIS shows registered farmland, the cadastre shows parcels and ownership, statistics describe statistical areas. Combining them requires checking boundaries, dates, definitions, licences and uncertainty."
highlights:
  - "LPIS shows registered agricultural use; the cadastre shows parcels and ownership. They are different layers"
  - "D4.2's Beta already uses Czech LPIS, cadastre, RÚIAN and forestry data"
  - "A spatial overlap shows a relationship, not harm or non-compliance"
  - "Publicly viewable is not the same as openly licensed"
status: accepted
concept: klatovsko-open-data
conceptTitle: "Open geodata for Klatovsko"
parents: local-geoai-kb
lang: en
lens: czech-bavaria
depth: standard
formalism: none
visuality: balanced
lengthBand: deep
genre: worked-example
state: edited
carriers: prose|table|diagram
---

Klatovsko is not a blank map for the project. In D4.2's pilot table, the Czech–Bavarian pilot uses JackDaw for **1 × 1 km attractiveness grids** comparing south-western Bohemia with eastern Bavaria. The Beta workflows already include Czech **forestry data, LPIS, the cadastre and RÚIAN**, which bring operational detail that European sources lack.

## Start with questions, then find layers

| Local question | Layer and provider | How to read it |
|---|---|---|
| How does vegetation change through the season? | Copernicus Sentinel imagery and Land Monitoring Service products | Repeated observations; clouds and acquisition dates limit comparisons |
| Which land is registered as farmland, and in what use? | LPIS, Ministry of Agriculture (eAGRI) | Agricultural land blocks and their use; not ownership |
| Where are the parcels and who owns them? | Cadastre of real estate, ČÚZK | The formal reference for parcel boundaries and ownership |
| Which addresses and buildings belong to a municipality? | RÚIAN, ČÚZK | Official territorial units, addresses and buildings |
| What do weather and water stations record? | ČHMÚ (Czech Hydrometeorological Institute) | Measurements at stations, not at every field; JackDaw adds ERA5 and WorldClim grids |
| Which roads, paths and services are mapped? | OpenStreetMap | Community-maintained and current where mappers are active; completeness varies |
| How are population and the local economy changing? | ČSÚ (Czech Statistical Office); Eurostat and GISCO for NUTS and LAU | Averages over statistical units, published with a delay |

D4.1 makes the last two rows a pair on purpose: statistics give a standard framework but average out local differences and age quickly, while OSM gives spatial detail and timeliness with uneven quality.

## An answer that can be checked

Take a question about farmland next to a Natura 2000 site (site boundaries from AOPK ČR and the EEA). A draft block overlays LPIS land blocks with the site boundary, adds ČÚZK orthophotos for interpretation, and records each dataset's date, coordinate reference system and the intersection method. That shows a **spatial relationship**. It does **not** establish ecological harm, legal non-compliance or a required management action; those need further evidence and a competent interpretation.

## Local questions already on the table

Funded third parties in this pilot (D6.3) point to the questions that matter locally: **FarmTourist** linked farms, local products and tourism; the **DIPS** ideathon covered agriculture, smart tourism, local food and planning; **LocalLinks.AI** is mapping local farms and short food supply chains with AI assistance (mid-term accepted conditionally in March 2026).

## Open is not unrestricted

Check licences dataset by dataset. A public viewer does not grant bulk download or redistribution. OpenStreetMap carries ODbL obligations, Copernicus products have their own notices, and Czech services need their specific terms read. Resolution matters as much: a pixel is not a survey, a station is not a field sensor, and municipal statistics say nothing about a household.

**Sources:**
- D4.2 PoliRuralPlus platform Beta, §4.1 Integrated data sources and pilot data flows; §6.2 Pilot-specific use cases (Table 7) — [PDF](https://www.poliruralplus.eu/docs/421/D4.2_PoliRuralPlus_Platform_Beta.pdf)
- D4.1 PoliRuralPlus platform design, §2.1.2 Rural Attractiveness and Innovation Potential Data — [PDF](https://www.poliruralplus.eu/docs/162/D4.1_PoliRuralPlus_platform_design_v1.pdf)
- D6.3 Comprehensive Report on Funded Activities and Impact Assessment — [PDF](https://www.poliruralplus.eu/docs/437/D6.3_Comprehensive_report.pdf)
- Dataset providers: Copernicus Land Monitoring Service; LPIS, Ministry of Agriculture of the Czech Republic (eAGRI); ČÚZK (cadastre, RÚIAN, orthophotos); ČHMÚ; ČSÚ; Eurostat/GISCO; OpenStreetMap contributors (ODbL); AOPK ČR and EEA (Natura 2000)