> For the complete documentation index, see [llms.txt](https://bellingcat.gitbook.io/toolkit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bellingcat.gitbook.io/toolkit/more/all-tools/wikimapia.md). # Wikimapia Wikimapia is a long-running collaborative mapping project that remains partially accessible, providing open source researchers with a unique database of historical, user-generated content. ## URL ## Description Wikimapia is a collaborative mapping project that combines an interactive map with a wiki system. While it aims to describe every location on Earth, researchers must understand that despite ongoing activity, the data should not be treated as a current or authoritative map without verification. Firstly, many of the site's secondary features - such as the official Wikimapia Statistics pages - are still reachable but no longer functional. The interface loads, but the underlying data have not updated for years, leaving the charts empty. Archived versions (for example, [this 2023 Wayback capture showing historical user counts](https://web.archive.org/web/20231115072150/http://wikimapia.org/stats/action_stats/?fstat=6\&period=3\&year=2009\&month=6)) confirm that these pages once displayed detailed metrics such as total users and added places, but the feature itself has long since gone dormant. Secondly, the Countries Watchlist feed confirms ongoing editing activity from multiple users daily. Archived snapshots of the platform's place counter show steady growth - from approximately [30.6 million places in February 2021](http://archive.today/2021.02.24-100603/https://wikimapia.org/%23lang=en\&lat=52.366700\&lon=-1.250000\&z=12\&m=w), [31.4 million in August 2022](http://archive.today/2022.08.22-110644/http://wikimapia.org/%23lang=en\&lat=52.366700\&lon=4.900000\&z=12\&m=w), [31.6 million in March 2023](http://archive.today/2023.03.07-171023/https://wikimapia.org/%23lang=en\&lat=52.366700\&lon=4.900000\&z=12\&m=w), [32 million in March 2024](http://archive.today/2024.03.12-150845/http://wikimapia.org/%23lang=en\&lat=50.450000\&lon=30.523300\&z=12\&m=w), [32.5 million in July 2025](http://archive.today/2025.07.02-143127/https://wikimapia.org/%23lang=en\&lat=38.254200\&lon=-85.759400\&z=12\&m=w), to over 32.9 million by June 2026 - suggesting roughly 400,000–500,000 new places are added per year. Ongoing activity can be observed via the live Countries Watchlist, accessible under the Tools menu on the main map. Despite its age, Wikimapia's historical dataset can be a valuable source for open-source researchers in specific contexts: * **Historical Geolocation:** The platform is useful for investigating past events. For instance, "user tags" from 2014 - crowdsourced labels that people created by drawing a shape around a location and adding a name or description - can help identify buildings or military positions in Ukraine that have since been altered or destroyed. * **Regional Focus:** The data on Wikimapia is most comprehensive in regions where it had a large user base, particularly in Russia, Ukraine, and other Eastern European countries. For research focused on this area during Wikimapia's [peak activity period (approximately 2006–2012)](https://www.researchgate.net/figure/Google-searches-for-Wikimapia-and-OpenStreetMap-on-a-monthly-basis-source-Google-Trends_fig4_324675292), it may contain labels and details not found on other maps from that period. It is not the most comprehensive data source available for any region today, but it can be a unique source for historical context. The screenshot below with the view of [Donetsk International Airport](https://www.theatlantic.com/photo/2015/02/a-year-of-war-completely-destroyed-the-donetsk-airport/386204/) demonstrates its value as a historical record. The main airport area is labeled "Ruined" on Wikimapia, a title updated by users following its destruction in 2014. The map is covered in detailed, user-added polygons that pinpoint specific locations, including historical events like the nearby "Il-76 shoot-down."

A screenshot of the Wikimapia interface displays the map of Donetsk International Airport in Ukraine. The tag "Ruined Donetsk International Airport" is an example of how the platform was used by Wikimapia users to try to document the real-world impact of conflict.

The log shows user activity from the year 2014, specifically highlighting two key changes in response to the battle for the airport. First, at Revision 56, a user adds a protection status of "(destroyed)"; this is immediately followed by Revision 58, where the same user performs an "Edit title \[en]", adding the word "Ruined" to the official name. This sequence demonstrates how Wikimapia was updated in near real-time by its users to try to document the consequences of a major conflict.

This screenshot captures the edit history for the Donetsk International Airport entry on Wikimapia, providing a clear example of user efforts to use it as a historical ledger.

### Features: * **Search & Categories:** Search for locations by name or filter the map by dozens of pre-set categories (e.g., military, hospital, factory). * **Multiple Map Layers:** Switch between various base map providers, including [Google Maps](https://bellingcat.gitbook.io/toolkit/more/all-tools/google-maps), [Bing Maps](https://bellingcat.gitbook.io/toolkit/more/all-tools/bing-maps), and OpenStreetMap. * **Measurement Tool:** Includes a tool for measuring distances between points on the map. * **Measure distance:** measure distance between points in feet and metres. * **Multilingual Interface:** The user interface is available in multiple languages.

This screenshot illustrates two of Wikimapia's features working together. The main map view shows the result of a category filter, displaying only locations tagged as a "hospital" in the Berlin area. By selecting one of these hospitals, the information panel on the left opens, revealing details about that specific place, including the "last modified" date located at the very bottom of the panel.

### Use Case examples for Open Source Researchers 1. **Corroborating Old Evidence:** Use the map's historical annotations to find supplementary information on claims or events mentioned in old news reports, videos, or documents from the 2007-2015 period. 2. **Discovering Informal Place Names:** Identify local, unofficial, or historical names for locations that do not appear on official maps, which can be crucial for keyword searching in local languages. 3. **Analyzing Historical Site Layouts:** Examine the detailed, user-drawn layouts of industrial sites, military bases, or critical infrastructure as they existed before being altered, expanded, or destroyed. 4. **Cultural and Historical Context:** Gain insights into the significance of local landmarks or historical sites based on what users were documenting and describing during the platform's most active years. ## Similar Tools Wikimapia's strength lies in its historical, user-generated geographic annotations, particularly for Eastern Europe in the 2007–2015 period. The tools below either overlap with or complement Wikimapia's functionality and may be worth consulting depending on your research needs. | Tool | Description | Similarities | Differences | | ----------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | [OpenStreetMap](https://bellingcat.gitbook.io/toolkit/more/all-tools/openstreetmap-search-tool) | A live, collaborative global map with structured geospatial data. | Both are crowdsourced mapping projects covering locations worldwide. | OSM is actively maintained with current data; Wikimapia is a largely static historical archive. | | [Mapillary](https://bellingcat.gitbook.io/toolkit/more/all-tools/mapillary) | Crowdsourced street-level imagery platform. | Both rely on user-contributed geographic content. | Mapillary focuses on photos and street-level imagery; Wikimapia focuses on place labels and polygon annotations | | [Google Maps](https://bellingcat.gitbook.io/toolkit/more/all-tools/google-maps) | Commercial mapping platform with street view, satellite imagery, and place data. | Both allow searching for and exploring specific locations on an interactive map. | Google Maps reflects current conditions; Wikimapia preserves informal, user-generated historical labels. | | [KartaView](https://bellingcat.gitbook.io/toolkit/more/all-tools/kartaview) | Open source street-level imagery collection. | Both are community-driven platforms for documenting real-world locations. | KartaView provides photographic documentation; Wikimapia provides textual and categorical place annotations. | #### Who Should Use Which Tool? * **Use Wikimapia if**: You are an open source researcher needing historical context for a specific time period (pre-2016) in specific regions (e.g., Eastern Europe), especially for finding informally labeled sites. * **Use OpenStreetMap if:** You need more current crowdsourced, and reusable map data for any other purpose, including analysis, visualization, navigation, or as a base layer for your own research. OSM is the standard for up-to-date, open-source geospatial information. * **Use Mapillary if:** You need street-level photographic documentation of a location, especially for geolocation tasks or verifying the appearance of a specific place at a particular point in time. * **Use Google Maps if:** You need a reliable, up-to-date reference map with broad commercial coverage, satellite imagery, and street view for verifying or contextualizing current locations — particularly in regions where OSM coverage may be thinner. * **Use KartaView if:** You are looking for an open source alternative to Mapillary for street-level imagery, particularly in regions or on routes where Mapillary has limited coverage. ## Cost * [x] Free * [ ] Partially Free * [ ] Paid ## Level of difficulty
1
## Requirements * **Web**: any modern web browser. * **Account:** requires email address. ## Limitations Researchers must be aware of Wikimapia's significant limitations. The data should never be used as a standalone source and must be treated with extreme caution. * **Data Accuracy**: Wikimapia’s content is user-generated, leading to potential inaccuracies. In addition, there is no standardized validation process for user-submitted data, which means errors or assumptions may persist without correction. * **Outdated information:** This is the most critical limitation. The overwhelming majority of the data may not reflect the current reality of a location and must be verified using contemporary sources. * **Inconsistent Coverage:** Data density varies dramatically. While areas like Eastern Europe are heavily detailed with historical data, many other regions have sparse or non-existent information. * **API Rate Limiting**: There might be limitations on the number of API requests that can be made in a certain timeframe, impacting extensive data retrieval tasks. The actual rate limits are not clearly documented at this time. See the [Wikimapia API documentation](https://wikimapia.org/api/) for more detail. ## Ethical Considerations When using Wikimapia, ethical considerations include: * **Responsibility for Verification:** Given that the platform contains unverified, outdated, and potentially false information, researchers have an ethical responsibility to rigorously verify any claims before using them in publications or reports. Publishing unverified data from Wikimapia risks spreading misinformation. * **Handling Sensitive and Private Information:** The map's archive may contain labels for private homes or other sensitive locations added without consent. Researchers must be cautious not to amplify or republish information that could infringe on the privacy and security of individuals. * **Contextual use and attribution:** When Wikimapia data is referenced in analysis or reporting, researchers should clearly indicate that the information originates from a crowdsourced platform and does not represent an official or authoritative mapping source. This is also a [licensing requirement](https://wikimapia.org/terms_reference.html), not just good practice - Wikimapia Data is released under Creative Commons Attribution-ShareAlike, and public reuse requires linking back to the original data URL and crediting Wikimapia.org. Presenting such data without context or attribution may mislead audiences even when individual claims have been verified. ## Guide The following resources are recommended for understanding how Wikimapia has been used in an open source research context. Note that most of these guides are several years old and should be viewed as examples of methodology rather than tutorials for a modern tool. * Open Source Research Case Studies (Highly Recommended): * Seitz, J. (2015) [*Automating Photo Retrieval for Geolocating - Part 2:Wikimapia*](https://www.bellingcat.com/resources/2015/05/13/automating-photo-retrieval-for-geolocating-part-2-wikimapia/), Bellingcat. This article is an excellent example of how the tool's data was used in geolocating workflows at its peak. * Sheldon, M. (2022) [*Meet the Irregular Troops Backing up Russia’s Army in the Kharkiv Region*, Bellingcat](https://www.bellingcat.com/news/2022/06/17/meet-the-irregular-troops-backing-up-russias-army-in-the-donbas). This article shows the tool being used to identify the location of a Russian military base, demonstrating its value in conflict analysis. * Historical Guides: * [*Wikimapia Quick Start Tutorial.MP4*](https://www.youtube.com/watch?v=MbN36OxmX9A) (2014). This official video shows the basic functionality of the Wikimapia interface as it was during its most active period. * [*Wikimapia Forum*](http://wikimapia.org/forum/index.php). The official forum, while having very low activity, is a place to see historical discussions about the tool. * Developer and User Resources (Advanced/Historical): * Disclaimer: The Wikimapia API is not actively maintained and may be unreliable. These resources are for archival purposes. * [Official Wiki](https://wikimapia.org/docs/Main_Page) - Wikimapia's own documentation site, covering editing tools, categories, and community guidelines. Last modified July 2015, so treat it the same way as the rest of Wikimapia's content: a snapshot of how the platform worked during its active period, not current documentation. * [Getting Started with wikimapia\_api (Python)](https://wikimapia-api-py.readthedocs.io/en/latest/). * [GIS StackExchange](https://gis.stackexchange.com/questions/tagged/wikimapia): (Archive of technical questions). ## Tool provider Wikimapia Ltd. Wikimapia was created by the Russian software company Wikimapia Ltd., founded in 2006 by Alexander Koryakin and Eugen Saveliev. ## Advertising Trackers * [ ] This tool has not been checked for advertising trackers yet. * [x] This tool uses tracking cookies. Use with caution. * [ ] This tool does not appear to use tracking cookies. | Page maintainer | | --------------- | | tsvetelina | | | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://bellingcat.gitbook.io/toolkit/more/all-tools/wikimapia.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.