Reasons for population changes in statistical regions, counties, cities, parishes (within borders at the beginning of 2024), comparing the situation on two dates in neighbourhoods and densely populated areas (experimental statistics)

Open data API in a single place

Provided by Centrālā statistikas pārvalde

Get early access to Reasons for population changes in statistical regions, counties, cities, parishes (within borders at the beginning of 2024), comparing the situation on two dates in neighbourhoods and densely populated areas (experimental statistics) API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2018.02.05 00:00
Created
2018.02.05
Available languages
English
Keywords
administratīvā teritorija, bat, iedzīvotāju skaits, migrācija, mirstība, apkaime, reģions, novads, blīvi apdzīvota teritorija, eksperimentālā statistika, dzimstība, pagasts, pilsēta
Quality scoring

Dataset description

The table provides information on the population living in the area in the given starting year (e.g. 2000, at the time of the census) and their status in the given end year (early 2017). For example: * if the person lived in Riga on 31 March 2000 and the place of residence was Riga on 1.1.2017, then reside in the same territory; * if the person lived in the vicinity of Mežaparks in Riga on 31 March 2000 and the place of residence was the Torņakalns district in Riga on 1.1.2017, then moved to another territory in Latvia. [Structural metadata](https://data.gov.lv/dati/dataset/csp-strukturalie-metadati). New data sources and methods shall be used for the calculation of experimental statistics, seeking to broaden the range or level of detail of statistics according to the needs of the users. It should be noted that experimental statistical methods are not constant, approbated and internationally harmonised and may be changed to improve data quality. CSB publishes experimental statistics to receive user feedback, assess the analytical potential of data, relevance to reality and user needs. The CSB considers that the experimental data series can also be useful for users and the opinion of the users of statistics is the basis for a decision on the inclusion of these statistics in the Official Statistical Programme. By publishing experimental statistics, the CSB provides data users with new sources of information for decision making. The calculation of the population number in all specified periods has been carried out using geospatial data – the coordinates of the address points and the boundaries of the administrative territory according to the data of the State Land Service at the time indicated. This reduced population fluctuations in the relevant territorial unit or administrative area as a result of changes in the boundaries of territorial units. Residents whose last reason for updating the information of the place of residence is the cancellation of the registration of the place of residence is included in the number of inhabitants of the administrative territory where the place of residence of this person was previously declared or registered. By territorial units and neighbourhoods, the place of residence of these persons is reported as unknown. More on the assessment of population and key demographic indicators in experimental statistics [descriptive metadata](https://stat.gov.lv/lv/metadati/8113-iedzivotaju-skaits-un-galvenie-demografiskie-raditaji-eksperimentala-statistika).
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks