はじめにQuickOSMとは、OpenStreetMapのデータを追加するためのQGISプラグインです。QuickOSMを使えば、必要な地域の必要なデータだけを素早く取得できるため、大きなファイルをダウンロードして処理する手間が省けます。この記事では、QuickOSMのインストール方法と、QGISにデータを追加する手順をご紹介します。OpenStreetMapについて詳しく知りたい方は、以下の記事

We’re working with OpenStreetmap for Day 15 of the #30daymapchallenge. We’ll learn how to use the QuickOSM plugin for #QGIS to download data and then style t...

I want to figure out (qualitatively) how much area of my city has a bus stop within 400 m walking distance. My approach so far is to load all bus stops and draw circles with radius = 400 m around them. Then I can see how much of the city is covered in circles. I use QGIS, OpenStreetMap and the QuickOSM plugin. I seem to get something wrong with the measurements / projections though. Starting from knowing nothing, I figured out the following: * I can easily get all the bus stops as a layer with QuickOSM. * I can then modify the symbol layer. I tried 800 meters in scale (as the input seems to be diameter) but surprisingly the diameter is then not 800 meters - well, it is, but only if I change the measure tool to cartesian. * But it should not be Cartesian, it should be the default, ellipsoid, as that is what is used to measure "real life" distances - as in, if I leave my house and walk 100 meters, the same distance will show up as 100 meters in QGIS if I measure based on the ellipsoid. * I figured out that the bus stops layer uses EPSG 4326 WGS 84 as source while OSM Standard, loaded via the Quick Map Services, uses EPSG 3857 WGS 84 as source. Now if I understood it correctly, one is position on the globe and one is position on my map. It makes sense to me that meters have different meanings then, but still the bus stops end up at their actual positions just fine. I just can't draw circles around them. I tried re-projecting the bus stop layer to EPSG 3857 but that did not help at all (and probably does not make sense). I also noted that for OSM, "meters in scale" and "map units" seem to be identical. I read something about EPSG:3857 meters not being real meters but I do not know what to do with that. Is that the issue? How do I correct for the "fake" meters? How can I address my original problem and what is the explanation? It especially makes me wonder why measuring in Cartesian matches exactly what I entered in the "meters in scale" box. Meta information: QGIS 3.24, QuickOSM 2.0.1, my location is Germany.

First of all, thank you for developing and maintaining this wonderful plugin. It has been extremely helpful for my spatial data workflow. I am currently using QuickOSM to extract road and spatial data for map figures to be included in an Environmental Impact Assessment (EIA) report. I would like to ensure full compliance with the ODbL license regarding copyright attribution. Could you please clarify or recommend the standard format for citing the data in printed or embedded map figures?

I want to figure out (qualitatively) how much area of my city has a bus stop within 400 m walking distance. My approach so far is to load all bus stops and draw circles with radius = 400 m around them. Then I can see how much of the city is covered in circles. I use QGIS, OpenStreetMap and the QuickOSM plugin. I seem to get something wrong with the measurements / projections though. Starting from knowing nothing, I figured out the following: * I can easily get all the bus stops as a layer with QuickOSM. * I can then modify the symbol layer. I tried 800 meters in scale (as the input seems to be diameter) but surprisingly the diameter is then not 800 meters - well, it is, but only if I change the measure tool to cartesian. * But it should not be Cartesian, it should be the default, ellipsoid, as that is what is used to measure "real life" distances - as in, if I leave my house and walk 100 meters, the same distance will show up as 100 meters in QGIS if I measure based on the ellipsoid. * I figured out that the bus stops layer uses EPSG 4326 WGS 84 as source while OSM Standard, loaded via the Quick Map Services, uses EPSG 3857 WGS 84 as source. Now if I understood it correctly, one is position on the globe and one is position on my map. It makes sense to me that meters have different meanings then, but still the bus stops end up at their actual positions just fine. I just can't draw circles around them. I tried re-projecting the bus stop layer to EPSG 3857 but that did not help at all (and probably does not make sense). I also noted that for OSM, "meters in scale" and "map units" seem to be identical. I read something about EPSG 3857 meters not being real meters but I do not know what to do with that. Is that the issue? How do I correct for the "fake" meters? How can I address my original problem and what is the explanation? It especially makes me wonder why measuring in Cartesian matches exactly what I entered in the "meters in scale" box. Meta information: QGIS 3.24, QuickOSM 2.0.1, my location is Germany.

15/01/2026-21/01/2026 1] How to Make a Lighthouse Map Using QGIS and QuickOSM | by Mashford Mahute | map data © by [OpenStreetMap Contributors. ## About us * Hello dear friends of the Italian language. This is probably our last issue in Italian. Last week we didn’t publish issue #808 because we only had one proofreader.This week we are publishing even though we only have one proofreader.Our quality standards stipulate that at least two native speakers must proofread the automatic translations. As we were unable to do this last week and again this week, we assume that you would like to read one of the remaining languages from issue #810 onwards. We would like to thank you for your loyalty over the years and especially our many colleagues in Italy who have been offering this service for many years. ## Mapping campaigns * Koreller reported that, on 7 January, Mapbox updated over 10 million square kilometres of aerial imagery across the world with a resolution of 30 cm. * After a fatal train crash in Spain, which occurred by the Adamuz crossover, OSM mappers began mapping the surrounding area in solidarity to improve map quality. * Saarpfalz-Touristik has launched ► an organised OpenStreetMap editing initiative aimed at updating hiking trail data in the Bliesgau region of Germany. ## Community * Anne-Karoline Distel presented her latest project on YouTube, in which she transferred historical data from the 1655 ‘Down Survey’ map for County Kilkenny, Ireland into an interactive map on uMap. She explained the challenges of working with the old manuscripts, such as outdated spellings, copying errors by the cartographers of the time, and matching to modern geographical data on Wikidata. She also showed in detail how different layers of information, including townlands, castles, churches, bridges and historic mills, can be visualised using technical filters and formatting. * Foxy has noticed that Google publishes statistics on website metrics collected by Google Chrome. Using this data, it can be inferred that more than half of users who access OSM via Chrome do so on mobile devices. * Ivan Branco marked six months of _MensileOSM_ , an Italian newsletter dedicated to the OpenStreetMap community, by presenting it live in Trento at OSMit 2026 and in Biella at the OSMers Biella, Vercelli, and Canavese ► meeting. * While waiting for a subway train, Mittens_unofficial used ► the Vespucci mobile app to map the surveillance cameras at subway stations in the Nuremberg–Fürth area. * PizzaTreeIsland has emphasised that `access` tags indicate whether use is permitted, whereas the `wheelchair` tag describes whether access is physically possible, regardless of permission. This distinction is reflected in the iD editor’s input mask, where ‘allowed access’ and ‘wheelchair access’ appear in entirely separate sections. * After three and a half years of drafting and polling to find the tagging concept the community prefers, Penegal has made a request for comments on a tagging scheme for advisory access restriction ideograms on destination signs. This proposal aims to tag advisory restriction ideograms, which are displayed on destination signs in many countries. Comments can be made on the proposal’s talk page or in the OSM Community forum topic. ## Local chapter news * OpenStreetMap US has announced that it is seeking mapping enthusiasts to fill two vacant seats on its Board of Directors. The nomination period will open on Monday 26 January and close on Saturday 8 February. ## Events * Recordings of the State of the Map Europe 2025 sessions are being uploaded and are available on its YouTube channel. The details can be found in the event’s schedule. ## Maps * 1] Mashford Mahute has [ published a little routine to create a map of lighthouses using QGIS and the QuickOSM plugin and offered Japan’s lighthouses as an example. * Hidde discovered Lights of Sea Online (we reported earlier), a web map that visualises around 65,000 blinking lighthouses, light buoys, and other navigational beacons, taken from OpenStreetMap data. * The European Environmental Agency published a map of ports belonging to the core network and not, with LNG bunkering facilities based on OpenStreetMap. But the download area does not have the option to offer OSM data. The product is part of the Sustainability of Europe’s mobility systems EEA programme. * Christoph Hormann has released his Musaicum satellite image mosaics as a ready-to-use tileset for interactive web maps. * Christoph Hormann published an article explaining how features located outside a map tile can affect its rendering, a factor that can lead to inconsistencies in map visualisation. ## Software * Eugene reported that OsmAnd’s topography plugin now includes an avalanche colour scheme for the Slope layer, which colours terrain based on its steepness, to highlight potential avalanche risks and provide a more intuitive visualisation for safer backcountry navigation. * Eugene introduced OsmAnd’s Snowmobile map style, aimed at visualising `route=snowmobile` trails. ## Programming * Richard Hemmer, from Geschichten aus der Geschichte , has published a post on his own blog, in which he explains his design and developing process behind the postcard application we reported earlier. * Michael Reichert reported that Geofabrik has decided to port Nik4, a tool for rendering single map images for a given location, to C++ to address its unmaintained dependency on Mapnik’s Python bindings. The code is published on Codeberg. ## Releases * Alexis Lecanu has released Baba version 1.20.0, a mobile app for contributing to the Panoramax project. ## Did you know that … * … you can see the top OSM users over the past day, week, or month by accessing the statistics page? ## Other “geo” things * The international OCEANIDS Project noted that a lot of coastal settlements are shifting to inland areas as climatic risks increase. It can be a challenge to global collaborative mapping projects, including OSM. There is a web map (OCEANIDS Platform) that shows related geodata and geoservices (still in the initial stages of development), which is provided by the EU, but unfortunately the option ‘OpenStreetMap’ in the layers panel is written incorrectly. * The OGC Artificial Intelligence-Discrete Global Grid System (AI-DGGS) has offered a workshop on a pilot, which uses a recently published DGGS API standard, providing a natively digital alternative to traditional coordinate systems. * In response to escalating geopolitical tensions, OpenCage has revised its planned geotrivia topics, shifting the focus to Greenland. * There is a proposal to include ‘location collected’ as a property in Wikidata records and you can cast your vote. It is intended to record the geographic location where a specimen or sample was collected in the field. * Lena Mattson, from the US Library of Congress, blogged about the ups and downs of daily life for a fire insurance map company’s surveyors, citing experiences that include being denied entry, locked out on high-rise rooftops, attacked by dogs, shot at by smugglers, and even detained by military police on suspicion of espionage. * Mary Wadland, of _The Zebra_ , reported that Gladys West, renowned for her pioneering work in mathematical modelling of the Earth’s shape and the development of satellite geodesy models, later integrated into GPS, died on Saturday evening 17 January. * Robert Schwandl regularly publishes some urban rail networks on the Urbanrail.net potal. You can learn more about this service and send photographs to the project. ## Upcoming Events Country | Where | Venue | What | When ---|---|---|---|--- | | | UN Mappers: OpenStreetMap Beginner Training using JOSM | 2026-01-23 | | | OSMF Engineering Working Group meeting | 2026-01-23 | Bengaluru | RT Nagar | OSM Bengaluru Mapping Party | 2026-01-24 | Nashik | Nashik Engineering Cluster, MIDC Ambad | State of the Map India 2026 | 2026-01-24 | | | Missing Maps : Mapathon en ligne – CartONG fr] [ | 2026-01-26 | Hannover | Kuriosum | OSM-Stammtisch Hannover | 2026-01-26 | Saint-Étienne | Zoomacom | Rencontre Saint-Étienne et sud Loire | 2026-01-26 | | Online | Mappy Hour OSM España | 2026-01-27 | Kiel | Mango’s, Kiel | Kieler Mapper*innentreffen | 2026-01-27 | Berlin | Online | OSM-Verkehrswende #71 | 2026-01-27 | Düsseldorf | Online bei https://meet.jit.si/OSM-DUS-2026 | Düsseldorfer OpenStreetMap-Treffen (online) | 2026-01-28 | Amsterdam | TomTom HQ Amsterdam | 2026 Kickoff Meetup – Mapping, Fireside Chats, Show & Tell, and More! | 2026-01-29 | | | Mapping USA 2026 | 2026-01-30 – 2026-01-31 | Gent | Sporewegel 1 | OpenStreetMap meetup in Gent | 2026-01-30 | Aosta / Aoste | Museo archeologico regionale | Compleanno di Wikipedia e mapping party ad Aosta @ Fiera di Sant’Orso | 2026-01-31 | Mumbai | Churchgate (approximate location) | OSM Mumbai Mapping Party No.6 (Mumbai City) | 2026-01-31 | नई दिल्ली | Jitsi Meet (online) | OSM India – Monthly Online Mapathon | 2026-02-01 | | EPN d’Arlon, rue de Diekirch 37, Arlon | EPN d’Arlon – OpenStreetMap – Découverte | 2026-02-03 | Essen | Verkehrs- und Umweltzentrum | Essen OSM-Treffen | 2026-02-03 | | | Missing Maps London: (Online) Mapathon eng] [ | 2026-02-03 | | | iD Community Chat | 2026-02-04 | Stuttgart | Stuttgart | Stuttgarter OpenStreetMap-Treffen | 2026-02-04 | | Le Schmilblick, Montrouge | Réunion des contributeurs de Montrouge et du Sud de Paris | 2026-02-05 | Montpellier | La Base | Mapathon OSM à La Base : cartographier Haïti pour la prévention des risques ​ | 2026-02-05 | Freiburg im Breisgau | CCCFR | OSM-Treffen Freiburg/Brsg. | 2026-02-05 | Braunschweig | Stratum 0 | Braunschweiger Mappertreffen im Stratum 0 Hackerspace | 2026-02-07 | København | Cafe Bevar’s | OSMmapperCPH | 2026-02-08 | Chennai Corporation | | Mapping Party @ Chennai | 2026-02-08 | | | Missing Maps : Mapathon en ligne – CartONG fr] [ | 2026-02-09 | 臺北市 | MozSpace Taipei | OpenStreetMap x Wikidata Taipei #85 | 2026-02-09 Note: If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM. _This weeklyOSM was produced by MarcoR, MatthiasMatthias, Raquel Dezidério Souto, Strubbl, Andrew Davidson, barefootstache, derFred, miurahr. We welcome link suggestions for the next issue via this form and look forward to your contributions._

I am using QGIS v4.0.2. My goal is to extract countries land and coastal borders from OSM using QuickOSM. I have successfully extracted the land borders of a few smaller countries like Denmark and Iceland using this QuickOSM quick query: https://i.sstatic.net/UD2tyILE.png But this includes the EEZ which I do not want. This doesnt matter for land locked countries but is very noticeable with countries with large coastlines just turning into soft blobs of geometry. When I try to export larger countries like the USA, China and Russia, I get a "OverpassAPI timeout, try again later or a smaller query." error. This error also persists after increasing the timeout to over 1000. And my final adjacent question is: How do I extract every red restricted area in a country or in the world as denoted by the polygon with dashed lines? https://i.sstatic.net/0dOm0oCY.png

When making a quick request through the QuickOSM module, the following error occurs: Overpass API: Failed to load: Error transferring https://overpass-api.de/api/interpreter?info=QgisQuickOSMPlugin - server replied: Gateway Timeout

I want to make a preset from the selection of queries that i have made in the quick query tab, when i try to save it as a new preset i get the following error FileExistsError: [WinError 183] Cannot create a file when that file already exists: 'C:\\Users\\name\\AppData\\Roaming\\QGIS\\QGIS3\\profiles\\default\\QuickOSM\\query_preset\\railway_building' Traceback (most recent call last): File "C:\Users/name/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\ui\quick_query_panel.py", line 261, in save_query q_manage.add_preset(properties['layer_name']) File "C:\Users/name/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\core\utilities\query_saved.py", line 168, in add_preset os.mkdir(join(preset_folder, self.name[0])) FileExistsError: [WinError 183] Cannot create a file when that file already exists: 'C:\\Users\\liami\\AppData\\Roaming\\QGIS\\QGIS3\\profiles\\default\\QuickOSM\\query_preset\\railway_building' Python version: 3.12.13 (main, Mar 5 2026, 15:14:54) [MSC v.1944 64 bit (AMD64)] QGIS version: 3.44.8-Solothurn Solothurn, d25052deb8b Python Path: C:/PROGRA~1/QGIS34~1.8/apps/qgis-ltr/./python C:/Users/liami/AppData/Roaming/QGIS/QGIS3\profiles\default/python C:/Users/liami/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins C:/PROGRA~1/QGIS34~1.8/apps/qgis-ltr/./python/plugins C:\PROGRA~1\QGIS34~1.8\apps\grass\grass84\etc\python C:\Users\liami\Documents C:\Program Files\QGIS 3.44.8\bin\python312.zip C:\PROGRA~1\QGIS34~1.8\apps\Python312\DLLs C:\PROGRA~1\QGIS34~1.8\apps\Python312\Lib C:\Program Files\QGIS 3.44.8\bin C:\PROGRA~1\QGIS34~1.8\apps\Python312 C:\PROGRA~1\QGIS34~1.8\apps\Python312\Lib\site-packages C:\PROGRA~1\QGIS34~1.8\apps\Python312\Lib\site-packages\win32 C:\PROGRA~1\QGIS34~1.8\apps\Python312\Lib\site-packages\win32\lib C:\PROGRA~1\QGIS34~1.8\apps\Python312\Lib\site-packages\Pythonwin C:/Users/liami/AppData/Roaming/QGIS/QGIS3\profiles\default/python it makes a json file but i dont think that is a preset and it doens appear in the preset tab, this is my selection of fields Any help that you can give will be appreciated

I want to figure out (qualitatively) how much area of my city has a bus stop within 400 m walking distance. My approach so far is to load all bus stops and draw circles with radius = 400 m around them. Then I can see how much of the city is covered in circles. I use QGIS, OpenStreetMap and the QuickOSM plugin. I seem to get something wrong with the measurements / projections though. Starting from knowing nothing, I figured out the following: * I can easily get all the bus stops as a layer with QuickOSM. * I can then modify the symbol layer. I tried 800 meters in scale (as the input seems to be diameter) but surprisingly the diameter is then not 800 meters - well, it is, but only if I change the measure tool to cartesian. * But it should not be Cartesian, it should be the default, ellipsoid, as that is what is used to measure "real life" distances - as in, if I leave my house and walk 100 meters, the same distance will show up as 100 meters in QGIS if I measure based on the ellipsoid. * I figured out that the bus stops layer uses EPSG 4326 WGS 84 as source while OSM Standard, loaded via the Quick Map Services, uses EPSG 3857 WGS 84 as source. Now if I understood it correctly, one is position on the globe and one is position on my map. It makes sense to me that meters have different meanings then, but still the bus stops end up at their actual positions just fine. I just can't draw circles around them. I tried re-projecting the bus stop layer to EPSG 3857 but that did not help at all (and probably does not make sense). I also noted that for OSM, "meters in scale" and "map units" seem to be identical. I read something about EPSG 3857 meters not being real meters but I do not know what to do with that. Is that the issue? How do I correct for the "fake" meters? How can I address my original problem and what is the explanation? It especially makes me wonder why measuring in Cartesian matches exactly what I entered in the "meters in scale" box. Meta information: QGIS 3.24, QuickOSM 2.0.1, my location is Germany.