Feature #2290
closed
Cadaster API (kataster.bev.gv.at)
Description
As discussed in the meeting a connection to https://kataster.bev.gv.at/ would help a lot with the data entry.
Since there is an OpenAPI/Swagger API it should be possible to fetch the data as a external reference system. This data can then be presented on a presentation site.
We have to look deeper into the API and what information we can get from it, besides name and geometries.
branch: feature/kataster
Updated by Bernhard Koschiček-Krombholz over 1 year ago
- Description updated (diff)
Updated by Alexander Watzinger 8 months ago
- Target version changed from Wishlist to 9.2.0
Updated by Alexander Watzinger 3 months ago
- Subject changed from Include kataster.bev.gv.at to Import data from kataster.bev.gv.at
Updated by Alexander Watzinger 3 months ago
- Target version changed from 9.2.0 to 9.1.0
Updated by Alexander Watzinger 23 days ago
- Status changed from Acknowledged to Assigned
- Assignee set to Bernhard Koschiček-Krombholz
Updated by Bernhard Koschiček-Krombholz 23 days ago
- Description updated (diff)
- Status changed from Assigned to In Progress
Updated by Bernhard Koschiček-Krombholz 23 days ago
I found some issues with the kataster.bev.gv.at, which needs to be discussed:
Landing site¶
There is no nice landing site URL like with wikidata, geonames or GND. The URL, e.g. https://kataster.bev.gv.at/#/center/13.64543,47.55562/zoom/20.6/vermv/0.6 consits of a point y,y, the zoom level and some transparency. The only thing we could to, to link to the correct place is to calculate the centerpoint.
Or it is linked to its JSON representation.
Search¶
There is no fuzzy search, only an exact match search. This means one has to enter the exact Katestralgemeindenummer (kdnr), e.g. 42007, and the correct Grundstücksnummer (gnr), e.g. 222, and either there is only one match, or the sub parcel number are shown. So a valid search string looks like this: 42007-222
There is the possibility of adress search, but this gives no information about the kdnr or the gnr.
There is also no possiblity to list all Grundstücke of a Katestralgemeinde , so a system wide import of for example all Grundstücke of Hallstatt is not possible.
Questions¶
- Is there any official list of all Grundstücksnummer for a Katestralgemeinde?
- How are the students getting their information about the Grundstücksnummer? Also through kataster.bev.gv.at?
Swagger: https://kataster.bev.gv.at/at.gv.bev.kataster/api/swagger.yml or via kataster.bev.gv.at -> Anleitung/Guide -> API
tl;dr: So the implementation of a external reference system is possible, but the comfort functions like a fuzzy search and the link to a user friendly landing page will be an issue.
Updated by Alexander Watzinger 22 days ago
- Subject changed from Import data from kataster.bev.gv.at to Cadaster API (kataster.bev.gv.at)
- Description updated (diff)
Updated by Bernhard Koschiček-Krombholz 15 days ago
· Edited
- Description updated (diff)
We choose to just implement a basic version, whichout search possibility, and the landing site is the JSON view of the Katestralgemeinde or a Grundstück.
I implemented an external reference system to cover the cadastre. It will automatically detect if the number is a Katestralgemeinde or a Grundstücksnummer if one retrieves more information.
The next step is to add the SQL update script and data SQL.
Updated by Bernhard Koschiček-Krombholz 15 days ago
· Edited
There is following CSV dataset: Kataster Grundstücksverzeichnis CSV Stichtag 01.04.2023
These are lists sorted by province of all property numbers. We could think about an import strategy. One real good thing would be that we can really state the date of this cadastre data.
Otherwise, the feature is, from the technical point of view, done.
Updated by Bernhard Koschiček-Krombholz 10 days ago
- SQL: add exact match as default
- include the JSON error message, if Grundstück is not found
- Change Kataster to cadaster
Updated by Bernhard Koschiček-Krombholz 10 days ago
- Status changed from In Progress to Closed
Everything in develop branch.