Many people have noticed that publicly available Overpass servers have been suffering from overuse (a typical “tragedy of the commons”). OSM usage policies generally contain the line “OpenStreetMap (OSM) data is free for everyone to use. Our tile servers are not”. Unfortunately, there have been problems with overuse of the public Overpass servers, despite the usage policy. “Just blocking cloud providers” isn’t an option, because (see here - use the translate button below) lots of different sorts of IP addresses, including residential proxy addresses, are the problem.

People who want to use e.g. Overpass Turbo do have the option to point it at a different Overpass API instance. If you’re using Overpass Turbo and you get an error due to unavailability, likely that is because the Overpass API that it is using is overwhelmed. There are other public Overpass API instances, but they may be complete (in terms of geography, or history) or up to date.

At this point, if you’re one of the people who created the problem you’ll likely just spin up more instances to retry after timeouts and make the problem worse. Most people reading this are I hope not in that category. There are commercial Overpass API providers - more details for the example in that table can be found here.

Other people (including me) might wonder whether it’s possible (without too much work) to set up an Overpass API server that just covers one or two countries. To keep it simple, let’s restrict myself to Britain and Ireland 2.3GB in OSM, and let’s not worry about Attic Data (used for “queries about what was in OSM in the past”) or metadata.

Let’s just try and do regular Overpass queries such as you might start from this taginfo page, like this. I’ll also only target the Overpass API, and will use “settings” in an Overpass Turbo instance to point to my Overpass API server. I do want to apply updates as OSM data is changed.

I’m interested in creating a server covering the UK and Ireland. In terms of size, have a look at how much bigger or smaller your area of interest is than the 2.3GB of Britain and Ireland below and use that to judge what size server you might need.

Documentation

At this point it’s perhaps worth mentioning that the documentation around Overpass is … (and I’m channelling my inner Sir Humphrey here) “challenging”.

There’s the OSM wiki which talks about “Debian 6.0 (squeeze) or Debian 7.0 (wheezy)”, the latter of which went EOL in May 2018. There is also an HTML file on overpass-api.de. That is … (engages Sir Humphrey mode again) not entirely accurate, in that it says to run something that doesn’t exist if you’ve cloned the github repository.

One of the best document by far is external and is by ZeLonewolf, which starts off by saying “I found the existing guides to be lacking”. It then says “This is a combination of various other guides, the official docs, Kai Johnson’s diary entry…”

(which is the other “best document”)

“… and suggestions from @mmd on Slack. This guide is intended to demonstrate how to configure a server dedicated to only running overpass”. Kai’s diary entry from 2023 is definitely worth reading (sample quote there “Running an Overpass server is not for the faint of heart. The software is really finicky and not easy to maintain. You need to have some good experience with Linux system administration and the will and patience to deal with things that don’t work the way they’re supposed to”).

Also, this github issue (and things linked from it) summarises some of the issues that I had on the way to getting my test server set up.

Where what I’m doing below differs from what the other guides say I’ll try and say why I am doing it differently. Usually it’s because my requirements are different (e.g. an overpass server for a small area rather than everywhere, on a VSP rather than a piece of tin, or because I need limited functionality).

Server

For my use case, we’ll need a server that is publicly accessible on the internet to do this. I’m already a customer of Hetzner, so I’ll create a test server there. Other providers are available, and may make more sense depending where you are in the world and how much you want to pay. For testing, spinning up something at one of the hyperscalers might make financial sense, but I suspect not long-term. I went with a CX43 with 160GB of SSD disk space, 16GB RAM and a rather large amount of bandwidth. This turned out to be about the right size for Britain and Ireland. I went with Debian 13 and public ipv4 and ipv6 addresses. I don’t know if Overpass releases need a particular architecture, but went with “x86” rather than “ARM” just in case.

If you’re needs are different you don’t have to use a cloud server for this. and Kai’s diary entry has a lot of information about physical server sourcing and setup.

Sizing was alas largely guesswork and trial and error - while I’m sure that the commercial providers know chapter and verse on this, there isn’t a lot written down about “sizing based on extract size” that isn’t “how long is a piece of string”. I found that loading even North Yorkshire (just 56MB in OSM) created a nodes file in the database area of 23GB, so that sets the minimum server size, even for very small test extracts.

The speed of the disk used needs to be able to apply updates in less time than the updates are of. If it takes 2 hours to apply 1 hour of updates, your server will never catch up. In practice I didn’t find this to be an issue with the servers at Hetzer and the relatively small extracts that I was working with.

Initial server setup

In what follows I’ll use youruseraccount, yourserver and yourdomain in place of the actual values I used.

I already have some ssh keys stored at Hetzner, so when buying the server, I chose a new name in the format “yourserver.yourdomain” and added my ssh keys. I have yourdomain registered at a DNS provider, and I added the IPV4 and IPV6 addresses there. I can now ssh in as root to “yourserver.yourdomain”, and run the usual:

ssl -l root yourserver.yourdomain
apt update
apt upgrade

and bounce the server and log back in again.

The next job is to create a non-root account for regular use and add it to the “sudo” group:

useradd -m  youruseraccount
usermod -aG sudo youruseraccount
chsh -s /bin/bash youruseraccount

I’ll create a new password in my password manager for youruseraccount on this server (obviously I used my account name rather than actually youruseraccount, but you get the idea…). Next, set the new account password to the newly chosen password

passwd youruseraccount

and check I can login to the new server as youruseraccount with that password, and become root:

ssh -l youruseraccount yourserver.yourdomain
sudo -i 
exit

Install some initial software:

sudo apt install emacs-nox screen git tar unzip wget bzip2 net-tools curl apache2 wget g++ make expat libexpat1-dev zlib1g-dev libtool autoconf automake locate 

That list includes both software prereqquisites (apache2) and things that will be really useful (screen). It also includes emacs as a text editor; you can use your preferred one instead wherever emacs is mentioned below.

To use screen you just type screen and then press return. You can manually detach from it by using ^a^d and later reattach by using “screen -r”. If there are multiple screens you can attach to you’ll see something like this:

There are several suitable screens on:
    95207.pts-2.h23 (02/15/2026 09:20:20 AM)        (Detached)
    95200.pts-2.h23 (02/15/2026 09:19:57 AM)        (Detached)
    1633.pts-2.h23  (02/14/2026 12:37:50 PM)        (Attached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.

and you can choose which one to reconnect to by typing in (say) “95207” and pressing “tab”. To force a reconnection to a screen that something else is attached to, use “screen -d -r”.

In many cases below I’ll say “(in screen)” - this just means it’s a good idea to run these commands from somewhere that you can detach from and reattach to. It doesn’t mean you need to create a new screen every time.

The ssh keys that I had stored have been added for root by Hetzner, but I also want to add them to my new account too:

sudo -i
sudo -u youruseraccount -i
ssh-keygen -t rsa
(either use existing password for ssh passphrase, or create and store a new one)
exit

cp /root/.ssh/authorized_keys /home/youruseraccount/.ssh/
emacs /home/youruseraccount/.ssh

… and in there change the ownership of the files to youruseraccount.

Next, check that you can ssh in to yourserver.yourdomain without a password. Next disable regular password access. We don’t want people to be able to brute force password access to a server on the internet, so we can just turn this off.

sudo emacs /etc/ssh/sshd_config

Find the line that says

# To disable tunneled clear text passwords, change to "no" here!

and uncomment and change the next two lines to say

PasswordAuthentication no
PermitEmptyPasswords no

save the file and then

sudo /etc/init.d/ssh restart

and then try and login (from the shell on that machine will work as a test)

ssh 127.0.0.1

It should say Permission denied (publickey).

Setting up a certificate is the next priority. Everything on the internet these days pretty much assumes https access, so let’s do that before even thinking about overpass. I’ll use acme.sh for that. Other providers and tooling are available and you can use them if you prefer. Login as your non-root account and then:

sudo -i
cd
wget -O -  https://get.acme.sh | sh -s email=youremailaddress
exit
sudo -i
/etc/init.d/apache2 stop
acme.sh --standalone --issue -d yourserver.yourdomain -w /home/www/html  --server letsencrypt

the last lines of the output you get should be like

-----END CERTIFICATE-----
[Sat Feb 14 12:51:45 AM UTC 2026] Your cert is in: /root/.acme.sh/yourserver.yourdomain_ecc/yourserver.yourdomain.cer
[Sat Feb 14 12:51:45 AM UTC 2026] Your cert key is in: /root/.acme.sh/yourserver.yourdomain_ecc/yourserver.yourdomain.key
[Sat Feb 14 12:51:45 AM UTC 2026] The intermediate CA cert is in: /root/.acme.sh/yourserver.yourdomain_ecc/ca.cer
[Sat Feb 14 12:51:45 AM UTC 2026] And the full-chain cert is in: /root/.acme.sh/yourserver.yourdomain_ecc/fullchain.cer

Next do

sudo a2ensite default-ssl
sudo a2enmod ssl
sudo systemctl reload apache2

and then edit the default site config

sudo emacs /etc/apache2/sites-enabled/default-ssl.conf

Replace the SSL references with the correct ones.

SSLCertificateFile      /root/.acme.sh/yourserver.yourdomain_ecc/fullchain.cer
SSLCertificateKeyFile   /root/.acme.sh/yourserver.yourdomain_ecc/yourserver.yourdomain.key

Restart apache

sudo systemctl restart apache2

and browse to https://yourserver.yourdomain to make sure that the certificate is working. You’ll need to arrange for that certificate to be renewed every couple of months, but let’s concentrate on overpass for now.

That is it for the initial server setup, so now would be a good time for a server snapshot or other sort of backup.

Setting up the user for Overpass

For this part, we’re going to follow parts of ZeLoneWolf’s guide. I’ve reproduced that mostly as written below, although some of the software already was installed earlier.

sudo su

mkdir -p /opt/op
groupadd op
usermod -a -G op youruseraccount
useradd -d /opt/op -g op -G sudo -m -s /bin/bash op
chown -R op:op /opt/op
apt-get update
apt-get install g++ make expat libexpat1-dev zlib1g-dev apache2 liblz4-dev curl git
a2enmod cgid
a2enmod ext_filter
a2enmod headers

exit

The username that we created above is “op”. We won’t use a password for that but will just use

sudo -u op -i

when we need to change to it from our normal user account.

Configuring Apache

We already have Apache set up with a default HTTPS website that says “It works!”. We’ll use some of what’s in ZeLoneWolf’s Guide but we DON’T want to completely replace our config with that one. Instead we’ll selectively copy in some sections. Edit the file as is:

sudo emacs /etc/apache2/sites-available/default-ssl.conf

Note that we are using https with the defaults and the filename is different to the example.

Find this line:

DocumentRoot /var/www/html

and after it insert this section:

# Overpass API (CGI backend)                                                                          
ScriptAlias /api/ /opt/op/cgi-bin/

<Directory "/opt/op/cgi-bin/">
        AllowOverride None
        Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
        Require all granted

        # CORS for Overpass Turbo                                                                     
        Header always set Access-Control-Allow-Origin "*"
        Header always set Access-Control-Allow-Methods "GET, POST, OPTIONS"
        Header always set Access-Control-Allow-Headers "Content-Type"
</Directory>

# Compression (for API responses)                                                                     
ExtFilterDefine gzip mode=output cmd=/bin/gzip

# Logging                                                                                             
ErrorLog /var/log/apache2/error.log
LogLevel warn
CustomLog /var/log/apache2/access.log combined

# Long-running Overpass queries                                                                       
TimeOut 300

I then deleted a bunch of lines, all comments of functional duplicates of what we had just added, down to but not including:

#   SSL Engine Switch:                                                                                

Save and restart apache:

sudo /etc/init.d/apache2 restart

and check that you can still browse to “https://yourserver.yourdomain”. It won’t look any different as the default website has not been changed; we’ll test the “cgi-bin” parts later.

Compile and Install Overpass

This is drawn directly from ZeLoneWolf’s guide. Note that this does NOT clone the github repository and build it locally. At the time of writing the latest version is “v0.7.62.10” so you’ll see that number below.

sudo su op

cd
wget https://dev.overpass-api.de/releases/osm-3s_latest.tar.gz
tar xvzf osm-3s_latest.tar.gz

cd osm-3s_v0.7.62.10/

time ./configure CXXFLAGS="-O2" --prefix=/opt/op --enable-lz4

That took 5s when I ran it. Next:

time make install

That took 9 minutes. Next:

cp -pr cgi-bin ..
cd
chmod -R 755 cgi-bin
mkdir db
mkdir diff
mkdir log
cp -pr osm-3s_v0.7.62.10/rules db

Those three directories created are for the database, minutely diff files and logfiles. In operation, the biggest by far will be “db” - we’ll expect 2.3GB of .pbf extract to create a database of initially 80GB or so. We’ll talk more about this later.

Loading OSM Data

The equivalent section of ZeLoneWolf’s guide is called “Download the Planet”. We don’t actually want to do that - we just want a data extract for our area of interest.

I’ll download a Geofabrik extract in my normal user account and make sure that it is accessible to the “op” user. Firstly browse to (in may caase) https://download.geofabrik.de/europe/britain-and-ireland.html . There is a link there to https://download.geofabrik.de/europe/britain-and-ireland-latest.osm.pbf anf a comment that says something like “This file was last modified 22 hours ago and contains all OSM data up to 2026-02-12T21:23:29Z”.

When logged in as youruseraccount:

mkdir ~/data
cd ~/data
time wget https://download.geofabrik.de/europe/britain-and-ireland-latest.osm.pbf

I then moved the file so that the filename contained the timestamp

mv britain-and-ireland-latest.osm.pbf britain-and-ireland_2026-02-12T21:23:29Z.osm.pbf

That is a .pbf format download - that format was introduced to OSM around 2010 and is basically pretty standard now. Unfortunately, Overpass still needs the previously used .bz2 format, but we can convert it:

(in screen)
sudo apt install osmium-tool
time osmium cat britain-and-ireland_2026-02-12T21\:23\:29Z.osm.pbf -o britain-and-ireland_2026-02-12T21\:23\:29Z.osm.bz2

That took around 1 hour 20 minutes (and frustratingly the progress bar looks like it was written by someone from Windows 2000) - don’t cancel it if it appears to be stuck, instead have a look to see if it is actually writing out a file. If you want to verify the resulting file:

(in screen)
time bzip2 --test britain-and-ireland_2026-02-12T21\:23\:29Z.osm.bz2 

That took around 11 minutes for me.

Still as youruseraccount, make the download area browsable via the “op” user”::

chmod o+rx ~
chmod o+rx ~/data

If you’re not comfortable with this then you can of couurse copy or more the file as root later.

Configure launch scripts.

This is based on ZeLoneWolf’s guide again, which in turn is using scripts that Kai Johnson wrote.

As the overpass user:

mv bin bin.bak && mkdir bin
git clone --depth=1 https://github.com/ZeLonewolf/better-overpass-scripts.git bin
rm -rf bin/.git

and we’ll need to copy some things from the build into that directory. This will include at least:

cp /opt/op/osm-3s_v0.7.62.10/bin/update_database bin/
cp /opt/op/osm-3s_v0.7.62.10/bin/update_from_dir bin/
cp /opt/op/osm-3s_v0.7.62.10/bin/osm3s_query bin/
cp /opt/op/osm-3s_v0.7.62.10/bin/dispatcher bin/

but I actually copied everything missing from the new “bin” directory. We installed “locate” above. If anything hs been inadvertantly missed you can use e.g. “locate nameofmissingthing” and it will find it. This is a bit messy, and it’d be great to have something that’s a bit more solid and has less of the “porcine face paint applicator” feel to it; but I did not want to go too far down that road as I was trying to set something up “without too much work”.

Change the scripts to work with data extracts and no attic or meta data

We’re going to load a data extract from Geofabrik, and we’d also like to be able to update it with changes as other people update OSM. Normally the workflow that I’d suggest for this sort of thing is to download minutely updates from https://planet.osm.org, use trim_osm.py to snip them down to the area that we’re interested in and then apply those as updates.

By default, Overpass does run with planet.osm.org minutely diffs but alas I’ve struggled to get those to work with a data extrct; the updater falls over when it finds certain sorts of data that it is not expecting (i.e. was never originally loaded) in diff files. However, Geofabrik does provide daily diff files that match their extracts, so we can use those instead.

Also, we’re only interested in “now” data - we’re not creating an Overpass server with “attic” data that allows us to query data from back in 2012.

We therefore have to make a bunch of changes to scripts.

startup.sh

In there, we will change “https://planet.openstreetmap.org/replication/minute” to “https://download.geofabrik.de/europe/britain-and-ireland-updates”.

We’ll change --meta=attic to --meta=no because we’re not doing anything with “attic” data.

We’ll remove the --attic from the “dispatcher” call.

apply_osc_to_db.sh

We’ll change EXPECTED_UPDATE_INTERVAL from 57 to 3557 or even longer. We’re expecting files once a day not once a minute, but checking every hour is not too bad.

log file management

There’s a section in ZeLoneWolf’s guide that covers this.

Log files will eventually grow large and will eventually need a log rotation mechanism to be set up, but let’s gloss over that for now as I’m eager to see Overpass actually running!

Server automation

See ZeLoneWolf’s guide.

I have deliberately not done this yet as I don’t want to automatically do anything; rather I’d like to control it manually so that I can watch that it does what it is supposed to.

Load the data.

(in screen)
time bin/init_osm3s.sh /home/youruseraccount/data/britain-and-ireland_2026-02-12T21\:23\:29Z.osm.bz2 "db/" "./" --meta=no

That took about 77 minutes for me. Lots of files will have been created in “db”. A quick check on disk usage is in order:

df .
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda1      157207480 76407544  74363468  51% /

op@h23:~$ fc du
du -BG db/* | sort -n -r | head
53G     db/nodes.map
9G      db/ways.map
3G      db/ways.bin
3G      db/nodes_meta.bin
3G      db/nodes.bin
2G      db/way_tags_global.bin
2G      db/ways_attic.map
2G      db/nodes_attic.map
1G      db/way_tags_local.bin.idx
1G      db/way_tags_local.bin

It’s worth noting that those are large numbers for an extract. The 2.3GB data extract has created a 53GB nodes.map file. Compression is supported, but I haven’t tested it.

Set up replicate_id

There’s a file in the “db” directory (which will be created if it does not already exist) that determines the place to start consuming diffs from. These vary by server; the number corresponding to planet.osm.org replication from a certain data will different to the one for Geofabrik replication for the same date.

In our example we’re using Geofabrik data from 12th Feb 2026. We can browse through https://download.geofabrik.de/europe/britain-and-ireland-updates/ and https://download.geofabrik.de/europe/britain-and-ireland-updates/000/004/ until we find the immediately prior state file https://download.geofabrik.de/europe/britain-and-ireland-updates/000/004/693.state.txt , which contains sequenceNumber=4693. This means that 4693 is our magic number.

We’ll therefore edit the replicate_id file (creating it if it does not exist) and write 4693 (with a linefeed after) to it.

Before we do anything else, now is a good opportunity for another snapshot.

Start overpass

If this isn’t the first time you’ve started overpass you may want to take backup copies of previous “diff” directories or “log” files. Then:

bin/startup.sh

You should see something like this:

[2026-02-15 12:43:14] INFO: Starting Overpass API components...
[2026-02-15 12:43:14] INFO: Starting base_dispatcher...
[2026-02-15 12:43:14] INFO: Cleaning up stale files...
[2026-02-15 12:43:14] INFO: base_dispatcher is running (PID: 107771)
[2026-02-15 12:43:14] INFO: Starting area_dispatcher...
[2026-02-15 12:43:14] INFO: area_dispatcher is running (PID: 107783)
[2026-02-15 12:43:14] INFO: Starting apply_osc...
[2026-02-15 12:43:14] INFO: apply_osc is running (PID: 107795)
[2026-02-15 12:43:14] INFO: Starting fetch_osc...
[2026-02-15 12:43:14] INFO: fetch_osc is running (PID: 107835)
[2026-02-15 12:43:14] INFO: Performing final verification...
[2026-02-15 12:43:16] INFO: base_dispatcher verified (PID: 107771)
[2026-02-15 12:43:17] INFO: area_dispatcher verified (PID: 107783)
[2026-02-15 12:43:17] INFO: apply_osc verified (PID: 107795)
[2026-02-15 12:43:17] INFO: fetch_osc verified (PID: 107835)
[2026-02-15 12:43:17] INFO: All Overpass components started successfully

[2026-02-15 12:43:17] INFO: === Process Status ===
  base_dispatcher      PID: 107771
  area_dispatcher      PID: 107783
  apply_osc            PID: 107795
  fetch_osc            PID: 107835

In the directories below “diff”, you should see that it has downloaded daily diffs for any days since your extract, for example:

  /opt/op/diff/000/004: (56 GiB available)
  drwxrwxr-x 2 op op    4096 Feb 16 01:07 .
  -rw-rw-r-- 1 op op 3874289 Feb 16 01:07 697.osc.gz
  -rw-rw-r-- 1 op op     113 Feb 16 01:07 697.state.txt
  -rw-rw-r-- 1 op op 3033325 Feb 15 12:43 696.osc.gz
  -rw-rw-r-- 1 op op 3405594 Feb 15 12:43 695.osc.gz
  -rw-rw-r-- 1 op op 3057997 Feb 15 12:43 694.osc.gz
  -rw-rw-r-- 1 op op     113 Feb 15 12:43 695.state.txt
  -rw-rw-r-- 1 op op     113 Feb 15 12:43 696.state.txt
  -rw-rw-r-- 1 op op     113 Feb 15 12:43 694.state.txt
  drwxrwxr-x 3 op op    4096 Feb 15 12:43 ..

In “log” you should see something like:

  /opt/op/log: (56 GiB available)
  -rw-rw-r--  1 op op  12111701 Feb 16 23:39 apply_osc_to_db.out
  drwxr-xr-x 13 op op      4096 Feb 16 20:14 ..
  drwxrwxr-x  2 op op      4096 Feb 15 12:43 .
  -rw-rw-r--  1 op op         0 Feb 15 12:43 osm_base.out
  -rw-rw-r--  1 op op         0 Feb 14 14:26 fetch_osc.out
  -rw-rw-r--  1 op op         0 Feb 14 14:26 areas.out

Testing standalone

At the command line type:

bin/osm3s_query

Paste in this:

<query type="nwr"><bbox-query n="51.96" s="51.86" w="-3.31" e="-3.22"/><has-kv k="amenity" v="pub"/></query><print/>

Press return. Press ^d. A selection of data will be returned.

Testing from Overpass Turbo

In a web browser, browse to https://overpass-turbo.eu/s/2kEW .

Click “settings”. Change “server” from “https://overpass-api.de/api/” to “https://yourserver.yourdomain/api/”. Click “run”. You should not get an error, and should get a couple of nodes and 4 ways returned.

Now what?

Shutting everything down and taking a snapshot of the server is a good idea at this point. The long-term cost of snapshots is small (€0.20 per month or so). The cost of leaving a server of this specification running 24x7 isn’t that large - around €10, perhaps a couple of beers or a couple of fancy coffees.

You might also want to think about setting up an Overpass server that does include metadata and attic data - but you’re probably better off with a dedicated server for that, and better off following one of the other guides linked above.

Lincolnshire ER OUT Routes

Hello! This is my first Diary Entry and I wanted to dedicate it to the Forum Post that I made about the UKs Only (I Believe) ER OUT routes in the case of any emergencies: mainly flooding in this case.

Overview

After major flooding in 2013 the council created the Lincolnshire ER Routes to enable people to quickly evacuate from the flood areas. Many of you make have driven past these and never even noticed! They are Red rectangular signs with the white text of ER out on them with a direction to follow. They are placed at every turn, so the evacuees follow the road ahead until a signs says otherwise.

Example Sign

Route End

The end of the route signifies that the evacuees are clear of the major flood risk and (presumably) there would be further guidance at the end of the route. The route end sign is the same as the direction signs however it features 5 black diagonal lines.

OSM Mapping

In the forum post I have included some proposed tags and along with Insert User who has suggested some changes to the signage.

I will be unable to fully map these routes out as I rarely venture to the south of Lincolnshire. If you live near one of these routes please do help to map these! I presume it will take a while to map all of the routes but I think it will be worth it in the event of any flooding within the region!

Please do not hesitate to contribute to the forum post!

Σε εφαρμογές που “πατάνε” στους Open Street Maps (σίγουρα στις Mapy. OSMand, Organic Maps, ίσως και αλλού), ως E65 εμφανίζεται ΛΑΘΟΣ ο παλιός δρόμος Λαμία-Δομοκός-Φάρσαλα-Λάρισα και όχι ΣΩΣΤΑ ο αυτοκινητόδρομος Θερμοπύλες-Καλαμπάκα (και ημιτελές Βορειότερα ως την συμβολή με την Εγνατία). Ιδίως για τους ξένους ταξιδιώτες είναι μέγα μπέρδεμα.

Die FOSSGIS-Konferenz 2026 findet vom 25.-28. März 2026 in Göttingen und Online statt. Es sind nur noch wenige Wochen bis zur Konferenz. Die Vorfreude wächst stetig und die Vorbereitungen laufen auf Hochtouren!

Die Konferenz wird vom gemeinnützigen FOSSGIS e.V, der OpenStreetMap Community in Kooperation mit dem Geographischen Institut der Georg-August-Universität Göttingen organisiert und findet auf dem Campus der Uni Göttingen statt.

Auch in diesem Jahr zeichnet sich ein großes Interesse an der Konferenz ab. Die Anmeldungen steigen von Woche zu Woche. Zum Glück bietet das Zentrale Hörsaalgebäude der Uni Göttingen ausreichend Platz, so dass es die bisher größte FOSSGIS-Konferenz werden könnte.

FOSSGIS 2026 Programm und Zeitplan

Das FOSSGIS Team freut sich auch in diesem Jahr auf ein spannendes Programm mit zahlreichen Vorträgen, ExpertInnenfragestunden, Demosessions, BoFs und Anwendertreffen und sowie 28 Workshops. Das Konferenzprogramm findet von Mittwoch bis Freitag im Zentralen Hörsaalgebäude (ZHG) der Uni Göttingen statt. Am Samstag finden OSM-Samstag und Community Sprint an der Fakultät für Geowissenschaften und Geographie am Nordcampus statt.

https://www.fossgis-konferenz.de/2026/programm/

Die Konferenz startet in diesem Jahr schon am Dienstag, den 24.03.2026 ab 10 Uhr mit längeren Workshops (180 Minuten). Wählen Sie unter 7 Workshops aus siehe Programm und reisen Sie schon am Dienstag an. Die Workshops sprechen sowohl Einsteiger:innen als auch Fortgeschrittene an, es sind noch Plätze frei. Buchen Sie gerne noch einen Workshop und nutzen Sie die Chance in kurzer Zeit Wissen zu einem Thema aufzubauen.

FOSSGIS vernetzt - Anwendertreffen und Community Sprint

Rund um die und während der Konferenz gibt es zahlreiche Möglichkeiten sich zu vernetzen. Die Pausenversorgung kombiniert mit Firmen-Ausstellung und Poster-Ausstellung finden im Foyer des ZHG statt sowie auch die Abendveranstaltung am ersten Konferenztag. Für die fachliche Vernetzung bieten sich Gelegenheiten bei den Anwendertreffen, Expert:innenfragestunden und weiteren Community Sessions, eine Onlineteilnahme ist möglich. https://www.fossgis-konferenz.de/2026/socialevents/

Reichhaltiges Rahmenprogramm

In diesem Jahr freuen wir uns über ein vielseitiges Rahmenprogramm mit spannenden Exkursionen und Treffen in interessanten Lokationen Göttingens. FOSSGIS steht auch für Netzwerken. Dies ist schon am Dienstagabend möglich. Die Geochicas laden zu einem Treffen ein. Außerdem findet der Inoffizielle Start mit einem gemeinsamen Abendessen (Selbstzahler) statt und heißt alle schon angereisten Konferenzteilnehmenden willkommen.

Alle Informationen finden sich unter https://www.fossgis-konferenz.de/2026/socialevents/

FOSSGIS Konferenz 2026 Sponsoren

Herzlichen Dank an die Sponsoren der Konferenz. die durch Ihre Unterstützung maßgeblich zur Finanzierung der Veranstaltung beitragen. Werden auch Sie FOSSGIS-Sponsor. Wir freuen uns über weitere Unterstützung. Informationen finden Sie unter https://fossgis-konferenz.de/2026/#Sponsoring

FOSSGIS - ein Teamevent

Die FOSSGIS lebt vom ehrenamtlichen Engagement, zahlreiche Helfer:innen bringen sich ein und übernehmen unterschiedlichste Aufgaben vor und während der Konferenz. Herzlichen Dank dafür!

Es werden noch Helfende gesucht, insbesondere für Sessionleitung, Unterstützung im Hörsaal für die Vortragenden sowie beim Catering, siehe https://www.fossgis-konferenz.de/2026/helfen/.

OSM-Samstag und Community Sprint

Am Samstag, den 28.03.2026 werden OSM-Samstag und Community Sprint in den Räumen des Geographischen Instituts in der Goldschmidtstr. 3-5, 37073 Göttingen stattfinden. Die Gelegenheit ins Gespräch zu kommen oder beim Community Sprint sich einzubringen oder Know-How aufzubauen. Jede:r ist herzlich willkommen teilzunehmen, https://pretalx.com/fossgis2026/talk/VVYN7A/.

Informiert rund um die Konferenz

Informationen rund um die FOSSGIS finden sich unter dem Hashtag #FOSSGIS2026. Den Haschtag #FOSSGIS2026 nutzen wir für Informtionen in den Social Media, nutzen sie es auch, um die Social Media Aktivitäten zu verbinden.

Archiv FOSSGIS-Konferenzen

Im FOSSGIS-Archiv finden Sie die Homepages der vergangenen Konferenzen, inkl. Programm und Videos https://fossgis-konferenz.de/liste.html.

Das FOSSGIS Team 2026 wünscht eine gute Anreise und freut sich auf eine spannende Konferenz in Göttingen

05/02/2026-11/02/2026

Mapping

• User AndreaDp271 is seeking comments on their proposal of a tagging scheme for civil protection areas used in case of large scale emergencies. Please review the proposal and share your feedback to help refine the technical details and address any potential issues.
• Voting on the tagging scheme for advisory access restriction signage on destination signs proposal is open until Saturday 21 February.

Mapping campaigns

• Henry Wilkinson has mapped the Dundas West Station in Toronto, Canada, using the LiDAR sensor on an iPhone 17 Pro, in combination with the Niantic Scaniverse app, to capture 3D data. He then reconstructed the digital 3D scene with Meshroom and Blender before uploading the results to OpenStreetMap through JOSM (using the PicLayer plugin) to align imagery, and iD for streamlined indoor tagging. The completed work enabled detailed indoor mapping of the station, now viewable on OpenLevelUp.

Community

• darkonus wrote in their diary about elliptical toponyms (geographical names in which generic terms disappear over time) and explained why it is important for OpenStreetMap mappers to verify the full forms of names. The author examined various cases and focused on Ukrainian microtoponyms, emphasising that abbreviations in sources or in speech do not always indicate a change in the proper name.
• Bart Louwers and others have released the January 2026 edition of the MapLibre Newsletter.
• Matt Whilden has made an Ultra query to create a map that renders the nickname tag of places in OpenStreetMap.

OpenStreetMap Foundation

• Paul Norman reported that the OpenStreetMap Operations Team has recently made several improvements to the tile.openstreetmap.org raster map tile service.
• Minh Nguyễn reported that the OSM Wiki has just switched the CAPTCHA used in the account creation process from hCaptcha to Cloudflare Turnstile, aiming to improve protection against bots.

Local chapter news

• Oliver Rudzick announced ► that FOSSGIS e.V. will once again host the FOSSGIS–OSM Community Meeting at the Linuxhotel in Essen. The event is scheduled for the extended first May weekend, from Thursday 30 April to Sunday 3 May. Additional details are available on the event’s Wiki page.
• OpenStreetMap United States 2026 board candidate nominations closed on 8 February 2026. There are five candidates and you can read their position statements on the Wiki.

Events

• The FOSS4G 2026 organising team announced that the Call for Proposals (closing 16 March) and Travel Grant Programme (closing 28 February) are now open for the global conference to be held in Hiroshima, Japan (30 August to 5 September 2026).
• Developers are invited to register for a free GeoSolutions instructional webinar on the Geonode 5.0 open-source software, a web-based application and platform for developing geospatial information systems and for deploying spatial data infrastructures. The webinar will be held on Tuesday 24 February at 4 pm GMT.
• Recordings of the State of the Map CZ/SK 2025 sessions are available on its Peertube channel. The details can be found ► in the event’s schedule.
• The State of the Map US call for proposals closes on 16 February. OpenStreetMap US invites you to share your presentation ideas. Looking for inspiration? Check out the recorded talks from previous conferences. They also have Mapping USA recordings available.

OSM in action

• Christoph Langner, of Linux und ich, showcased ► Chainlaine, a Brouter-powered bike navigation app on Android.

Software

• ^[1] Martijn van Exel has developed the osm-mapper-globe, a visualisation dashboard that enables users to watch OpenStreetMap edits in real time on an interactive globe. The code is available on Codeberg under an ISC licence.
• Stefan blogged about GraphHopper’s route optimisation API and ‘stop timing’, a new feature accounting for location overhead (the time spent at a stop on a delivery route).

Programming

• Martijn van Exel has developed cosmo, a command-line tool for filtering and converting OSM PBF data into GeoJSON or Parquet formats.

Releases

• The CoMaps team released version 2026.02.09 featuring OSM data from 7 February and automatic updates of the check_date tag when adding/editing POI. Furthermore, the search now supports Scandinavian letters (æøå), on Android you can now disable the speed limit display during car navigation, and on iOS in the EU you can now set CoMaps as your default map app.
• Sarah Hoffmann (aka lonvia) announced enthusiastically that Photon 1.0.0 was released with a lot of improvements in its search engine. She also thanked GraphHopper, Komoot, and Entur for their continued support of Photon development, which has made this release possible.

Did you know that …

• … the Academic Computer Club, at Umeå University, and the Oregon State University Open Source Lab contribute to OpenStreetMap by hosting tile render servers? If you also want to help OpenStreetMap run a tile server in your region, check this guide.
• … according to OpenStreetMap’s tile usage policy, it is recommended to include a ‘Report a map issue‘ link, so your app users can help improve the data?
• … Séverin Ménard (Les Libres Géographes) gave a keynote titled Le numérique, vecteur d’une appropriation collective des données environnementales? It was part of the Cycle Annuel 2025, helded by the Institut des hautes études d’aménagement des territoires. He showed the application of open and collaborative data and detailed the mapping carried out in Mayotte. The explanation of this mapping effort was published in the weeklyOSM issues 770 and 775.
• … the General Bikeshare Feed Specification (GBFS) has used the OpenStreetMap opening_hours format since version 3.0? GBFS is an open data standard designed to make it easier to discover and use shared mobility services.
• … the statistics of uMap instances are also published as a chart?

OSM in the media

• Historian Arseniy Chuhuy outlined how place names in Crimea changed during the imperial and Soviet periods and described efforts to restore historical, especially Crimean Tatar, toponyms. He also noted practical issues in the process, including duplicate names and settlements without clearly documented historical alternatives. The article is illustrated with a map by Ukrainian OpenStreetMap contributor and cartographic designer Fedir Gontsa.

Other “geo” things

• The Editora IVIDES is accepting ► applications for the selection process to form the scientific committee for volumes 2 and 3 of the series Case studies in collaborative and participatory mapping (in Portuguese). Raquel Dezidério Souto, editor of the series, reported ► in her OSM user diary that the first volume was released in August 2025 and has already been downloaded by over a thousand people.
• The Government of Portugal has published ► a list of municipalities affected by Storm Kristin that are now under a state of public calamity. A humanitarian mapping effort is emerging, and you can learn more about this and other topics by following the Portuguese OpenStreetMap community group on Telegram and Discord.
• The UCL Warning Research Centre invites you to their free and hybrid launch of the UCL Warning Database, which will occur on 4 March, from 3 pm to 4 pm GMT, at Room 225, Central House, Bloomsbury.
• Miguel Alvarez has taken a look at the maps of Leonardo da Vinci. Further detail of Leonardo’s mapping career can be found in Christopher Tyler’s 2017 article.
• Will Dunham wrote in The Japan Times about radar data which shows a cavernous underground lava tube on Venus. Lava tubes are also found in certain volcanic locations on Earth and its moon and are believed to be present on Mars.
• Melinda Laituri, of Colorado State University, discussed women’s contributions to cartography. We previously reported ► that Daniel Meßner had highlighted the American geologist and cartographer Marie Tharp and her contribution to the cartographic depiction of the Mid-Atlantic Ridge.

Upcoming Events

Country	Where	Venue	What	When
	Delhi	Dosa Coffee, Model Town	ILUGD Meetup × OSM Delhi Mapping Party No.26 (North Zone)	2026-02-15
	Lancaster	Lancaster University Welcome center 1	Lancaster FoMSF Mapathon	2026-02-16
		EPN d’Arlon, rue de Diekirch 37, Arlon	EPN d’Arlon – OpenStreetMap – Contribution	2026-02-17
	Milano	Building 3A Ground Floor – Politecnico di Milano	PoliMappers Maptedì	2026-02-17
			Missing Maps London: (Online) Mid-Month Mapathon [eng]	2026-02-17
		Online	Mappy Hour OSM España	2026-02-17
	Lyon	Tubà	Réunion du groupe local de Lyon	2026-02-17
	Bonn	Dotty’s	197. OSM-Stammtisch Bonn	2026-02-17
	San Jose	Online	South Bay Map Night	2026-02-17
		Online	Lüneburger Mappertreffen (online)	2026-02-17
		MJC de Vienne	Réunion des contributeurs de Vienne (38)	2026-02-18
	Karlsruhe	Chiang Mai	Stammtisch Karlsruhe	2026-02-18
	Bratislava	Prírodovedecká fakulta UK Bratislava	Missing Maps mapathon Bratislava #12	2026-02-19
			OSMF Engineering Working Group meeting	2026-02-20
	Karlsruhe	Geofabrik, Amalienstraße 44, 76133 Karlsruhe	Karlsruhe Hack Weekend February 2026	2026-02-21 – 2026-02-22
	Belfast	School of Geosciences, Queen’s University Belfast	Belfast Mapathon	2026-02-21
		TAK Kadıköy Tasarım Atölyesi	OpenStreetMap Outdoor Editing	2026-02-21
	Kalyani Nagar	TomTom Pune Office, India	OSM Mapping Party at TomTom Pune, India	2026-02-21
		Atelier Vélo Utile	Rencontre OSM Saint-Brieuc	2026-02-21
	Toulouse	Artilect – 10, Rue Tripière – Toulouse	Rencontre OSM Toulouse	2026-02-21
	Mumbai	Third Wave Coffee Roasters, Lokhandwala Market	OSM Mumbai Mapping Party No.7 (Western Line – South)	2026-02-22
			Missing Maps : Mapathon en ligne – CartONG [fr]	2026-02-23
	Olomouc	Přírodovědecká fakulta Univerzity Palackého	Únorový olomoucký mapathon	2026-02-24
	City of Edinburgh	Guildford Arms, Edinburgh	OSM Edinburgh pub meetup	2026-02-24
	Derby	The Brunswick, Railway Terrace, Derby	East Midlands pub meet-up	2026-02-24
	Hannover	Kuriosum	OSM-Stammtisch Hannover	2026-02-25
	Luxembourg	neimënster, Luxembourg & online	MSF Luxembourg hybrid Mapathon	2026-02-25
	Düsseldorf	Online bei https://meet.jit.si/OSM-DUS-2026	Düsseldorfer OpenStreetMap-Treffen (online)	2026-02-25
	Seattle	Seattle, WA, US	OpenThePaths 2026: Connecting People and Places Through Sustainable Access	2026-02-26 – 2026-02-27
	Santa Clara	Santa Clara University	Friends of MSF Mapathon	2026-02-26
		Online	Asamblea General Ordinaria – Asociación OpenStreetMap España	2026-02-26
	Ferrara	Cimitero monumentale della Certosa di Ferrara	Ferrara mapping party	2026-02-28
	Messina	Messina	Mapping Day @ Messina	2026-02-28
	नई दिल्ली	Jitsi Meet (online)	OSM India – Monthly Online Mapathon	2026-03-01
	Chennai Corporation		Mapping Party @ Chennai	2026-03-01

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 IVIDES.org, MatthiasMatthias, Raquel Dezidério Souto, Strubbl, Andrew Davidson, barefootstache, darkonus, derFred, giopera, jcr83.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

多言語表記のタグ付けを考える

2026-02-01に’さくらインターネット Blooming Camp’で行われた「マッパーズサミット2026」での発表内容です

パート１: OSMの基礎知識編

発表内容のうち、OSM wikiに記載されている項目の解説を「OSMの基礎知識編」します

「基礎知識」と思ってバカにしないでください。日本の編集のほとんどすべて（９９％以上）がOSM wikiに記載事項に違反しています
また、’talk-ja’などでの意見も OSM wikiに記載事項を理解されていないと思われるものが多いです

実例を使って交差点のタグ付けを考えて見ましょう。

ちなみに、この例は私の自宅近くにある交差点で一般的なものです、特殊な例ではありません。

• 交差点なので junction=yes とします。

案内板に表示されている「虚空蔵橋際」をタグ付けします

• 「虚空蔵橋際」をそのまま name = 虚空蔵橋際 とします。

アルファベット表記になっている部分をタグ付けします

この部分は @国土交通省では「国際化に対応する・・・」とされています

• 国際化表記部分なので int_name = Kokuzobashi とします

この部分は @国土交通省では「ローマ字表記」とされていますが、「英語」と「ローマ字」が混じった表記とされています

• 「英語/ローマ字」の判断が必要です → 「bashi」となっているので「ローマ字表記」と考えられます name:ja-Latn = Kokuzobashi とします

案内標識のローマ字表記は「長音」が省略されています。 OSMwiki では’省略してはいけない’ことになっているので「省略された長音」を補完します

• name:ja-Latn = Kokuzō-bashi とします
  • 「省略しない」@wiki/JA:名称#略称
  • 「name:ja-Latnのローマ字表記にはūやōなどのマクロン付きの文字を使用する」@wiki/JA:Japan_tagging#地名の入力規則

[OSM wiki]には「現地語名称は言語明示サブキーと重複させてください」とあります

• 日本では現地語名称は「日本語」なので name:ja = 虚空蔵橋際 を追加します
  • 「現地語名称は言語明示サブキーと重複させてください 」@wiki/JA:多国語の名称#言語明示タグによる複数回の名前付け

案内標識のローマ字表記は”省略”されています。 OSMwiki では’省略してはいけない’ことになっているので「省略された部分」を補完します

この例では「際」が省略されています

• name:ja-Latn = Kokuzō-bashi-giwa とします
  • 「略称は使用しないでください」@wiki/JA:名称#略称

osmwiki/JA:名称に「特定の言語での名前（name:en=…）の使用を検討してください」とありますので、int_name に対応する name:en の使用を検討します

• 「特定の言語での名前（name:en=…）の使用を検討してください」@osmwiki/JA:名称

name:ja-Latn と同様に、name:enについても省略された「長音」と「省略部分」を補完します

• name:en = Kokuzoh bridge side とします
  • 「特定の言語での名前（name:en=…）の使用を検討してください」@wiki/JA:名称#名称キー int_name
  • 「略称は使用しないでください」@wiki/JA:名称#略称

name:en,name:ja,name:ja-Latn は一致させる必要があります。つまり int_nameからname:enを作るのではなく、nameからname:enを作ります

• 「name=虚空蔵橋際」の「虚空蔵橋」は「ごくぞうばし」と読むので name:en = Gokuzoh bridge side とします

ここで「ローマ字表記」部分が変更された場合を考えてみます

• 案内標識のローマ字表記部分が「Gokuzou Bridge」に変更された場合は、int_name = Gokuzou Bridge に変更します。
• name:en,name:ja-Latnを変更する必要はありません
  • 平成26年に発令された「改正標識令」により、2026年現在で約60％の「ローマ字表記」部分が変更されました。残りの40％程度が今後変更される可能性があります。
  • 令和７年に「内閣告示」が改定されましたので、またローマ字表記が変更されることが予想されます

@osmwiki:多国語の名称には、「存在しないものには名称をタグ付けしないでください。」「その他すべての言語に対して name: タグをつけるべきではありません!」とあります

• 有名な「渋谷交差点」を見てみましょう。name:en以外の16カ国語が設定されています。
  • 「[その他すべての言語に対して name: タグをつけるべきではありません](osm.wiki/JA:%E5%A4%9A%E5%9B%BD%E8%AA%9E%E3%81%AE%E5%90%8D%E7%A7%B0)」というOSM wiki の規定に違反した状態になっています

osmwikiに「存在しないものには名称をタグ付けしないでください」とあるにも関わらず、@osmwiki:名称には「特定の言語での名前（name:en=…）の使用を検討してください」と矛盾した記述があります

name:enが特別扱いされる理由は,フォールバックした言語で現地語の名称を表示する場合に、目的の言語が存在しないときは’英語の名称’を表示するためです

つまり、name:enはレンダリングのためのタグ付けということになります

• 「存在しないものには名称をタグ付けしないでください」@osmwiki:多国語の名称
• 「特定の言語での名前（name:en=…）の使用を検討してください」@osmwiki:名称には
• 「[フォールバックした言語で現地語の名称を表示する場合に英語の名称を表示」@JA:多国語の名称#理由

『name:enはレンダリングのためのタグ付け』というのはOSMの原則に反することになります

そのため、「特定の言語での名前（name:en=…）の使用を検討してください」というOSMwikiの基準に矛盾する記載が OSM wiki に多く見られます。

• 「”名前に複数の言語タグが付けられている場合”に注意してください。名前が1つの言語のみでタグ付けされ、今後もその状態が続くと予想される場合、この方法のメリットは大幅に小さくなり、めったに行われません。また、この方法は議論の余地があります。特に単一言語地域では顕著です。@wiki/JA:多国語の名称
• 「存在しないものには名称をタグ付けしないでください」 @wiki/JA:多国語の名称#言語明示タグによる複数回の名前付け
• 「翻訳は回避すべき」@wiki/JA:多国語の名称#課題
• 「通常の綴り規則から逸脱していても、標識にある通りに入力します」@[wiki/JA:名称#良いやり方](](osm.wiki/JA:%E5%90%8D%E7%A7%B0#%E8%89%AF%E3%81%84%E3%82%84%E3%82%8A%E6%96%B9)
• 「標識のような地物の名前を示すものがあるときに限って、名前をタグ付けすべきです」@wiki/JA:名称#名称で説明しない

ここまでのタグ付けをまとめてみましょう

name と int_name は、標識に記載された内容をそのまま設定している

しかし、name:ja以外の name:en,name:ja-Latnは、マッパーの思考・嗜好が反映されたものとなっています

立場をかえて、日本人である私達は、USAの「ゴールデンゲートブリッジ」のことを「金門橋」と呼んでいます

このことをOSMに入力することはできるのでしょうか？

• ‘リレーション: Golden Gate Bridge‘に、name:ja = 金門橋 をタグ付けすることは、OSM wikiに明確に否定されています
  • 「存在しないものには名称をタグ付けしないでください」 @wiki/JA:多国語の名称#言語明示タグによる複数回の名前付け
  • 「翻訳は回避すべき」@wiki/JA:多国語の名称#課題
  • 「通常の綴り規則から逸脱していても、標識にある通りに入力します」@wiki/JA:名称#良いやり方
  • 「標識のような地物の名前を示すものがあるときに限って、名前をタグ付けすべきです」@wiki/JA:名称#名称で説明しない

では、「金門橋」のような現地に表示が情報はどうすればよいのでしょう？

それは、wikidataと連携させて間接的にOSMに反映させることができます

• wikidataの「ゴールデンゲートブリッジ」に、「金門橋」を入力します
• OSMの’リレーション: Golden Gate Bridge‘に、wikidata=Q44440 として、Wikidataとリンクさせます

wikidataとのリンクで ‘name:XX’ が無効化

wikidataとリンクすると、iDエディタでは ‘name:XX’ がグレーアウトして ‘name:XX’が編集できなくなることに注目してください。

wikidata と OSM では扱うデータが住み分けられています。

• wikidata :
  公開された文献(Webデータを含む)に記載された情報
• openstreetmap :
  現地の事実情報(位置情報を持つものに限る)

つまり、nameやint_nameは現地の事実情報なので
- –> OpenStreetMapに入力(OSM wikiでも推奨しています)

いっぽう、name:XX は、現地に表記されていない情報なので
- –> Wikidata は、公開情報に記載があれば入力できる - –> OpenStreetMapに入力できない(OSM wikiでも現地に表記のないデータは入力しないことになっています)

POIが wikidata とリンクした時点で、OSMのデータとしては不適切なname:XX は、用無しとなります
以後、name:XXを編集することは意味がありませんし、name:XXはゴミデータになります

もし、’wikidata’は 『’wikipedia’のようなもの』と認識しているのでしたら、それは間違いです。
‘wikidata’は、’wikipedia’よりも『’OpenStreetMap’のようなもの』と認識したほうが正しいです。

‘wikipedia’と’OpenStreetMap’は、互いに補完しあうことでデータの一貫性を担保することができるようになっています。
また、そのための仕組みや強力なツールも整備されています

• wiki/JA:Wikidataには 「wikidataとのリンク」の重要性が説明されています
  • 1 なぜウィキデータにリンクするのか？
    • 1.1 ウィキデータはウィキペディアではない
  • 2 OSMからウィキデータへのリンク
    • 2.1 タグの修飾子として
    • 2.2 ツール
      • 2.2.1 OSM要素にウィキデータをリンクする
      • 2.2.2 検証ツール
      • 2.2.3 品質保証
    • 2.3 ウィキデータのユーザースクリプト
  • 3 ウィキデータからOSMへのリンク
    • 3.1 ウィキデータにおけるOpenStreetMap関連のプロパティ
    • 3.2 OSMタグとキー

ライセンス上の理由により、OSMのデータをwikidataへコピーすることは禁止されています

• そもそもOSMには、現地に存在する事実情報しかないはずなので、文献データを扱うwikidataへコピーする情報などないはず・・・

ライセンス上の理由により、’wikidata’のデータをOSMへコピーすることは禁止されています

• そもそもwikidataには、文献情報しかないはずなので 現地の事実情報を扱う OSMへコピーする情報などないはず・・・

OSMのマッピングをはじめて、今日で継続年数1年たった。

アカウント自体は5年前に作っていたが、
当時は県道沿いに建物は張り付いてた分しかなくて（うるおぼえ）、
かつて住んでたところくらいはと、3町分の建物を描いたところで、飽きてしまい辞めた。

そして去年の今日、たまたまマップを見てみたら、建物やPOIがかなり充実してたのを見て再燃し、今に至る。

今のところ、熱は冷めてない。
個人的に継続中の調査テーマもあるし、描きたいものもたくさんある。
続けていくつもりなら、いずれはデータを活用する側にも回りたい。
そのためにもマッピングを進めていこうと思う。

オレはようやくのぼりはじめたばかりだからな
このはてしなく遠いマッピング坂をよ……

大阪市の中心付近に、信号停止線に「一時停止」タグがつけられた箇所がたくさんあります。

「一時停止」標識が存在しない場所なので、誤ったタグ付けなのですが、交点に信号機があるだけの状態よりも優れたマッピングです。

しかし、このままでは、初心者マッパーに「誤りだから・・」という理由で単純に削除されてしまう恐れがあります。

改善編集

「osmwiki JA:Tag:highway=traffic_signals」で推奨されている「highway=traffic_signals」に書き換えましょう！

• 信号停止線にある「highway=stop」タグを「highway=traffic_signals」に書き換えます。
• 交差点の交点にあった「highway=traffic_signals」を「junction=yes」に書き換える

Today I covered a slice through the Northumberland Coalfield. Starting in Newbiggin-on-sea, riding through Ashington to Pegswood then returning through Bothal and Woodhorn to Newbiggin. 

NCN 155 runs from Newbiggin-on-sea to Morpeth. The whole route is less than 8 miles long, but I only followed it for about 5 miles, as far as Pegswood. That section is pretty flat. The only real challenge is following twists and turns through Ashington. On the route back, for variety, I deviated from NCN 155 to visit Bothal then Woodhorn.

Newbiggin-on-sea has history as a fishing port and colliery town but today it mainly has the character of a small seaside resort Today was a sunny Saturday. It followed what feels like endless days of rain. Despite the cold, lots of people were out. Newbiggin-on-sea claims to have the longest promenade in Northumberland and it was buzzing with activity.

A short section of NCN 155 took me to Ashington. Until the 1840s Ashington was a tiny hamlet. But it lies above several layers of coal seams. In the second half of the 19th century the Duke of Portland built housing to attract people to come and work at his multiple local collieries. Ashington expanded rapidly to become the "world's largest pit village". The coal industry declined rapidly in the 1970's and 80's but the long parallel rows of colliery housing remain. The loss of employment hit the town hard, and parts still show the scars. But former industrial land has been reclaimed, private housing has expanded. Ashington station reopened to passenger services at the end of 2024. It feels as though a different town is emerging.

Next, on to Pegswood. This is a small pit village, with a similar history of growth, decline and recent regeneration. Perhaps the most striking feature is this sculpture, officially called 'Fire', but also known as "Robin of Pegswood", it depicts a bronze figure on a steel girder firing a miner's shovel as though it was a bow and arrow. The landowner, Welbeck Estates, has associations with Nottingham. Hence the link to Robin Hood.

It's a steep climb out of Bothal, but there's no shame in pushing. On to Woodhorn, where the colliery closed in 1981. The site is now home to Northumberland Archives and the Woodhorn Museum which depicts the work and lives of local mining families, and art created by the Ashington Group of painters. The pithead gear is currently covered in scaffolding as repair works start thanks to a grant from Historic England of almost £1million. I would have liked to take a closer look but I wasn't prepared to pay the entrace fees. So I pressed on to Newbiggin-on-Sea, where I pootled around the back streets, doing a bit of exploring before calling it a day.

The weather was cold, but not too cold. There's still a lot of water on the fields and some on the roads, including one quite exciting splash though a deep flood. However, today's blue sky was a very welcome change. Total distance covered was just over 15 miles.

Purpose

Safe Routes to School is a program designed to help parents encourage their children to walk and bike to school safely, while promoting healthy engagement. In some locations, walking or biking to school is a child’s only means of getting to school. My goal is to help parents find the best routes to school and to assist them in working with local governments to improve safety. But we need more volunteers to help improve the data.

What We’re Building

• Pedestrian and bike maps
• Child-safe routing opetions
• Walking and biking isochrone (walkshed) tools
• Clear tutorials on how to map for pedestrians and cyclists
• Tools SRTS groups can use in their local communities

Pedestrian and bike maps

Bike maps already exist. Not only does OSM offer two different map layers for cyclists, but there are several apps available. Pedestrian maps are a different story. While there are some pedestrian maps, such as the University of Washington’s Taskar Center for Accessible Technology’s AccessMap.app, they are limited. What is needed is a tool that parents can use to find a good walking route to school, as well as a tool that can help improve pedestrian mapping, much like OpenStreetMap US’s OpenTrailMap.us. The rendering should show pedestrian ways, crossings, accessibility features like tactile pads and kerb ramps.

Routing Engines

OSM has some great routing engines. The user interface will likely need to be improved so that features can be added to avoid. For example, railways may be dangerous for children to cross. By allowing the addition of features to be avoid, it’s possible to provide a safe route.

Walking and biking Isochrones (Walksheds)

Good open-source isochrone maps are available. One of my favorites is Valhalla. Below is an example of an isochrone map of a local elementary school created using Valhalla in QGIS. It shows 5, 10, and 15 minute walk areas. However, there are two major problems with the isochrone. First, it uses streets with no sidewalks. It also crosses the Division Street Bridge, which the school district doesn’t feel is safe for children to cross. If we add an isochrones feature to our pedestrian and bike map, it needs to be able to restrict the isochrones to only safe walking and biking routes.

Mapping for pedestrians and cyclists

Four main features need to be mapped: schools, pedestrian ways, cycleways, and traffic calming features. A how-to page, along with video tutorials are needed to help new mappers get started.

Schools’ buildings, parking, bus drop off areas, main entrance, and bike racks need to be mapped. Emphasis needs to be placed on adding accessibility features for kids with disabilities. See https://wiki.openstreetmap.org/wiki/Disabilities

The OSM US Pedestrian Working Group has developed a schema for mapping pedestrian ways. Footways, curb ramps, tactile pads, crossings, surface, width, and other features needed to be mapped. I should note that the schema focuses on mapping sidewalks as separate ways, which is not universally accepted. My experience is that mapping sidewalks as a separate way produces better routing.

Bike mapping is well established in OSM. For SRTS, intersection details, like traffic signal mapping is important for the safety of the children.

Traffic calming features, such as speed bumps, traffic islands, choker points, etc, are used to slow vehicle speeds, making walking and biking safer. Additionally, highway classifications and speed limits on roads are needed to help pick safer streets for children to walk or bike to school.

Volunteers Wanted

The project needs your help in bring together the tools needed for parents to find safe routes to school. Below is an incomplete list of what is needed. If you are interested in helping, leave a message below, or join our #safe-routes-to-school channel on the OSM US Slack.

• Tutorial to map sidewalks
• tutorial to map bike routes
• Turorial to map traffic calming features
• Create a background layer to assist mappers add and update pedestrian features
• Making sure that routers (Valhalla, OSRM, GraphHopper) can handle exceptions (next phase)
• Create an isochrone layer for use with the pedestrian layer (later phase)

Final thought

Not only is mapping for SRTS important in helping parents get their kids to school safely, but it also helps document areas that need safety improvements. While local governments typically have a detailed inventory of cycleways, sidewalks, curbs, and roads, they may not have put it together in one source like we do in OSM.

Links:

Safe Routes: National Center for Safe Routes to School https://www.saferoutesinfo.org/

Federal Highway Administration’s Guidance for the Safe Routes to School Program website: https://www.fhwa.dot.gov/environment/safe_routes_to_school/guidance/#toc123542171

Safe Routes Partnership website: https://saferoutespartnership.org/

Washington State Department of Transportation website: https://wsdot.wa.gov/business-wsdot/support-local-programs/funding-programs/safe-routes-school-program

Seattle PDF: https://www.seattle.gov/documents/Departments/SDOT/SRTS/SeattleSafeRoutestoSchoolEngineeringToolkit.pdf

Washington Safe Routes to School Network website: https://www.washingtonsaferoutes.org/

About 99% of supplements have garbage in them like seed oils, starch, citric acid or other fillers because most people are too ignorant to read the ingredients labels, let alone realize that ultra-processed pseudo-food is harmful for them in the first place.

I wonder if there is some tag for a nutrition supplements store to state that they offer clean supplements with just one ingredient, just like vegetarian tags, except focused on health rather than ethics.

Maybe diet:raw=* could somewhat apply?

县道、乡道、村道的编号规则是什么？ 答：1.县道命名及编号规则：

（1）命名规则：以起终点行政节点名称第一个汉字加“线”组成，如起于高淳县东坝镇终于高淳县固城镇，则命名“东固线”；如起终点为非行政节点，则以起终点具代表性的名称第一个汉字加“线”组成。

（2）编号规则：本轮县道网编号以现有编号体系为基础，现有县道编号基本保持不变，新增县道编号按照方向和类型，在现有县道编号后依次排列，即“老路老编号、新路新编号”。具体编号原则如下：

①编号由字母和数字共10位构成，如“X105320125”，其中，“X”反映县道的性质；“105”反映线路的类型、方向和顺序；“320125”为线路所在县（市、区）的行政代码（以国家统计局发布的2013年江苏省行政区划代码为准）。

②例：“105”：第一位“1”表示线路方向和类型，“05”表示为顺序码。

“1”开头表示由县城（市、区）向外辐射的树状县道网，顺序码从正北方向顺时针依次增大；

“2”开头表示南北纵向县道编号，顺序码从东向西依次增大；

“3”开头表示东西横向县道编号，顺序码从北向南依次增大；

其中，“101~150”、“201~250”、“301~350”编号，适用于保留、局部延伸或调整的现有县道线路，原有县道线路编号不做调整；“151~199”、“251~299”、“351~399”编号，适用于本轮新增县道和上轮县道规划后陆续增编的临时县道编号线路（即X+字母+两位数字+行政区划代码的线路）。

2.乡道命名及编号规则：

（1）命名规则：以起终点行政节点名称第一个汉字加“线”组成，如起于溧水区晶桥镇止于溧水区晶桥镇新山里村，则命名“晶新线”；如起终点为非行政节点，则以起终点具代表性的名称第一个汉字加“线”组成。以上两种命名规则，必须保证在同一县域范围内名字不重复。

（2）编号规则：路线编码由行政等级代码+三位编号+县级行政区划代码共十位组成，具体表示方法如下所示：

“Y”：代表乡道的行政等级代码；“101”：代表乡道的排列顺序编码，采用“老路老编码，新路新编码”原则，老线路以及延伸段采用原有编码，新线路编码从“AA0”开始至“ZZ9”；“320111”：代表该县（市、区）的行政代码。

县（市、区）交通运输局根据各乡镇的实际情况拆分乡道编码，确保县（市、区）域范围内乡道编码的唯一性。

3.村道公路命名及编号规则：

（1）命名规则：以起终点行政节点名称第一个汉字加“路”组成，如：起于溧阳市上兴镇建盟村，终于溧阳市上兴镇红旗村，则命名“建红路”；如起终点为非行政节点，则以起终点具代表性的名称第一个汉字加“路”组成。以上两种命名规则，必须保证在同一县（市、区）域范围内名字不重复。

（2）编号规则：路线编码由行政等级代码+三位编号+县级行政区划代码共十位组成，具体表示方法如下所示：

“C”：代表村道的行政等级代码；“101”：代表村道的排列顺序，采用“老路老编码，新路新编码”原则，老线路以及延伸段采用原有编码，新线路编码从“AA0”开始至“ZZ9”；“320125”：代表该县（市、区）的行政区划代码。

县（市、区）交通运输局根据各乡镇的实际情况拆分村道编码，确保县（市、区）域范围内村道编码的唯一性。

We are happy to announce the release of Photon 1.0.0. With its first major release Photon fully switches to OpenSearch, sees a lot of improvements in performance and gets some new features on the query side.

This release marks a major milestone in the journey to make Photon a more efficient and flexible geocoder. Over the last year the code has seen a lot of modernization. We are moving away from being a simple search front end to Nominatim, towards becoming a fully featured geocoder where OpenStreetMap data can be one of many sources.

Here are the most important highlights for this 1.0 release:

Streamlined database structure

Photon’s internal database structure has been streamlined. Any metrics that are not relevant for the geocoding problem have been dropped. We’ve also dropped all language-specific indexes. Using those has slowed down queries for very little gain in accuracy.

Altogether the database is now about half the size than a 0.7 database. A planet needs about 95GB of disk space as of early 2026.

Revamped CLI

Over the years Photon has collected quite a few command-line options to tweak the import and the operation of the server. To bring a bit of order into this mess, the command-line is now organised in git-style subcommands for import, update and serving. You can ask for help for each of the commands with the ‘-h’ parameter and will get a more compact response with parameters neatly organised in groups. Have a look at the new usage documentation to learn more about the available commands.

The changes to the CLI are backwards-compatible. When no command is given then Photon will fall back to the old-style command-line parameters. This will give everybody some time to adapt their scripts to the new layout. But don’t wait too long. The old-style parsing will be removed with the next major version.

New query features

The /structured endpoint, which was optional in previous releases, is now available by default and can be used together with the database dumps from the export server. Be aware though that structured search is still somewhat new and little tested. You are welcome to provide feedback on the Github discussion page.

Version 1.0 newly introduces categories. These are custom tags that can be added to the import data and can then be used for filtering queries. This is much more powerful than the current layer and osm-tag filters. In fact, categories will replace the osm-tag filters eventually. There are currently special categories included except for a category that represents the OSM main tag. So this is mainly something you can use right now when customizing your data to create a specialised search engine.

Finally, there is a new dedupe parameter which switches off the internal result deduplication. This can for example be useful when a street is cut into many sections in OSM and you would like to get all sections instead of just one representative.

JSON import and export

Version 0.7 already introduced an experimental feature for exporting to and importing from JSON dumps. With version 1.0 we have finalized the format and published the official specification. JSON dumps of the OSM planet and selected abstracts are available on the export server. Use them to filter and adapt the data before importing into Photon, to create databases with custom settings (like additional languages) or add your own custom data. We are looking forward to hear what you are doing with this new feature.

Server metrics

If you are running Photon in a production environment that is monitored by prometheus, then the server is now able to export internal metrics like number of queries and query duration or memory usage. The endpoint isn’t enabled by the default, you need to switch it on when starting the server.

With this major release, Photon will switch to a more conventional use of the semantic versioning schema. From now on, patch releases will only bring bug fixes and dependency updates. Minor releases may contain new features or change existing ones trying to maintain backwards compatibility. Major releases are reserved for breaking changes in functionality and for changes that require a database reimport. We have a few ideas for more major changes to come, so don’t expect another 12 years to pass before Photon 2.0.

Many thanks to Graphhopper, Komoot and Entur for their continued support of Photon development, which has made this release possible.

Вітаю, спадарства!

Неўзабаве скончыў перакладаць openstreetmap на клясычную (тарашкевіцу).

Спроба сыстэматызаваць тое што было, пасьлядоўна ды ґрунтоўна прайшоўся водле працы якую пачалі ўжо даўно. Пэўныя тэрміны, магчыма, будуць незразумелымі ці нязвыклымі, мэтай была ўжываць нашыя спрадвечныя адменьнікі, унікаючы калькаваньня.

Цяпер патрэбная вычытка, прыбраць хібу, якую я мог дапусьціць.

Пераклад ужо бачны на сайце, каб пабачыць трэба выбраць мову, яна ніжэй, пад “беларуская”. Перакладзены толькі сайт, не id-рэдактар, там нашмат болей працы, і іншы пляц для перакладу, не такі зручны як translatewiki.

OPORTUNIDADE PARA PARTICIPAR DE PUBLICAÇÃO CIENTÍFICA ABERTA

Portuguese only

A Editora IVIDES está com inscrições abertas para processo seletivo que visa à composição do comitê científico dos volumes 2 e 3 da série Estudos de caso em mapeamentos colaborativo e participativo. O primeiro volume da série, lançado em 2025, já conta com mais de mil downloads! Os documentos informativos desta seleção estão disponíveis:

🡇 Chamada pública para o comitê científico - Critérios

🡇 Convite para o comitê científico

✻ O prazo para envio das candidaturas é:

20 de fevereiro de 2026, 17h (UTC-3, hora de Brasília)

✍ Formulário de inscrição

✻ Os resultados serão comunicados até 23 de fevereiro de 2026, 23h59 (UTC-3, hora de Brasília), via e-mail informado pelo candidato;

✻ Chamada para residentes em países lusófonos;

✻ Parte dos capítulos inclui OpenStreetMap, aproveite para contribuir e enriqueça o seu currículo como parecerista.

For a while, I was interested in understanding what makes one pedestrian OSM way better than another. I wanted to know if there is some generic way to identify good walking routes from OSM data. I looked at Garmin and Strava heatmaps at first. Then I checked Strava segments and their proximity to points of interest such as rivers, ponds, and parks. Then I thought to look at my running pace along OSM ways to separate good and not-so-good walking routes. My idea was simple — a good walking route means a smooth running pace. There are fewer stops, less waiting at intersections, etc. Of course, my pace depends on many factors, such as how far I have to run to get to a certain place. So it cannot be a simple cutoff, but rather the distribution of paces along a given segment. This turned out to be a reasonably good approximation of how good or bad I perceive each route to be. I created this Kaggle dataset as an illustration. This relies on my personal GPX data, so it does not scale, but it captures the kind of local knowledge that I find hard to share in any other way.

Banjar

• SD Negeri - ALL DONE
• SD Swasta - ALL DONE

Pataruman

• Pataruman
  • Negeri 1-5 - ALL DONE
  • Swasta
• Binangun
  • Negeri 1-2 - ALL DONE
  • Swasta

Purwaharja

• SD Negeri - ALL DONE
• SD Swasta - Empty

Langensari

I mainly edit OSM based on GPX files from my runs. I use JOSM. I created a simple script to extract a buffered area around my GPX files to make sure I don’t accidentally edit parts of OSM I don’t intend to. See this Github Gist for the source.

Hello! I’m Quincy Morgan. Thank you for considering my candidacy for the board of directors of OpenStreetMap US.

If we haven’t met before, or if you just want to chat about OSM, I encourage you to reach out via OSM, Slack, email, or social media. You can check out my website for detailed information about me, my work, and more ways to contact me.

About

I have been an avid member of the OpenStreetMap community since 2018 in both volunteer and professional capacities. I am the only person to have been employed by both OpenStreetMap US and the OpenStreetMap Foundation. Recently I have organized my activities under Wayside Mapping.

Mapping

As a volunteer mapper, I’ve contributed more than 13,000 changesets over the span of 1,400 mapping days, including more than 3,000 changesets in the past year. My mapping interests are varied but include trails, waterways, peninsulas, scenic routes, monitoring stations, and undermapped places.

Development

As a paid and volunteer open source developer, I have made major contributions to OpenStreetMap tools such as iD, Field Papers, OpenTrailMap, and the openstreetmap.us website. Most recently, I have built and launched themap.is and OSM 411 on my own time.

Life

I’m currently based in New York City but have previously lived in Pennsylvania, California, and Idaho. I’ve spent time in all 48 contiguous United States and all 10 provinces of Canada. When I’m not at my desk, you can find me hiking, biking, paddling, train hopping, or road tripping to the next spot on the map.

Positions

I believe the core roles of a nonprofit board member are threefold:

1. Represent membership

A board member is a democratic representative of the members of the organization. If elected, it would be my job to actively listen to the community and be responsive to their interests.

As a white cis male, I am concerned that people like me are overrepresented in many OSM spaces to the detriment of others and to the OpenStreetMap project as a whole. OSM should be a welcoming environment where everyone has a seat at the table. If elected, I would use my position on the board to support initiatives that promote demographic and geographic diversity within OSM US events and spaces, and to ensure some voices aren’t privileged over others.

2. Support professional staff

OpenStreetMap US has an amazing executive director and professional staff who continue to excel in their large slate of responsibilities. These include running conferences and working groups, supporting mappers and tools, and helping the public use and understand OSM.

I am the only board candidate to have previously been a paid employee of OpenStreetMap US, giving me extensive firsthand knowledge of the organization.

If elected, I would be a stalwart advocate and supporter of the org’s professional staff, making sure they have the space and resources to carry out the mission of OpenStreetMap US.

3. Perform outreach

A core but often underappreciated role of a nonprofit board member is to interface with people outside the organization. Educators, researchers, organizers, nonprofits, governments, and companies are just some of the stakeholders who use or should be using OSM data, and who should be giving back.

I’ve attended over a dozen geospatial conferences since 2019. Most recently, I attended State of the Map Europe at my own expense as a representative of the US mapping community, hoping to improve understanding with European mappers.

But the bigger task for a board member is to represent OSM US in non-OSM spaces in an effort to build partnerships and solicit funding. If elected, ensuring the financial solvency of OSM US would be a top priority for me.

Election

To vote, make sure you are a member of OpenStreetMap US before February 22, 2026. You will receive your ballot via email. Please vote by March 1. Thank you again for considering my candidacy.

Eu odeio relações de ônibus

About me

I started mapping in 2021 as I tried to ride every street in Brooklyn, NY on wandrer.earth. I kept finding private streets and other issues on OSM and began fixing them.

At the moment I split my time between the Seattle area and Tucson, Arizona. My professional work is in non-profit accounting. I have worked with a number of organizations covering a full range of financial responsibilities. Handling everything from hands on bookkeeping to grant management to financial strategy.

My mapping

My most cohesive, complete project is detailed mapping of Train Mountain Railroad, the worlds longest miniature railroad. If you’re curious I gave a talk at State of the Map US in 2024 about it.

Most of my mapping is more miscellaneous in nature. I’m a big StreetComplete user, and I’ll always pull over on a bike ride to map a public bookcase! I also enjoy contributing detail to pedestrian and bicycle networks.

Board service and goals

Through the last two years serving as the Board Treasurer I have help usher OpenStreetMap US through a number of shifts in financial situation. Guiding the staff through financial challenges and changes in financial structure.

Through the next two years I want to continue this work, and assist the staff in streamlining bookkeeping and reporting. In addition, as a best practice I would like to see the organization through a financial audit or review. Ultimately leaving the organization on an even stronger financial foundation than it is today.

En mi entrada anterior “Procesamiento en tiempo real de notas de OSM con Bash” expliqué cómo mantener una base de datos local sincronizada con las notas de OpenStreetMap en menos de 10 segundos, usando herramientas comunes de Linux y PostgreSQL. Ese trabajo permitió tener un repositorio actualizado y confiable de notas, comentarios y cambios de estado.

Hoy quiero mostrar el siguiente paso: cómo esa base de datos se convierte en un servicio WMS que permite visualizar las notas directamente en aplicaciones como JOSM, Vespucci o QGIS. De esta manera, pasamos del procesamiento en segundo plano a la representación gráfica en el mapa, abriendo nuevas posibilidades para mapeadores e investigadores.

Las Capas del Servicio

El servicio ofrece cuatro capas principales:

• Notas abiertas (rojo): todas las notas activas, con intensidad de color según antigüedad.
• Notas cerradas (verde): reflejan el trabajo ya realizado, con intensidad según el tiempo desde el cierre.
• Países y zonas marítimas: fronteras, aguas territoriales y ZEE, para dar contexto geográfico y político.
• Zonas en disputa y no reclamadas: áreas donde la asignación de país es ambigua, clave para entender por qué algunas notas no encajan en un análisis nacional.

Casos de Uso

• Priorización de trabajo: un mapeador abre JOSM, carga la capa de notas abiertas y ve un cúmulo de puntos rojos en su ciudad. Decide enfocarse allí.
• Verificación de progreso: un grupo comunitario carga la capa de notas cerradas y observa un mar de puntos verdes, evidencia del esfuerzo colectivo.
• Contexto geopolítico: cerca de una frontera, las notas aparecen en una zona marcada como disputada. El mapeador entiende la ambigüedad en la asignación.
• Análisis espacial: un investigador usa QGIS para estudiar patrones: más notas en áreas urbanas, menos en rurales. El servicio facilita estadísticas y visualizaciones.

Cómo Usarlo

En JOSM:
1. Ir a Imagery → Add WMS Layer…
2. Ingresar la URL: https://geoserver.osm.lat/geoserver/osm_notes/wms
3. Seleccionar las capas deseadas.

En Vespucci:
1. Abrir configuración de capas.
2. Agregar capa WMS con la misma URL.
3. Activar las capas de notas abiertas, cerradas, países o disputas.

Conclusión

El proyecto avanza en dos etapas complementarias: primero, la ingesta en tiempo real de notas con Bash y PostgreSQL; ahora, la visualización mediante un servicio WMS que las pone directamente sobre el mapa. Juntos, estos componentes permiten a la comunidad OSM analizar, priorizar y coordinar esfuerzos con mayor claridad.

Invito a todos a probar el servicio en JOSM o Vespucci, y a seguir aportando ideas para mejorar esta herramienta que conecta la potencia del procesamiento en tiempo real con la riqueza de la visualización geográfica.

1. The first would have been Christon Bank Station. This lies just outside Embleton but for some reason was named after a nearby farm rather than the village. It opened in 1847 and closed in 1965. In addition to a limited volume of passenger traffic the station also carried whinstone from the nearby Embleton Quarry. The two were linked by a narrow gauge tramway. More details <here>.
2. The second would have been Fallodon which opened in 1847 and closed in 1934. Only a mile or so from Christon Bank, this was another complete station with two platforms, name boards and a station house. But it was never intended for the general public. They used Christon Bank Station. Fallodon was solely for the use of the Grey family, their guests and their servants. The Grey family also had a private station at Little Mill: four miles south, close to the other family seat at Howick Hall. At the time, the proprietor of Fallodon Hall was Sir George Grey, who was Home Secretary. The passage of the Newcastle & Berwick Railway Bill through Parliament was eased by providing him with a private station and the right to stop any public train. More details <here>.
3. The third was Chathill Station (pictured above). This opened in 1847. At the time there four passenger trains called every weekday in both directions. Now there are only two services each way on a weekday and none on Sunday. The station building is now a private house. It is listed, Grade-2, but the station is unstaffed and has no ticket facilities or other amenities.
4. From 1898 Chathill Station was the south-western terminus of the North Sunderland Railway. This was built to serve the harbour at Seahouses. The line was rarely profitable and a proposed extension to Bamburgh was never constructed. It was taken over by the LNER in 1939, and closed in 1951. Seahouses station was then demolished. The site where it stood is now the village car park and (importantly on a cold day) also houses the public toilets. For a view of how the North Sunderland line looked about 100 years ago (with its one loco and three coaches) see the Pathe film <here> and more information <here>.

We've had a lot of rain recently. Fields are flooded and ditches over-flowing. But the weather today was an improvement. Some mist, and a noticeable headwind on the return journey. No proper rain, patches of blue sky and even a little sunshine were very welcome. 

Kilka słów o postępie w nauce, 8 lutego 2026 roku

1. Dodawanie zakresów mieszkań tagiem addr:flats jest tylko informacyjne. Nie pomaga to niestety w nawigacji i możliwości wpisywania adresów z numerem mieszkań do prowadzenia przez nawigację. Stanowi jednak dobry wstęp by w przyszłości “rzeźbić” samemu każde mieszkanie lub by ktoś inny się tego podjął.
2. To dziwne, że nie było automatu Pocztex zaznaczonego na osiedlu Zygmunta starego. InPost, DPD czy one box są dobrze oznaczone w całym mieście, jednak tutaj niezweryfikowane podejrzenia iż to się zaczytuje automatycznie.
3. Podejrzewam, że OSM jest traktowane po macoszemu przez wszystkich. Szczególnie tych, którzy korzystają z tego nieświadomie. Ma to swoje zalety - udało mi się jako pierwszemu dodać dwa urządzenia będące recyklomatami na mapie OSM dla Poznania.

Podsumowując, całkiem przyjemnie jest edytować wiedząc, że nikt mnie nie ubiegnie. Szkoda jednak, że tak wiele jest jeszcze przez to do zrobienia.