Question about mapping GWR codes in the API

19 views
Skip to first unread message

Silvan Bernal

unread,
Jun 19, 2025, 3:34:00 AMJun 19
to GeoAdminCh API
In the GeoAdmin building API (layer ch.bfs.gebaeude_wohnungs_register), the following fields, among others, are delivered in the JSON:

gwaerzh1: 7430

genh1: 7520

gwaersceh1: 859

These are displayed on the web interface as follows

7430 → Boiler (gen.) for a building

7520 → Gas

859 → Other

Is there an official mapping table (code → plain text) that is publicly available or can be accessed directly via the API?

GeoAdminCh API

unread,
Jun 19, 2025, 8:13:47 AMJun 19
to GeoAdminCh API
Hi SilvanThe mapping in code form is unfortunately in one of our private repositories we use to populate the database. However, the orginal source for these mappings can be found here:https://www.housing-stat.ch/catalog/de/4.2/finalSearch for example for "7430" and you are going to find one of your examples. It's not ideal because there are different versions and it's not in a machine-readable form but that is all we can provide for the moment.Whenever you have detail questions on a layer, it is worth following the links we provide per layer. In this case, we traced back the original source via this path:
1. Click the (i) icon next to the layer "RBD: building status" (ch.bfs.gebaeude_wohnungs_register, "GWR: Gebäudestatus" in German)
2. Follow "link to description": https://www.bfs.admin.ch/bfs/de/home/register/gebaeude-wohnungsregister.html
3. Then follow the links on these detail pages. Here there is a link at the bottom guiding you to https://www.gwr.admin.ch/ which in turn advertises the https://www.housing-stat.ch/catalog/de/4.2/revised.Alternatively, geocat shows similar metadata on layers:
https://www.geocat.ch/geonetwork/srv/eng/catalog.search#/metadata/56553efe-4a2c-449d-93ba-cf7edd518d56Note that we are working on merging these different sources of metadata into a single portal "SWISSGEO", see http://www.geoinformation.ch/de/swissgeo-geoplattform.Hope that helps for next time.
Reply all
Reply to author
Forward
0 new messages