-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing subunit of land register in parcel search response #3384
Comments
@beat-github what is the expected result? works as defined https://api3.geo.admin.ch/services/sdiservices.html#search -> @edigonzales : proposal? |
Es müsste zusätzlich der Namen des Grundbuch(-kreises) in der Antwort stehen resp. im Suchdienst muss das Attribut "subunitoflandregister" drin sein. Bei fusionierten politischen Gemeinden ohne fusioniertes Grundbuch wird es für den Anwender unmöglich das Grundstück zu finden. Etwa so: Kann noch verwirrender werden: |
@edigonzales in which model is the attribute "subunitoflandregister" available? |
None that I'm aware of. One could use "nbident" (more or less). But the names of the subunits of land register would still be missing. +1 for a fast and pragmatic solution. |
so instead of having: Messen 168 (CH 8073 0658 3219) Parzelle we would have: Messen 168 SO0200002457 (CH 8073 0658 3219) Parzelle which doesn't bring too much IMHO. We already have the EGRID to distinguish between the 2 parcels |
No. What I meant with "fast + pragmatic" is that it can be done without a minimales Geodatenmodell including all the processes (FIG etc.). But with a simple INTERLIS model managed by V+D. |
Wishlist: Distinguish also the parcel type. Parzelle can be "Liegenschaft" or "selbständiges dauerndes Recht", e.g. Baurecht. |
https://api3.geo.admin.ch/rest/services/api/SearchServer?sr=2056&limit=15&type=locations&origins=address,parcel&searchText=messen%20168
Same parcel number and same municipality. They belong to a different subunit of land register. Without this information one cannot distinguish them.
The text was updated successfully, but these errors were encountered: