All cities with a population > 1000 or seats of adm div (ca 80.000)Sources and ContributionsSources : GeoNames is aggregating over hundred different data sources. Ambassadors : GeoNames Ambassadors help in many countries. Wiki : A wiki allows to view the data and quickly fix error and add missing places. Donations and Sponsoring : Costs for running GeoNames are covered by donations and sponsoring.Enrichment:add country name

The data is from:

https://simplemaps.com/data/world-cities

We're proud to offer a simple, accurate and up-to-date database of the world's cities and towns. We've built it from the ground up using authoritative sources such as the NGIA, US Geological Survey, US Census Bureau, and NASA.

Our database is:

• Up-to-date: It was last refreshed on May 11, 2025.
• Comprehensive: Over 4 million unique cities and towns from every country in the world (about 48 thousand in basic database).
• Accurate: Cleaned and aggregated from official sources. Includes latitude and longitude coordinates.
• Simple: A single CSV file, concise field names, only one entry per city.

About this dataset

Context

The dataset tabulates the City Point town population over the last 20 plus years. It lists the population for each year, along with the year on year change in population, as well as the change in percentage terms for each year. The dataset can be utilized to understand the population change of City Point town across the last two decades. For example, using this dataset, we can identify if the population is declining or increasing. If there is a change, when the population peaked, or if it is still growing and has not reached its peak. We can also compare the trend with the overall trend of United States population over the same period of time.

Key observations

In 2023, the population of City Point town was 179, a 0% decrease year-by-year from 2022. Previously, in 2022, City Point town population was 179, a decline of 0.56% compared to a population of 180 in 2021. Over the last 20 plus years, between 2000 and 2023, population of City Point town decreased by 4. In this period, the peak population was 186 in the year 2008. The numbers suggest that the population has already reached its peak and is showing a trend of decline. Source: U.S. Census Bureau Population Estimates Program (PEP).

Content

When available, the data consists of estimates from the U.S. Census Bureau Population Estimates Program (PEP).

Data Coverage:

• From 2000 to 2023

Variables / Data Columns

• Year: This column displays the data year (Measured annually and for years 2000 to 2023)
• Population: The population for the specific year for the City Point town is shown in this column.
• Year on Year Change: This column displays the change in City Point town population for each year compared to the previous year.
• Change in Percent: This column displays the year on year change as a percentage. Please note that the sum of all percentages may not equal one due to rounding of values.

Good to know

Margin of Error

Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.

Custom data

If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.

Inspiration

Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.

Recommended for further research

This dataset is a part of the main dataset for City Point town Population by Year. You can refer the same here

Total Population of Regions, Counties, Towns, and Cities - 2010 and 2020

About this dataset

Context

The dataset tabulates the City Point town population distribution across 18 age groups. It lists the population in each age group along with the percentage population relative of the total population for City Point town. The dataset can be utilized to understand the population distribution of City Point town by age. For example, using this dataset, we can identify the largest age group in City Point town.

Key observations

The largest age group in City Point, Wisconsin was for the group of age 60 to 64 years years with a population of 29 (12.24%), according to the ACS 2019-2023 5-Year Estimates. At the same time, the smallest age group in City Point, Wisconsin was the 20 to 24 years years with a population of 1 (0.42%). Source: U.S. Census Bureau American Community Survey (ACS) 2019-2023 5-Year Estimates

Content

When available, the data consists of estimates from the U.S. Census Bureau American Community Survey (ACS) 2019-2023 5-Year Estimates

Age groups:

• Under 5 years
• 5 to 9 years
• 10 to 14 years
• 15 to 19 years
• 20 to 24 years
• 25 to 29 years
• 30 to 34 years
• 35 to 39 years
• 40 to 44 years
• 45 to 49 years
• 50 to 54 years
• 55 to 59 years
• 60 to 64 years
• 65 to 69 years
• 70 to 74 years
• 75 to 79 years
• 80 to 84 years
• 85 years and over

Variables / Data Columns

• Age Group: This column displays the age group in consideration
• Population: The population for the specific age group in the City Point town is shown in this column.
• % of Total Population: This column displays the population of each age group as a proportion of City Point town total population. Please note that the sum of all percentages may not equal one due to rounding of values.

Good to know

Margin of Error

Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.

Custom data

If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.

Inspiration

Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.

Recommended for further research

This dataset is a part of the main dataset for City Point town Population by Age. You can refer the same here

This dataset contains geographic information concerning cities and towns in the United States, Puerto Rico, and the U.S. Virgin Islands. A city or town is a place with a recorded population, usually with at least one central area that provides commercial activities. Cities are generally larger than towns; no distinction is made between cities and towns in this map layer.

How would you define the boundaries of a town or city in England and Wales in 2016? Maybe your definition would be based on its population size, geographic extent or where the industry and services are located. This was a question the ONS had to consider when creating a new statistical geography called Towns and Cities. In reality, the ability to delimit the boundaries of a city or town is difficult! Major Towns and Cities The new statistical geography, Towns and Cities has been created based on population size and the extent of the built environment. It contains 112 towns and cities in England and Wales, where the residential and/or workday population > 75,000 people at the 2011 Census. It has been constructed using the existing Built-Up Area boundary set produced by Ordnance Survey in 2011. This swipe map shows where the towns and cities and built-up areas are different. Just swipe the bar from left to right. The blue polygons are the towns and cities and the purple polygons are the built-up areas.

This dataset contains information about the demographics of all US cities and census-designated places with a population greater or equal to 65,000. This data comes from the US Census Bureau's 2015 American Community Survey. This product uses the Census Bureau Data API but is not endorsed or certified by the Census Bureau.

This data collection contains information about the population of each county, town, and city of the United States in 1850 and 1860. Specific variables include tabulations of white, black, and slave males and females, and aggregate population for each town. Foreign-born population, total population of each county, and centroid latitudes and longitudes of each county and state were also compiled. (Source: downloaded from ICPSR 7/13/10)

Please Note: This dataset is part of the historical CISER Data Archive Collection and is also available at ICPSR -- https://doi.org/10.3886/ICPSR09424.v2. We highly recommend using the ICPSR version as they made this dataset available in multiple data formats.

The 2019 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. In New England (Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island, and Vermont), the Office of Management and Budget (OMB) has defined an alternative county subdivision (generally cities and towns) based definition of Core Based Statistical Areas (CBSAs) known as New England City and Town Areas (NECTAs). NECTAs are defined using the same criteria as Metropolitan Statistical Areas and Micropolitan Statistical Areas and are identified as either metropolitan or micropolitan, based, respectively, on the presence of either an urban area of 50,000 or more population or an urban cluster of at least 10,000 and less than 50,000 population. A NECTA containing a single core urban area with a population of at least 2.5 million may be subdivided to form smaller groupings of cities and towns referred to as NECTA Divisions. The generalized boundaries in this file are based on those defined by OMB based on the 2010 Census, published in 2013, and updated in 2015, 2017, and 2018.

The urban–rural continuum classifies the global population, allocating rural populations around differently-sized cities. The classification is based on four dimensions: population distribution, population density, urban center location, and travel time to urban centers, all of which can be mapped globally and consistently and then aggregated as administrative unit statistics.Using spatial data, we matched all rural locations to their urban center of reference based on the time needed to reach these urban centers. A hierarchy of urban centers by population size (largest to smallest) is used to determine which center is the point of “reference” for a given rural location: proximity to a larger center “dominates” over a smaller one in the same travel time category. This was done for 7 urban categories and then aggregated, for presentation purposes, into “large cities” (over 1 million people), “intermediate cities” (250,000 –1 million), and “small cities and towns” (20,000–250,000).Finally, to reflect the diversity of population density across the urban–rural continuum, we distinguished between high-density rural areas with over 1,500 inhabitants per km2 and lower density areas. Unlike traditional functional area approaches, our approach does not define urban catchment areas by using thresholds, such as proportion of people commuting; instead, these emerge endogenously from our urban hierarchy and by calculating the shortest travel time.Urban-Rural Catchment Areas (URCA).tif is a raster dataset of the 30 urban–rural continuum categories for the urban–rural continuum showing the catchment areas around cities and towns of different sizes. Each rural pixel is assigned to one defined travel time category: less than one hour, one to two hours, and two to three hours travel time to one of seven urban agglomeration sizes. The agglomerations range from large cities with i) populations greater than 5 million and ii) between 1 to 5 million; intermediate cities with iii) 500,000 to 1 million and iv) 250,000 to 500,000 inhabitants; small cities with populations v) between 100,000 and 250,000 and vi) between 50,000 and 100,000; and vii) towns of between 20,000 and 50,000 people. The remaining pixels that are more than 3 hours away from any urban agglomeration of at least 20,000 people are considered as either hinterland or dispersed towns being that they are not gravitating around any urban agglomeration. The raster also allows for visualizing a simplified continuum created by grouping the seven urban agglomerations into 4 categories.Urban-Rural Catchment Areas (URCA).tif is in GeoTIFF format, band interleaved with LZW compression, suitable for use in Geographic Information Systems and statistical packages. The data type is byte, with pixel values ranging from 1 to 30. The no data value is 128. It has a spatial resolution of 30 arc seconds, which is approximately 1km at the equator. The spatial reference system (projection) is EPSG:4326 - WGS84 - Geographic Coordinate System (lat/long). The geographic extent is 83.6N - 60S / 180E - 180W. The same tif file is also available as an ESRI ArcMap MapPackage Urban-Rural Catchment Areas.mpkFurther details are in the ReadMe_data_description.docx

The 2020 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. In New England (Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island, and Vermont), the Office of Management and Budget (OMB) has defined an alternative county subdivision (generally cities and towns) based definition of Core Based Statistical Areas (CBSAs) known as New England City and Town Areas (NECTAs). NECTAs are defined using the same criteria as Metropolitan Statistical Areas and Micropolitan Statistical Areas and are identified as either metropolitan or micropolitan, based, respectively, on the presence of either an urban area of 50,000 or more population or an urban cluster of at least 10,000 and less than 50,000 population. A NECTA containing a single core urban area with a population of at least 2.5 million may be subdivided to form smaller groupings of cities and towns referred to as NECTA Divisions. The generalized boundaries in this file are based on those defined by OMB based on the 2010 Census, published in 2013, and updated in 2018.

Context

This is a dataset of the most highly populated city (if applicable) in a form easy to join with the COVID19 Global Forecasting (Week 1) dataset. You can see how to use it in this kernel

Content

There are four columns. The first two correspond to the columns from the original COVID19 Global Forecasting (Week 1) dataset. The other two is the highest population density, at city level, for the given country/state. Note that some countries are very small and in those cases the population density reflects the entire country. Since the original dataset has a few cruise ships as well, I've added them there.

Acknowledgements

Thanks a lot to Kaggle for this competition that gave me the opportunity to look closely at some data and understand this problem better.

Inspiration

Summary: I believe that the square root of the population density should relate to the logistic growth factor of the SIR model. I think the SEIR model isn't applicable due to any intervention being too late for a fast-spreading virus like this, especially in places with dense populations.

After playing with the data provided in COVID19 Global Forecasting (Week 1) (and everything else online or media) a bit, one thing becomes clear. They have nothing to do with epidemiology. They reflect sociopolitical characteristics of a country/state and, more specifically, the reactivity and attitude towards testing.

The testing method used (PCR tests) means that what we measure could potentially be a proxy for the number of people infected during the last 3 weeks, i.e the growth (with lag). It's not how many people have been infected and recovered. Antibody or serology tests would measure that, and by using them, we could go back to normality faster... but those will arrive too late. Way earlier, China will have experimentally shown that it's safe to go back to normal as soon as your number of newly infected per day is close to zero.

https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F197482%2F429e0fdd7f1ce86eba882857ac7a735e%2Fcovid-summary.png?generation=1585072438685236&alt=media" alt="">

My view, as a person living in NYC, about this virus, is that by the time governments react to media pressure, to lockdown or even test, it's too late. In dense areas, everyone susceptible has already amble opportunities to be infected. Especially for a virus with 5-14 days lag between infections and symptoms, a period during which hosts spread it all over on subway, the conditions are hopeless. Active populations have already been exposed, mostly asymptomatic and recovered. Sensitive/older populations are more self-isolated/careful in affluent societies (maybe this isn't the case in North Italy). As the virus finishes exploring the active population, it starts penetrating the more isolated ones. At this point in time, the first fatalities happen. Then testing starts. Then the media and the lockdown. Lockdown seems overly effective because it coincides with the tail of the disease spread. It helps slow down the virus exploring the long-tail of sensitive population, and we should all contribute by doing it, but it doesn't cause the end of the disease. If it did, then as soon as people were back in the streets (see China), there would be repeated outbreaks.

Smart politicians will test a lot because it will make their condition look worse. It helps them demand more resources. At the same time, they will have a low rate of fatalities due to large denominator. They can take credit for managing well a disproportionally major crisis - in contrast to people who didn't test.

We were lucky this time. We, Westerners, have woken up to the potential of a pandemic. I'm sure we will give further resources for prevention. Additionally, we will be more open-minded, helping politicians to have more direct responses. We will also require them to be more responsible in their messages and reactions.

1117 Russian cities with city name, region, geographic coordinates and 2020 population estimate.

How to use

from pathlib import Path
import requests
import pandas as pd

url = ("https://raw.githubusercontent.com/"
   "epogrebnyak/ru-cities/main/assets/towns.csv")

# save file locally
p = Path("towns.csv")
if not p.exists():
  content = requests.get(url).text
  p.write_text(content, encoding="utf-8")

# read as dataframe
df = pd.read_csv("towns.csv")
print(df.sample(5))

Files:

• towns.csv - city information
• regions.csv - list of Russian Federation regions
• alt_city_names.json - alternative city names

Сolumns (towns.csv):

Basic info:

• city - city name (several cities have alternative names marked in alt_city_names.json)
• population - city population, thousand people, Rosstat estimate as of 1.1.2020
• lat,lon - city geographic coordinates

Region:

• region_name - subnational region (oblast, republic, krai or AO)
• region_iso_code - ISO 3166 code, eg RU-VLD
• federal_district, eg Центральный

City codes:

• okato
• oktmo
• fias_id
• kladr_id

Data sources

• City list and city population collected from Rosstat publication Регионы России. Основные социально-экономические показатели городов and parsed from publication Microsoft Word files.
• City list corresponds to this Wikipedia article.
• Alternative dataset is wiki-based Dadata city dataset (no population data).

Comments

City groups

• Ханты-Мансийский and Ямало-Ненецкий autonomous regions excluded to avoid duplication as parts of Тюменская область.

• Several notable towns are classified as administrative part of larger cities (Сестрорецк is a municpality at Saint-Petersburg, Щербинка part of Moscow). They are not and not reported in this dataset.

By individual city

• Белоозерский not found in Rosstat publication, but should be considered a city as of 1.1.2020

Alternative city names

• We suppressed letter "ё" city columns in towns.csv - we have Орел, but not Орёл. This affected:

  • Белоозёрский
  • Королёв
  • Ликино-Дулёво
  • Озёры
  • Щёлково
  • Орёл

• Дмитриев and Дмитриев-Льговский are the same city.

assets/alt_city_names.json contains these names.

Tests

poetry install
poetry run python -m pytest

How to replicate dataset

1. Base dataset

Run:

• download data stro rar/get.sh
• convert Саратовская область.doc to docx
• run make.py

Creates:

• _towns.csv
• assets/regions.csv

2. API calls

Note: do not attempt if you do not have to - this runs a while and loads third-party API access.

You have the resulting files in repo, so probably does not need to these scripts.

Run:

• cd geocoding
• run coord_dadata.py (needs token)
• run coord_osm.py

Creates:

• coord_dadata.csv
• coord_osm.csv

3. Merge data

Run:

• run merge.py

Creates:

• assets/towns.csv

This data layer produced by the National Center for Education Statistics’ (NCES) Education Demographic and Geographic Estimates (EDGE) program provides a geographic locale framework that classifies all U.S. territory into twelve categories ranging from Large Cities to Remote Rural areas. NCES uses this framework to describe the type of geographic area where schools and school districts are located. The criteria for these classifications are defined by NCES and rely on standard geographic areas developed and maintained by the U.S. Census Bureau. The NCES Locale boundaries are based on geographic areas represented in Census TIGER/Line. For more information about the NCES locale framework, and to download the data, see: https://nces.ed.gov/programs/edge/Geographic/LocaleBoundaries. The classifications include:City - Large (11): Territory inside an Urban Area with a population of 50,000 or more and inside a Principal City with population of 250,000 or more.City - Midsize (12): Territory inside an Urban Area with a population of 50,000 or more and inside a Principal City with population less than 250,000 and greater than or equal to 100,000.City - Small (13): Territory inside an Urban Area with a population of 50,000 or more and inside a Principal City with population less than 100,000.Suburb – Large (21): Territory outside a Principal City and inside an Urban Area with population of 250,000 or more.Suburb - Midsize (22): Territory outside a Principal City and inside an Urban Area with population less than 250,000 and greater than or equal to 100,000.Suburb - Small (23): Territory outside a Principal City and inside an Urban Area with population less than 100,000. Town - Fringe (31): Territory inside an Urban Area with a population less than 50,000 that is less than or equal to 10 miles from an Urban Area with a population of 50,000 or more.Town - Distant (32): Territory inside an Urban Area with a population less than 50,000 that is more than 10 miles and less than or equal to 35 miles from an Urban Area with a population of 50,000 or more.Town - Remote (33): Territory inside an Urban Area with a population less than 50,000 that is more than 35 miles of an Urban Area with a population of 50,000 or more.Rural - Fringe (41): Census-defined rural territory that is less than or equal to 5 miles from an Urban Area of 50,000 or more, as well as rural territory that is less than or equal to 2.5 miles from an Urban Area with a population less than 50,000.Rural - Distant (42): Census-defined rural territory that is more than 5 miles but less than or equal to 25 miles from an Urban Area with a population of 50,000 or more, as well as rural territory that is more than 2.5 miles but less than or equal to 10 miles from an Urban Area with a population less than 50,000.Rural - Remote (43): Census-defined rural territory that is more than 25 miles from an Urban Area with a population of 50,000 or more and is also more than 10 miles from an Urban Area with a population less than 50,000.All information contained in this file is in the public domain. Data users are advised to review NCES program documentation and feature class metadata to understand the limitations and appropriate use of these data.

Population and household characteristics by built-up area (BUA) size classification and individual BUAs, England (excluding London) and Wales, Census 2021. Data are available at a country, BUA size classification and individual BUA level.

This dataset is part of the Geographical repository maintained by Opendatasoft. This dataset contains data for places and equivalent entities in United States of America.This layer both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. Processors and tools are using this data. Enhancements Add ISO 3166-3 codes. Simplify geometries to provide better performance across the services. Add administrative hierarchy.

A dataset listing Washington cities by population for 2024.

This data set includes cities in the United States, Puerto Rico and the U.S. Virgin Islands. These cities were collected from the 1970 National Atlas of the United States. Where applicable, U.S. Census Bureau codes for named populated places were associated with each name to allow additional information to be attached. The Geographic Names Information System (GNIS) was also used as a source for additional information. This is a revised version of the December, 2003, data set.

This layer is sourced from maps.bts.dot.gov.

Per RCW 47.04.010, "population center" includes incorporated cities and towns, including their urban growth areas, and census-designated places in Washington State. The WSDOT Population Center dataset combines the WSDOT Incorporated City Limits dataset (May 2021) with the Office of Financial Management’s Census Designated Places (2020 Census) Dataset. Identification of Population Centers enables WSDOT to address the Complete Streets requirement under RCW 47.04.035 and to otherwise identify locations prioritized in the 2021 WSDOT Active Transportation Plan (ATP). WSDOT may also recognize other developed areas as exhibiting land use patterns consistent with the definition of population center, that are not currently captured by this data layer.This data layer assists WSDOT in prioritizing active transportation improvements in areas where people congregate and access destinations, and where travel distances between destinations align with typical distances travelled by users of pedestrian and bicycle modes. These areas are a priority because they serve the broadest range of users and potential users of the transportation system, including the very young, very old, and people with disabilities. In this dataset, each Population Center includes information for the “Place Name”, the “Place Type” (city/town, Urban Growth Area outside of city limits, or Census Designated Place), and whether or not the Population Center intersects a State Route (“yes” indicates that there is an intersection with a State Route, “no” indicates that there is no intersection.). The dataset will be updated as needed. Please direct questions about the Population Centers dataset to: Grace.Young@wsdot.wa.gov.