Fairview is comprised of smaller former real estate ventures. When a new area was built it was given a name by its developers. I am slowly researching those development names and adding them to OSM as I go. My neighborhood, for example, was called Hill-N-Dale. Tonight I’m working on Hayward Heights, which still displays its sign where it branches off from East Avenue.

Not a lot to say, other than “I’m glad to be starting!” I set up the following in my profile, which seemed as good a place to start as any:

Overview

GIS amateur in rural Maine, United States

Introduction

Hi there! I’m Geo, and I’m thrilled to contribute to public GIS data & resources! I’ve been editing Wikipedia since 2005, but despite registering in 2008, I’ve only started editing OSM in late 2025!

I can bring local knowledge from my area of Maine - Waldo County - and possibly more.

شرکت آذرگشت سهند شماره تلفن 02156371922 شماره همراه091259754461 حمل و نقل مسفر کد پستی 3314768993 آدرس اسلامشهر خ صیاد شیرازی زاهدی 2 پ b3 www.azar-ghasht.ir

Recently I’ve made some logos for the Italian community (osm.wiki/Logos#in_Italy) and today I want to tell you how to I make this logos.

The first step is always to analyze what data do I need to represent and research how to get it, the https://osm-boundaries.com/ has been helpful to get this data and to get a first imprint of how the border is.

I usually download the data in an OSM format and then I use the ogr2ogr tool to convert the data in a format compatible with QGIS like GPKGs, this will be important later in the creation of the logo since I need the representation to be an SVG file to put together with all the other elements of the logo, like the map and the magnifying glass.

After downloading boundaries I start searching all the elements and how I need to represent them in the map, like for the Italian railway logo I proceeded to make different GPKGs file with all the necessary railway data divided into the various types, this can be achieved with a regional osm file, osmium and ogs2ogr.

After this we have to put together the data, and believe it or not this is going to be the hard part.

After making the GPKGs we open QGIS and open the files with it, by doing this we can put them together and customize the representation of the data for the logo, after this we can make a layout and render an SVG file from all the data we’ve imported.

Once we have the SVG export we are able to use a program like Inkscape to put together the SVG file with the default Logo file, usually what I do is deleting unnecessary detail from the original logo, changing the background color and making changes to other details in SVG to mek the logo look better or more personalized.

Once done this the only thing left to do is giving the logo to the community and “fine-tune” it based on opinions.

I know this is a quite scarce guide but it’s left a little bit unexplained because I don’t want to give a step-to-step guide to make a logo, following a procedure while it may create a good result it won’t ever be as good as a logo that has been made from the creativity of one person.

This said explore and try out new approaches, that’s all from me and if you want more details you can find me probably on telegram or on the profile or by looking at my wiki page.

13/11/2025-19/11/2025

Mapping campaigns

• confusedbuffalo is proposing an automated edit of phone numbers in the US to remove extra punctuation and to add the country code. This will standardise numbers and make it easier to identify genuinely invalid phone numbers. Contributors are invited to discuss in the forum thread and get in touch if they think such an edit would also be useful and accepted in their country.

Community

• Alex Spritze has recorded ► his OSM editing activity and then published it on YouTube.
• Ian Buck and Parker Seaman, of the Streets.mn podcast, have conducted an interview with Jackson Kruger, a Minnesota-based OpenStreetMap contributor, in an episode titled ‘Demystifying OpenStreetMap’.
• Arizona State University News reported that YouthMappers marked its tenth anniversary on 17 November. Over the decade it has grown to 400 chapters in 80-plus countries with 26 million OpenStreetMap edits.

Imports

• GridRecce is preparing an OSM import project to improve address coverage in the City of Brampton, Canada, using open data provided through the Brampton GeoHub.

Humanitarian OSM

• A surge of recent mapping activity has been recorded in the areas surrounding Indonesia’s Mount Semeru, the highest peak of Java. The pattern reflects humanitarian mapping efforts by the OpenStreetMap Indonesia community following the volcano’s eruption on Wednesday 19 November at 4 pm local time.

Maps

• Bella Mironova shared a submission for Day 14 of the 30DayMapChallenge: a map titled ‘Palmanova’, depicting the star-shaped fortress city in northeastern Italy. This map was created using OpenStreetMap data.

OSM in action

• Dennis Metzler has built ► CacheTycoon, a mobile treasure-hunting game that uses GNSS and OpenStreetMap data to guide players to nearby caches. By locating these points, players can collect rewards, unlock achievements, and advance through the game’s levels.

Releases

• In the November update of Organic Maps, lakes, protected areas, and boundaries of uploaded regions are now displayed on overview zooms. Routing also now takes into account conditional access restrictions.
• Pablo Brasero gave a rundown of changes made to the OpenStreetMap website software since mid-October, including more dark mode compatibility, a redesigned context menu on the home page, and lots of behind-the-scenes improvements to the developer experience.
• Tobias Zwick announced the release of StreetComplete version 62.0, which introduces several new quests and improvements.

Did you know that …

• … ^[1] Zartbitter has a web map that visualises turn restrictions using OpenStreetMap data and will flag those with errors?
• … you can find all of weeklyOSM’s articles as a .csv file in Raquel Dezidério Souto’s GitHub repository? The extraction was done by TheFive, lead developer of the OSMBC. The last backup was done on 15 November 2025 and we intend to update this on a regular basis.

OSM in the media

• Pernille Tranberg, of DataEthics, has written an article titled ‘OpenStreetMap is for the People’. The article notes that OSM is maintained by a global community of volunteers who prioritise human-centred mapping, allowing users to find routes for walking, biking, or specific needs like finding shaded paths, all while offering an environment free from surveillance capitalism.
• The public broadcaster in Cherkasy, Ukraine, has spoken with architect and OpenStreetMap contributor Fedir Gontsa about the reconstruction of historic slopes, the city’s architectural heritage, and the importance of high-quality mapping for urban planning.

Other “geo” things

• The French National Library has launched Galligeo , a tool for visualising (on an OSM tile background) geolocated maps from its collection. It is also possible to contribute to the geolocation of historical maps.
• Zhenlong Li, a professor at Penn State University (PSU), has shared that the SpatialAnalysisAgent (or the GIS Copilot), a user-friendly QGIS plugin, now offers free access with a GIBD account with a daily limit. The PSU has also published a good guide to learn how to create an account and start to use the geoAI.
• Sorami Shiromizu has published an article about Rekichizu ►, a website where users can view historical Japanese maps presented with modern cartographic design. The project’s main developer, Hajime Kato, gathered various old maps and historical documents from libraries across Japan, digitally traced them using QGIS, and applied an original map style intended to convey the historical atmosphere while preserving modern readability.

Upcoming Events

Country	Where	Venue	What	When
			Missing Maps : Mapathon en ligne – CartONG [fr]	2025-11-24
	Karlovac	Prostorija, Mije Krešića 4, Karlovac	OSM predavanje i StreetComplete u praksi u Karlovacu	2025-11-25
	Berlin	Online	OSM-Verkehrswende #70	2025-11-25
			Transmission Grid Mapping MapYourGrid	2025-11-26
	Toronto	Workhaus Dundas	Workhaus Mapathon!	2025-11-26
		Fabrique des possibles	Réunion OpenStreetMap	2025-11-26
	Hannover	Kuriosum	OSM-Stammtisch Hannover	2025-11-26
			Mittelweser-Mappertreffen	2025-11-26
	Düsseldorf	Online bei https://meet.jit.si/OSM-DUS-2025	Düsseldorfer OpenStreetMap-Treffen (online)	2025-11-26
	Freiburg im Breisgau	CCC FR	OSM-Treffen Freiburg Br.	2025-11-26
			[Online] OpenStreetMap Foundation board of Directors – public videomeeting	2025-11-27
	Trento	Trento	FOSS4G-IT – OSMit 2025	2025-11-27 – 2025-11-28
	Amsterdam	TomTom HQ	Maptime Amsterdam: Map & Meet	2025-11-27
	Madrid	Online	Mappy Hour OSM España	2025-11-27
	Општина Стара Пазова	Saloon Two guns	Redovno okupljanje	2025-11-27
	Dar es-Salaam		State of the Map Africa 2025	2025-11-28 – 2025-11-30
			OSMF Engineering Working Group meeting	2025-11-28
	Bengaluru	Shanti Nagar	OSM Bengaluru Mapping Party	2025-11-30
	Melbourne	AURIN, Melbourne Uni Baldwin Spencer Building 113	PIA Urban Data Network Missing Maps: Map Party for a Cause Melbourne	2025-12-01
	Oslo	Mesh Nationaltheatret	Mapathon – Monthly Missing Maps w/ EWB Norway	2025-12-02
	Salzburg	Bewohnerservice Elisabeth-Vorstadt	OSM Treffen Salzburg	2025-12-02
	Bern	Yaadein, Bern	Berner OpenStreetMap-Znacht	2025-12-02
			Missing Maps London: (Online) Mapathon [eng]	2025-12-02
	Derby	The Brunswick, Railway Terrace, Derby	East Midlands pub meet-up	2025-12-02
			iD Community Chat	2025-12-03
			OSM Indoor Meetup	2025-12-03
	Stuttgart	Stuttgart	Stuttgarter OpenStreetMap-Treffen	2025-12-03
	Madrid	Online	Mappy Hour OSM España	2025-12-04
			UN Mappers #ValidationFriday Mappy Hour	2025-12-05
	Olomouc		SotM CZ+SK 2025	2025-12-05
	大阪市	大阪大学中之島センター	State of the Map Japan 2025	2025-12-06
	Paris	Carrefour Numérique² de la Cité des Sciences	PSL XXL	2025-12-06 – 2025-12-07
	Biella	Sala Riunioni 2, CTV Centro Territoriale per il Vo	Incontro dei mapper di Biellese, Vercellese e Canavese	2025-12-06
	Braunschweig	Stratum0	Braunschweiger Mappertreffen im Stratum0 Hackerspace	2025-12-06
	नई दिल्ली	Jitsi Meet (online)	OSM India – Monthly Online Mapathon	2025-12-07
			Missing Maps : Mapathon en ligne – CartONG [fr]	2025-12-08
	臺北市	MozSpace Taipei	OpenStreetMap x Wikidata Taipei #83	2025-12-08

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.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

足球场

各种足球场的标线异曲同工，生活中也很常见。

就尺寸上来看——

• 11人制足球场（也是最常见的标准足球场）：长度一般在105米左右，上下误差不超15米；宽度跨度较大，从45米到90米不等，70米左右比较常见。
• 由于空间限制或实际需求，5人制足球场也不算少见。5人制足球场长度最长42米，最短25米；宽度最长25米，最短15米。一般5人制足球场长宽均不足11人制足球场的一半，因此其面积一般不足11人制足球场的四分之一。
• 有时还会看到7人制足球场，长65~68米，宽45~48米。

注意：无论何时，正规足球场必须是长方形，边线的长度必须长于球门线的长度。

篮球场

这个就更常见了，同样是长方形，而且样式尺寸也更单一、更具标识性，故直接上图：

篮球场主场长28米，宽15米。加上副场的标准篮球场，总长32米，宽19米。

网球场、羽毛球场、排球场

三种球场同样都是长方形，且标线貌似也差不多，如何区分呢？

第一张图是网球场，第二张图是羽毛球场，仔细看，他们的标线还是有所不同的：网球场因单、双打划分出的四块发球区集中在中间，而羽毛球场的则靠近两端。而排球因为一般无单双打之说，如第三张图所示，场地的发球区没有分割。

如果觉得这个方法不方便的话，仍然可以通过尺寸大小来判断。十分简单，只需记住网球场长20米，宽10米，而羽毛球场长10米，宽5米，是网球场的二分之一，所以面积是羽毛球场网球场的四分之一。（以上数字均为约数）至于排球场，长18米，宽9米，都是整数，比网球场略小一点，但明显比羽毛球场大。

总结

• 大多数长方形球场，长宽之比约是2:1。小规格足球场除外。
• 在所有常见的长方形球场中，足球场最大，篮球场次之，排球场和网球场再次之，羽毛球场最小。
• 上述一些不太规整的尺寸，大都是英制单位的遗留问题，还有是约定俗成导致的标准化难。
• 除了这些长方形的球场，还有一些名字里带“球”的，比如铅球场、高尔夫球场等，本篇文章暂且不做讨论。

I’ve lived in this unincorporated neighborhood since 2004. Earlier this year, the U.S. Post Office with feedback from the Fairview Municipal Advisory Council (and surveys sent to residents) reverted our place name from “Unincorporated Hayward” to Fairview while leaving the zip code the same: 94541.

Twenty-one years of living here I’ve learned that you either know about this area and how it works or you’ve never heard of it. I was originally of the “never heard of it.” In 2010 I worked as a census enumerator sent to addresses that hadn’t mailed in their census packet. That’s when I really got to learn how Fairview works and how to use local data to better understand the area.

Now I am slowly working through my neighborhood in OSM to map it. I started with my house (my second residence here) and I’m working my way out. I am learning by doing (and reading the wiki).

The grumpy old man returns.

My diary entries all all my own thoughts and do not represent OpenStreetMap, The Humanitarian OpenStreetMap Team (HOT) or any organisation using the HOT systems. Any errors are all my own work.

This first diary entry is based on my response to a mapper on the HOT Slack Channel asking about validation methods.

When it comes to HOT mapping and validation, I’d say there are not really any standards, or training to judge mapping against those standards. It’s a constant frustration of mine. However, the use of the data should be considered when validating tasks. If a road in Africa is a few meters out from a vehicle GPS while driving, does it really matter? The driver is going to follow the track. Relative positions are more important - do things match what might be seen in the field?

Skipping a task that you don’t feel experienced enough to validate seems a mature approach to me. I also try to map a few tasks in a project before validating tasks to get some understanding of the problems mappers may face.

I’ve only been seriously HOT mapping with some validation since early 2024, although I’ve mapped in a small way since April 2019, including my own locality. I’ve developed the thought that there are three basic types of validators;

1. Validators who simply approve or reject tasks. These validators are usually new validators and sometimes they are still new mappers! These validators may give basic feedback such as ‘more mapping needed’. This is not very useful. It is not targeted to the task problem or the mapper.
   I’ve seen projects requiring roads, buildings and waterways with validated tasks without rivers mapped where rivers are visible. This is task fixation on buildings and roads because this is the requirement of many projects. It shows that mappers and validators are not reading the instructions. Sadly, some instructions are very poor, but that’s a separate discussion!

2. Validators who reject tasks with feedback that is relevant to specific problems and named mappers, often with image based examples. I try to be one of these. I’m not just looking to get the project finished, but to develop the mapper skills. This is more beneficial to the long term mapping quality. I call this Validation for the Mapper. I’m trying to develop mapper skills to make future validation easier and hopefully complete projects more quickly.
   It is probably the most time consuming and frustrating type of validation as many comments are ignored as most mappers never review the history comments. Several cycles of new mapper submissions and rejections with no mapping changes may occur before a mapper does read the history and correctly maps the task.

3. Validators who used to be type 2 validators. but may have become frustrated with the cycles described in 2 and just fix all the problems themselves. The project makes more rapid progress, but the mappers have no idea if they mapped well or not. I call this Validation for the Project. It gets the project completed with good quality, but may take up unnecessary validator time and it does not improve mapping skills in others.
   This can result in more validation work over the long term for all types of validator because the mappers may think that what they have mapped was good enough when it was not.

I usually fix small problems such as two or three missed or misshapen buildings, but I will state what I did in feedback, sometimes with images. This is very time consuming. I won’t do lots of mapping as a validator as I value my time. I’d rather map well first time than have my time wasted fixing up large amounts of poor mapping. I reject such tasks with appropriate feedback.

The biggest issue with rejecting tasks is that most mappers only map once. The statistics are obvious. https://tasks.hotosm.org/ shows over half a million mappers, but the number of on-line mappers can be single figures. It is probably only over 30 when mapathons take place. Mapathons usually mean many of new mappers at once and the associated problems. However most of us have likely started with a mapathon, so they are useful events.

For validation training, I suggest you join one of the early in month Missing Maps London on-line mapathons. These are focused on training new mappers with the iD Editor or JOSM. There is usually some validation training depending on numbers and trainer availability.

The mid-month Missing Maps London on-line events focus on experienced mappers and potentially more challenging or restricted projects. These and other mapathons can also be found on the OpenStreetMap Calendar.

There are also recorded webinars and tutorials on the HOT YouTube channel to help mappers and validators. Some of the videos are short, some are very long! Additional webinars may be notified on the HOT Slack Channel from time to time. Some mappers and validators also respond to questions asked on the HOT Slack Channel and past conversation may be searched.

Hopefully we’ll see you on-line. Happy Mapping!

เก้าเลี้ยว, เก้าเลี้ยว, นครสวรรค์, 60230

Haihole Dam is constructed across Kanee halla river near Haihole village about 12 Km from Shimoga city. Kane halla is a small tributary to Tunga River which originates in Shankaragudda hills and flows mostly in thick forest. This dam is located at longitude 75deg 28’ 45” E and Latitude 13deg 53’ 08” N in the limits of Haihole village in Shimoga taluk and district. This dam has been constructed during the period 1976-79 and is in operation since then The independent catchment area of the river at the dam site is 37.81 sqkm. The stream has its origin in a fairly heavy rainfall area with its entire catchment being in hilly and forest region and hence considered as Good for yield calculation. There are gauge stations situated near to the catchment area. However four influencing rain gauge station visa, (1) Malur (2) Aynur (3) Shimoga (4) Umblebylu have been considered for yield calculation. These polygons has been drawn on the basis of these four influencing rain gauge stations and the average rain falls have been calculated for these four rain gauge stations taking into consideration the rain fall of Ten years (1952 to 1963). The average rain fall works out to 98.55 cm with 70% dependability (year 1956) Considering the catchment area as Good for average annual rainfall of 98.55 cm the yield available at dam site is 13.52 cum (477.00 mcft.) apart from this perennially flowing two small streams across which the dam is constructed discharge about 0.11 to 0.14 Cumecs during the summer months due to the existence of some springs in the Shankaragudda hills also contribute to yield. There is good flow during the monsoon months and fair flow during November and December.

De Westwouderpolder is een polder én een eiland, zie de Historie, bereikbaar met de pont. Op De Woude zijn geen parkeerplaatsen, je kan voor de pont je auto achterlaten op het parkeerterrein.
* Geoapps Noord-Holland
* Geonames
* Staatsbosbeheer
* OSM
* wikipedia - de Woude

anyone in my area want to help me learn this. Having touble piping in my gps puck into OSM. I do SKYWARN and use my laptop and gps regulalry with other applications with no issues. I just want to learn osm.

Does anyone on here know the history of families in the area? Where they lived? May still live? I have tracked my Caskey ancestors to this area and am seeking info on them. My great great grandfather was from this place and moved to Yarmouth, Nova Scotia, Canada. His name was William Caskey. Cheers.

das ist der erste Test wies geht

• Interactieve kaart Oer-IJ
• Website Stelling
• OSM

dear diary i love <3 osm

The osm.org website currently has two “OSM-hosted” map styles on it - the “Standard” style (raster tiles) and a “Shortbread” one. The schema for “Shortbread” is here, and the display style shown is “Colorful” from Versatiles. It looks like this:

That’s … less informative than it could be. Most of those points of interest have names, which aren’t shown, and small grey icons on beige isn’t especially doesn’t help. Instead, let’s try a different one (see the picture at the top).

Immediately, footpaths, shop names and even restaurant cuisines are now visible. See that here and try moving around.

So how to install that on a server?

The map style is using OSMF’s shortbread-schema vector tiles, but the style itself consists of a few flat files that can be installed on pretty much any web server.

Here’s what it took to install on a brand-new server. My test examples was running “Debian 12” and I’ll install Apache for a web server, bit it’s certainly possible to use something else instead. To get started:

sudo apt install git apache2

From a non-root user that I’ll refer to as “youruserid”, we’ll create a “src” directory if it does not already exist, and get a couple of projects there:

mkdir ~/src
cd ~/src
git clone https://github.com/SomeoneElseOSM/SomeoneElse-vector-web-display
git clone https://github.com/systemed/tilemaker

“SomeoneElse-vector-web-display” contains the management scripts that are used to deploy a web page for external consumption as well as the actual style definition itself, and the only thing that we need from “tilemaker” are the font files.

Apache’s web root on Debian is typically /var/www/html/; we’ll create a directory below there to deploy in to:

sudo mkdir /var/www/html/vector

That path is hardcoded in the deployment script below but you can change it if necessary. We’ll then run that deployment script

sudo /home/youruserid/src/SomeoneElse-vector-web-display/svwd_into_apache.sh NONE svwd03 http://youripaddress /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03_spec.json /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03_metadata.json /home/youruserid/src/tilemaker/server/static/fonts /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03_style.json /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03_index.html svwd03sprite /home/youruserid/src/SomeoneElse-vector-web-display/resources

The references to /home/youruserid/src/ are just were we got the software earlier. The parameter http://youripaddress describes exactly how will access the site. If you already have a site set up at (say) https://mydelightfulmap.com (with an https certificate for that address) then you’d use that in place of “http://youripaddress” above. Because all the scripts point to the same place, we don’t need to worry about CORS unless we actually have multiple names pointing at it. The name “svwd03” is just the name of the map style - various sets of files with that name are copied from the source directory to the web server.

The output from that command will be something like:

youruserid@debian:~/src$ sudo /home/youruserid/src/SomeoneElse-vector-web-display/svwd_into_apache.sh NONE svwd03 http://youripaddress /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03_spec.json /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03_metadata.json /home/youruserid/src/tilemaker/server/static/fonts /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03_style.json /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03_index.html svwd03sprite /home/youruserid/src/SomeoneElse-vector-web-display/resources
Created spec file:     /var/www/html/vector/spec_svwd03.json
Created metadata file: /var/www/html/vector/metadata_svwd03.json
Installed fonts into:  /var/www/html/vector
Created style json:    /var/www/html/vector/style_svwd03.json
Created web page:      /var/www/html/vector/index_svwd03.html
Access via:            http://youripaddress/vector/index_svwd03.html
svwd03sprite@2x.png and svwd03sprite@2x.json copied to /var/www/html/vector
svwd03sprite.png and svwd03sprite.json copied to /var/www/html/vector
No optional @3x sprite files created; /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03sprite@3x.png does not exist.
No optional @4x sprite files created; /home/youruserid/src/SomeoneElse-vector-web-display/resources/svwd03sprite@4x.png does not exist.

As that suggests, we can just point a web browser at the URL on the “Access via” line to see a map. The resulting “index_svwd03.html” can of course be edited as desired, or incorporated into something else. In that, the call that sets up the map is:

map = new maplibregl.Map({
    container: 'map', // container id
    style: styleURL, // stylesheet location
    center: [ -1.5, 53 ], // starting position [lng, lat]
    hash: true,
    zoom: 8, // starting zoom
    maxZoom: 25,
    attributionControl: true
});

Changing the longitude and latitude of the centre of the map and the starting zoom level are straightforward.

For ease of debugging, there’s some debug code in the generated .html that is commented out by default. Set this to true to see vector tile boundaries:

map.showTileBoundaries=false;

and uncomment this section to load the inspector:

map.addControl(new MaplibreInspect({
     showInspectMap: true,
     showInspectButton: false
}));

Next step, modifying the style

Watch this space …

OpenStreetMap sleduji už mnoho let nejen jako užitečný nástroj, ale jako jedinečné společenství lidí, kteří dobrovolně budují mapu světa. Přitahuje mě otevřený, „wikipedický“ duch a pocit, že společně tvoříme něco, co má smysl a skutečně pomáhá. Poslední roky OSM vstupuje do období, které přináší nové výzvy i novou odpovědnost. Diskuze se už netočí jen kolem technických detailů. Diskutuje se, co vlastně znamená tvořit otevřená geodata v době velkých korporací a umělé inteligence.

Korporace jsou všude

Je zřejmé, že globální firmy jako Apple, Meta, Microsoft nebo navigátory TomTom mají o OSM velký zájem. Pochopily, že utvořit novou, vlastní mapu od nuly je prakticky nemožné a především drahé. Připojují tedy do projektu rozsáhlé mapovací týmy, využívají interní nástroje, importují vlastní datové sady. Tempo, s jakým dokážou doplňovat či aktualizovat data která je zajímají, je ohromující.

Přínosy jsou zjevné. Povrch světa je intenzívněji mapován. Zároveň ale soudím, že s tím roste i riziko, že se ztratí cit pro místní kontext a jemnost komunitního mapování. OSM dlouhodobě stojí na dobrovolnících, kteří mapují proto, že jim záleží na svém okolí. Tahle subkultura je křehká. A pokud má mít projekt budoucnost, neměla by být přehlušena privátním zájmem vydělat na odvozené službě.

AI v mapování

Umělá inteligence dokáže během pár minut odhalit mnoho nezmapovaných budov, nově vzniklé cesty, nebo změny v krajině. V oblastech třetího světa, které zůstávaly roky nemapované, to je obrovský skok kupředu.

A přesto u toho doporučuji i určitou opatrnost. AI má občas tendenci fungovat jako silný nástroj – užitečný, ale schopný způsobit nechtěné škody. Chybný import může vyvolat nepochopení proč se tak stalo, zahlcovat komunitu opravami a narušit důvěru v kvalitu dat. Rizikem je i to, že se z mapování vytratí lidský dotek a procesní zkušenost. Naučit se správně mapovat je cesta a AI by ji neměla novým mapovačům sebrat.

Humanitární zkušenost

Můj vlastní zážitek s mapováním pro Lékaře bez hranic mě naučil, že mapa epicentra události může být daleko víc, než jen pečlivý záznam škod viděných z letecké fotografie. V kontextu humanitárních krizí se stává pracovním nástrojem, který rozhoduje o tom, jak rychle a efektivně dokáží týmy díky mapám pomoci lidem v ohrožení.

Práce v těchto projektech ve mně zanechala hluboký respekt k lidskému vedení, které takové aktivity drží pohromadě. Humanitární mapování není jen o datech – je o disciplíně, lidském úsudku, empatii a schopnosti porozumět situaci vzdáleně i na místě. A to jsou kvality, které žádná AI nenapodobí. Zároveň věřím, že právě tady mají vyrůstat nové generace mapovačů. Humanitární mapování učí skupinové spolupráci, zodpovědnosti i porozumění tomu, jak digitální nástroje mohou pomáhat společně s obětavými lidmi.

Vandalismus v mapách

Nedávno OSM čelilo i něčemu, co bych ještě před lety nepovažoval za pravděpodobné: rozsáhlému a dobře koordinovanému vandalismu. Šlo o kombinaci lidského úmyslu s naprogramovanými škodítky, které dokázaly nárazově poškodit velké plochy mapy.

Pro mě to byla připomínka, že ani tak mírumilovný a altruistický projekt není imunní vůči podvratným činům. O to větší obdiv mám k lidem, kteří s trpělivostí, často neviditelně, tento nepořádek uklízejí. Kdesi pod povrchem OSM pracuje mnoho obětavých editorů, správců a moderátorů – a jsem hrdý na to, že takové jádro vůbec existuje. Zaslouží si respekt a poděkování.

Správa projektu

S rostoucí velikostí OSM přibývá i diskuzí o tom, kdo a jak má nastavovat pravidla jak celosvětová, tak místní. Od velkých rozhodnutí až po zdánlivé drobnosti typu tagování přechodů – to všechno tvoří podstatnou část identity projektu. Tyto debaty mohou být nekonečné a únavné, ale jsou naprosto zásadní. Právě v nich se definuje, jak bude OSM fungovat, jaké standardy bude držet a jak se bude bránit tlaku komerčních zájmů či automatizovaných nástrojů.

Kam dál

OSM je dnes hodnotnější než kdy dřív. Má globální význam, mapy používají humanitární organizace, korporace je integrují do svých produktů a běžně čtou mapu miliony lidí. Právě proto je důležité, aby si projekt zachoval svou odolnost vůči zneužití i nechtěným zásahům. Jde tu o rovnováhu: technologie a velcí hráči mohou OSM posunout výrazně dopředu, ale neměli by přehlušit komunitní hlas, etický základ a hodnotu lidské práce. Mapy s otevřenými daty by měly být tvořeny především lidmi – s rozumem, pokorou a místní znalostí. Tohle je největší síla kterou stojí zato chránit, i když kolem slídí algoritmy a byznysové zájmy.

Heyho, das ist mein erster Blog auf OSM :)

Ich habe einen kleinen Tipp, wenn ihr mal Indoor Dinge mappt: Mit SCEE (Street Complete Expert Edition) kann man sich selber Overlays erstellen. Das habe ich vor allem genutzt, als ich ein Gebäude, das ich vorher schon mit Indoor Features gemappt habe, anschließend mit den richtigen Raumnamen versehen wollte.

Das hier ist mein Setup, das sogar anzeigt, wenn wo das level fehlt:

Letzendlich habe ich nur ein custom overlay erstellt, bei dem ich “indoor” als Filtering details und “level” als coloring details angegeben habe. Damit kann man jetzt indoor Objekte und Räume auswählen und sogar sehen, auf welchem Level sie sind und sie werden rot markiert, falls das level fehlt.

Das ist die bisher beste Art und Weise, die ich gefunden habe, um wenigstens ein bisschen indoor mapping auf dem Smartphone zu betreiben.

Ich hoffe, das lesen hier hat euch geholfen und ich wünsche weiter ein erfolgreiches Mapping :D

Wanna play a game about the State of the Map Europe conference?

https://zverikk.itch.io/dundee

For the last 10 days I’ve been travelling in Europe to go to OSM events. I have some spare time before my flights to get home to Vancouver, so I’m posting a brief overview of the events and what got done.

My first event was the Karlsruhe hack weekend. This event is held twice a year and attracts lots of German and Swiss OSM developers. I started out by discovering that the jet lag is worse as I get older and I missed the pre-event social.

At the event itself I focused on the Shortbread Vector Tiles specification and osm2pgsql. In total three people from the Shortbread steering committee were at the event. The main Shortbread coding that’s been completed was a cleanup of the tables in the 1.0 spec. I think this is the last change we’ll see to 1.0 and all my Shortbread focus is now on 1.1.

I haven’t yet published the changes but support for multiple languages in the OSMF shortbread vector tiles is basically done. I just need to clean up some changes and add them to the WIP commit. Initially the language list is only en and de, but it’s ready to be added to.

I met with the two other maintainers of osm2pgsql and we discussed what’s necessary to tag releases of osm2pgsql-themepark. I think we’ve got a route forward there.

I spent the Monday after the hack weekend around town. The next morning I started for Nottingham via the Eurostar train. While I was in Nottingham I visited relatives and didn’t do anything OSM-related.

On the trip north to Dundee I got a cheap seat upgrade on the train to Edinburgh. This gave me three hours of focused time to work on my SOTM EU presentations.

The first day of the conference was good. The talks I attended were - Human elements of trust and data misuse in open maps - Equal Access at the National Trust. The National Trust is doing good collaborative work with OSM and trails. I need to follow up with them about trail tagging efforts. - What’s New with our Website. The answer? Lots. Thousands of PRs were merged in the last year and development is moving at a good pace. - Servers on Fire: Keeping OpenStreetMap Online. This talk was by Grant, a fellow sysadmin, and was an interactive talk with “war stories” from running all the osm.org services. It was part of an effort to get more people interested in ops work, so if it sounds like something you’re interested in, please get in touch. I wasn’t the target audience for the talk because I had heard most of the stories. - Future of the OpenStreetMap Foundation discussion group. This focused on the funding shortfall. A full review of the session is more than I can do before my flight. - From Coast to Coast: OSM Coastal Landforms Tagging & Mapping Strategies across the Atlantic. This was a talk by someone from the Canadian Red Cross about mapping stuff near the ocean. I need to get in touch with the presenter because they’re a fellow Canadian - Shortbread Steering Committee meeting. Three of the steering committee members were at the conference. I wasn’t sure if this session would be just us three or more. It was way more, with probably 20-40 people. There was a lot of longer-term discussion but less on the issues that were holding back a 1.1 release. One misunderstanding during the session is that a lot of people thought that we didn’t want to put out a minor release with backwards compatible changes. This is wrong, because that’s what 1.1 is! There was also the common issue of software developers treating all technical computer projects as software development. Shortbread isn’t a software project, it’s a vector tile specification. We were able to iron out most of the 1.1 holdups in a couple minutes at the end.

After the talks we got locked into the building. When we found our way out we went to a local Weatherspoons pub.

I had two talks the next day, so I got some more work done on talk prep. The talks I went to were

• “Survey Me” - Using external data comparisons to flag issues in OSM. Lots of interesting tools are being run in the UK
• Using New Vector Tiles, one of my talks
• Make your own base map with MapLibre and Planetiler. I wasn’t the target audience for this workshop so I worked on my slides while following along.
• Minutely vector tiles deep dive, another one of my talks
• Everything Everywhere All at Once. This was about OSM Spyglass, a tool that is likely to replace the data layer on osm.org. You can see it at http://test.osm2pgsql.org/
• Overpass Turbo goes PostGIS. This was about postpass, a SQL-based server similar to Overpass
• Overpass API. This talk focused on the current issues the Overpass API is facing with limited capacity and the steps that are being taken.

My first talk was on how to use the vector tiles the OSMF makes. I’ll have a blog post version of this soon, but the example I walked through was building versatiles colorful to use the vector tiles, building a pmtiles file with wall data for the whole planet, and using Maputnik to add the wall data to the style.

The second was a deep technical dive into how the tiles are served. The focus was on the move from storing tiles to storing tile layers to improve performance. I felt less prepared for this talk, but people afterwards told me is was the better of the two talks I gave.

We went to a museum on the old jute industry in Dundee for the social. I stuck it out at the social until the hours of standing on a hard stone floor made me limp back to the hotel. I’m not as young as I used to be.

For the makeathon today (Sunday) we had all the ops people there. We had some internal dicussions about usage policy changes and preventing abuse of the OSMF-run services. Nominatim in particular is overloaded, but AI scrapers running through mobile device botnets are a problem everywhere.

We had a second meeting about how to get more people involved in ops. This is a bigger subject than I can write about before my flight, but if you’re interested in helping, get in touch. We have some tasks well suited to onboarding new people. We also had some discussion around longer-term planning.

All of us had been hoping to get more coding done during the makeathon. Spending most of the time in discussion meetings isn’t as fun but I’m glad we got the chance to sort things out face to face.

After the makeathon we went to a pub and had a fun time trying to identify the date of a map of Dundee that was on the wall. The map said 1982 but based on the lack of the road bridge and tram lines we think it was 1932.

I caught the direct train from Dundee to Glasgow and stayed at a hotel near the airport.

🌐 MAPEO DE RUTAS Y PARADAS COLABORATIVO METROPOLITANO

¡Te invitamos a formar parte de un proyecto ciudadano que busca mejorar la movilidad en toda la zona metropolitana! Tu experiencia diaria como usuario de transporte es valiosa: cada ruta que recorres y cada parada que utilizas ayuda a construir un diagnóstico real, actualizado y colaborativo del territorio.

Este mapeo abierto permite identificar:

🚏 Paradas de ascenso y descenso (formales e informales)

🗺️ Rutas completas (conjuntos de puntos/coordenadas)

🚲 Estacionamientos y biciestacionamientos

🚇 Líneas de metro, tren, teleférico

🚌 Rutas de camiones, combis, autobuses y servicios especiales

🚐 Transporte escolar, foráneo o alternativo

🛠️ Lugares donde debería instalarse o mejorarse una parada

Tu participación alimenta una base de datos pública que será útil para estudiantes, investigadores, colectivos, autoridades y cualquier persona interesada en la dignidad de la movilidad.

🔗 Más información y participación: https://encuestaorigendestino.my.canva.site/

Si quieres recibir novedades del proyecto o conocer los resultados, deja tu correo al final del formulario. Juntos podemos construir mejores rutas, mejores decisiones y un territorio más accesible para todas y todos.