The Swedish Address Database (ZAP) provides access to properties of Swedish addresses as well as ability to geocode your own data against Geomatic's Swedish Address Database (ZAP).
This documentation is divided into two parts:
- A full overview of all available variables.
- Some recipies for how to access the variables through the API.
In the latter section you can find examples of how to:
- Perform geocoding
- Update your own addresses with correctly spelled street and town names
- Assign a unique ID to addresses, which can be used to identify duplicates in your data
What data is available?
Here you can get an overview of all the data that is available. If you cannot find what you are looking for, then it may belong to another data universe.
Before reading on, you may find it useful to read the concepts section to understand what we mean by e.g. variables and domains.
Domains
The variables available in this universe provides information about the following domains:
| Domain | ID | Description |
|---|---|---|
| Belägenhetsadresser | acadr |
En belägenhetsadress anger var en plats finns. För bostadsadresser är det vanligen entrén eller infarten som adresseras. |
| Bostadsadresser | unadr |
Med bostadsadress avses en adress som i flerbostadshus anges med lägenhetsnummer och får småhus och radhus anges som belägenhetsadress. Syftet är att så exakt som möjligt kunna matcha mot ett hushåll. |
Variables
The following variables are available in The Swedish Address Database (ZAP). You can click on the variable name in the list below to get further information about the particular variable.
Belägenhetsadresser
| Variable | Defined On | Type | ID | Data Levels | Source | Version | Update Freq | Description |
|---|---|---|---|---|---|---|---|---|
| A-Region | Belägenhetsadresser | Category | areg |
ZAP | 17-09-2024 | Månadsvis | A-region (arbetsmarknadsregion) är ett svenskt statistiskt begrepp. Indelningen i de 70 A-regionerna gjordes på 1960-talet och regionerna utgjorde då näringsgeografiskt sammanhängande områden omfattande en eller flera arbetsmarknader. Indelningen har inte ändrats sedan dess och är sedan 1990 i arbetsmarknadssammanhang ersatt av indelningen i lokala arbetsmarknadsregioner, LA-regioner. | |
| FA-Region | Belägenhetsadresser | Category | fareg |
SCB | 01-01-2003 | Okänd | Indelningen baseras främst på pendlingsstatistik från 2003, men även på utvecklingstendenser i resmönstren. | |
| Församling | Belägenhetsadresser | Category | parish |
ZAP | 17-09-2024 | Månadsvis | Den minsta administrativa enheten i Svenska kyrkan. | |
| H-Region | Belägenhetsadresser | Category | hreg |
SCB | 01-01-2003 | Okänd | Klassificeringen utifrån kommunens folkmängd 2002-12-31. Används inte som officiell indelning idag. | |
| Husnummer (alfabetisk del) | Belägenhetsadresser | Text | houno_alpha |
ZAP | 17-09-2024 | Månadsvis | Adressens husnummerbokstav. | |
| Husnummer (numerisk del) | Belägenhetsadresser | Text | houno_num |
ZAP | 17-09-2024 | Månadsvis | Adressens husnummer utan bokstav. | |
| Husnumret | Belägenhetsadresser | Text | houno |
ZAP | 17-09-2024 | Månadsvis | ||
| Kommun | Belägenhetsadresser | Category | muni |
ZAP | 17-09-2024 | Månadsvis | Administrativ indelning för lokalt beslutsfattande. | |
| Län | Belägenhetsadresser | Category | laen |
ZAP | 17-09-2024 | Månadsvis | Administrativ indelning för regionalt beslutsfattande. | |
| Navn | Belägenhetsadresser | Text | acadr_name |
ZAP | 17-09-2024 | Månadsvis | ||
| Postnummer (3-ställig) | Belägenhetsadresser | Category | pcod3 |
ZAP | 17-09-2024 | Månadsvis | ||
| Postnummerområde | Belägenhetsadresser | Category | pcodarea |
ZAP | 17-09-2024 | Månadsvis | Sverige är i sorteringshänseende indelat i 86 postnummerområden. Ett postnummerområde består av en eller flera kommuner. Det finns undantag där en kommuns geografiska område kan tillhöra mer än ett postnummerområde. Postnummerområdets nummer utgörs av de två första siffrorna i postnumret som då återfinns i postnumren till alla postorter inom postnummerområdet. | |
| Postort | Belägenhetsadresser | Category | postort |
ZAP | 17-09-2024 | Månadsvis | ||
| Postortnamn | Belägenhetsadresser | Text | postortnam |
ZAP | 17-09-2024 | Månadsvis | Namnet på postorten. | |
| Vägnamn | Belägenhetsadresser | Text | strname |
ZAP | 17-09-2024 | Månadsvis | ||
| ZAP-ID | Belägenhetsadresser | Integer | acadr_key |
ZAP | 17-09-2024 | Månadsvis | The ZAP-Id of an access address is a unique key for the access address that is assigned by Geomatic to all access addresses in the Geomatic's address database ZAP. |
Bostadsadresser
| Variable | Defined On | Type | ID | Data Levels | Source | Version | Update Freq | Description |
|---|---|---|---|---|---|---|---|---|
| conzoom®gruppe G4 | Bostadsadresser | Category | unadr_cnzgrp_g4 |
Bostadsadresser, Belägenhetsadresser, Cell-Kluster, Postnummer, SAMS-områden | Geomatic | 01-01-2019 | Årligt | |
| conzoom®type G4 | Bostadsadresser | Category | unadr_cnztyp_g4 |
Bostadsadresser, Belägenhetsadresser, Cell-Kluster, Postnummer, SAMS-områden | Geomatic | 01-01-2019 | Årligt | |
| Lägenhetens läge på våningen | Bostadsadresser | Text | aptloc |
ZAP | 17-09-2024 | Månadsvis | ||
| Lägenhetsnummer | Bostadsadresser | Text | aptnm |
ZAP | 17-09-2024 | Månadsvis | ||
| Navn | Bostadsadresser | Text | unadr_name |
ZAP | 17-09-2024 | Månadsvis | ||
| våning | Bostadsadresser | Text | floor |
ZAP | 17-09-2024 | Månadsvis | ||
| ZAP-ID | Bostadsadresser | Integer | unadr_key |
ZAP | 17-09-2024 | Månadsvis | The ZAP-Id of a unit address is a unique key for the unit address that is assigned by Geomatic to all unit addresses in the Geomatic's address database ZAP. |
Using The API
In this section we will through examples show how the API can be used to retrieve data from this universe.
Before reading on, you may want to read the technical documentation to understand how the API is structured. There you will also find information about how authentication works in the API. Also, if you do not have an account see here for how to get one.
If the provided examples do not cover your needs, then please contact us and we will try to help out.
An important note from the technical documentation is that you in production should supply the vars argument in requests to specify exactly which variables you want returned in your response. Leaving out the vars argument will return some variables - but exactly which can change in the future.
Some of the examples below will for brevity leave out the vars argument.
Using the Variables API, you can:
- Perform geocoding
- Update your own addresses with correctly spelled street and town names
- Assign a unique ID to addresses, which can be used to identify duplicates in your data
Perform geocoding
If you have a text based address that you want to add data to, then you need to geocode the address. This can be done using Geomatic's geocoder.
For example getting the unique Id of the address Norra Klubbfors 29 in postcode 941 99 Piteå would look like this:
https://apps.conzoom.eu/api/v1/match/se/geocoder?in_str=Norra Klubbfors 29&in_pcode=94199&vars=unadr_key
See the the Matching API documentation for further details on how to do match requests as well as specification of the response.
See the Geomatic's geocoder for further details on how to use the geocoder, and what input it supports.
Update your own addresses with correctly spelled street and town names
If you have text based addresses that a person has entered there is high chance that there are spelling mistakes in some of them. Using the API you can get the correctly spelled address parts back when geocoding an address.
For example getting the correctly spelled street name and city name of the address Norra Klupfors 29 in postcode 941 99 would look like this:
https://apps.conzoom.eu/api/v1/match/se/geocoder?in_str=Norra Klupfors 29&in_pcode=94199&vars=strname,postortnam
See the the Matching API documentation for further details on how to do match requests as well as specification of the response.
See the Geomatic's geocoder for further details on how to use the geocoder, and what input it supports.
Assign a unique ID to addresses, which can be used to identify duplicates in your data
If you have text based addresses that a person has entered there is high chance that it is hard find duplicates, as addresses may have slightly different formatting or spelling. Using the API you can get a unique Id back when geocoding an address, this can then be used to easily find dublicate addresses as they will have the same Id.
For example getting the unique Id of the address Norra Klubbfors 29 in postcode 941 99 Piteå would look like this:
https://apps.conzoom.eu/api/v1/match/se/geocoder?in_str=Norra Klubbfors 29&in_pcode=94199&vars=unadr_key
See the the Matching API documentation for further details on how to do match requests as well as specification of the response.
See the Geomatic's geocoder for further details on how to use the geocoder, and what input it supports.