#openbenches — Public Fediverse posts

🆕 blog! “Android now stops you sharing your location in photos”

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's…

👀 Read more: https://shkspr.mobi/blog/2026/04/android-now-stops-you-sharing-your-location-in-photos/
⸻
#android #geolocation #geotagging #google #OpenBenches

🆕 blog! “Android now stops you sharing your location in photos”

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's…

👀 Read more: https://shkspr.mobi/blog/2026/04/android-now-stops-you-sharing-your-location-in-photos/
⸻
#android #geolocation #geotagging #google #OpenBenches

🆕 blog! “Android now stops you sharing your location in photos”

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's…

👀 Read more: https://shkspr.mobi/blog/2026/04/android-now-stops-you-sharing-your-location-in-photos/
⸻
#android #geolocation #geotagging #google #OpenBenches

🆕 blog! “Android now stops you sharing your location in photos”

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's…

👀 Read more: https://shkspr.mobi/blog/2026/04/android-now-stops-you-sharing-your-location-in-photos/
⸻
#android #geolocation #geotagging #google #OpenBenches

🆕 blog! “Android now stops you sharing your location in photos”

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's…

👀 Read more: https://shkspr.mobi/blog/2026/04/android-now-stops-you-sharing-your-location-in-photos/
⸻
#android #geolocation #geotagging #google #OpenBenches

Android now stops you sharing your location in photos

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's Android has now broken that.

On the web, we used to use:

<input type="file" accept="image/jpeg">

That opened the phone's photo picker and let the use upload a geotagged photo. But a while ago Google deliberately broke that.

Instead, we were encourage to use the file picker:

<input type="file">

That opened the default file manager. This had the unfortunate side-effect of allowing the user to upload any file, rather than just photos. But it did allow the EXIF metadata through unmolested. Then Google broke that as well.

Using a "Progressive Web App" doesn't work either.

So, can users transfer their photos via Bluetooth or QuickShare? No. That's now broken as well.

You can't even directly share via email without the location being stripped away.

Literally the only way to get a photo with geolocation intact is to plug in a USB cable, copy the photo to your computer, and then upload it via a desktop web browser?

Why?!?!?

Because Google run an anticompetitive monopoly on their dominant mobile operating system.

Privacy.

There's a worry that users don't know they're taking photos with geolocation enabled. If you post a cute picture of your kid / jewellery / pint then there's a risk that a ne’er-do-well could find your exact location.

Most social media services are sensible and strip the location automatically. If you try to send a geotagged photo to Facebook / Mastodon / BlueSky / WhatsApp / etc, they default to not showing the location. You can add it in manually if you want, but anyone downloading your photo won't see the geotag.

And, you know, I get it. Google doesn't want the headline "Stalkers found me, kidnapped my baby, and stole my wedding ring - how a little known Android feature puts you in danger!"

But it is just so tiresome that Google never consults their community. There was no advance notice of this change that I could find. Just a bunch of frustrated users in my inbox blaming me for breaking something.

I don't know what the answer is. Perhaps a pop up saying "This website wants to see the location of your photos. Yes / No / Always / Never"? People get tired of constant prompts and the wording will never be clear enough for most users.

It looks like the only option available will be to develop a native Android app (and an iOS one?!) with all the cost, effort, and admin that entails. Android apps have a special permission for accessing geolocation in images.

If anyone has a working way to let Android web-browsers access the full geolocation EXIF metadata of photos uploaded on the web, please drop a comment in the box.

In the meantime, please leave a +1 on this HTML Spec comment.

Android now stops you sharing your location in photos

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's Android has now broken that.

On the web, we used to use:

<input type="file" accept="image/jpeg">

That opened the phone's photo picker and let the use upload a geotagged photo. But a while ago Google deliberately broke that.

Instead, we were encourage to use the file picker:

<input type="file">

That opened the default file manager. This had the unfortunate side-effect of allowing the user to upload any file, rather than just photos. But it did allow the EXIF metadata through unmolested. Then Google broke that as well.

Using a "Progressive Web App" doesn't work either.

So, can users transfer their photos via Bluetooth or QuickShare? No. That's now broken as well.

You can't even directly share via email without the location being stripped away.

Literally the only way to get a photo with geolocation intact is to plug in a USB cable, copy the photo to your computer, and then upload it via a desktop web browser?

Why?!?!?

Because Google run an anticompetitive monopoly on their dominant mobile operating system.

Privacy.

There's a worry that users don't know they're taking photos with geolocation enabled. If you post a cute picture of your kid / jewellery / pint then there's a risk that a ne’er-do-well could find your exact location.

Most social media services are sensible and strip the location automatically. If you try to send a geotagged photo to Facebook / Mastodon / BlueSky / WhatsApp / etc, they default to not showing the location. You can add it in manually if you want, but anyone downloading your photo won't see the geotag.

And, you know, I get it. Google doesn't want the headline "Stalkers found me, kidnapped my baby, and stole my wedding ring - how a little known Android feature puts you in danger!"

But it is just so tiresome that Google never consults their community. There was no advance notice of this change that I could find. Just a bunch of frustrated users in my inbox blaming me for breaking something.

I don't know what the answer is. Perhaps a pop up saying "This website wants to see the location of your photos. Yes / No / Always / Never"? People get tired of constant prompts and the wording will never be clear enough for most users.

It looks like the only option available will be to develop a native Android app (and an iOS one?!) with all the cost, effort, and admin that entails. Android apps have a special permission for accessing geolocation in images.

If anyone has a working way to let Android web-browsers access the full geolocation EXIF metadata of photos uploaded on the web, please drop a comment in the box.

In the meantime, please leave a +1 on this HTML Spec comment.

Android now stops you sharing your location in photos

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's Android has now broken that.

On the web, we used to use:

<input type="file" accept="image/jpeg">

That opened the phone's photo picker and let the use upload a geotagged photo. But a while ago Google deliberately broke that.

Instead, we were encourage to use the file picker:

<input type="file">

That opened the default file manager. This had the unfortunate side-effect of allowing the user to upload any file, rather than just photos. But it did allow the EXIF metadata through unmolested. Then Google broke that as well.

Using a "Progressive Web App" doesn't work either.

So, can users transfer their photos via Bluetooth or QuickShare? No. That's now broken as well.

You can't even directly share via email without the location being stripped away.

Literally the only way to get a photo with geolocation intact is to plug in a USB cable, copy the photo to your computer, and then upload it via a desktop web browser?

Why?!?!?

Because Google run an anticompetitive monopoly on their dominant mobile operating system.

Privacy.

There's a worry that users don't know they're taking photos with geolocation enabled. If you post a cute picture of your kid / jewellery / pint then there's a risk that a ne’er-do-well could find your exact location.

Most social media services are sensible and strip the location automatically. If you try to send a geotagged photo to Facebook / Mastodon / BlueSky / WhatsApp / etc, they default to not showing the location. You can add it in manually if you want, but anyone downloading your photo won't see the geotag.

And, you know, I get it. Google doesn't want the headline "Stalkers found me, kidnapped my baby, and stole my wedding ring - how a little known Android feature puts you in danger!"

But it is just so tiresome that Google never consults their community. There was no advance notice of this change that I could find. Just a bunch of frustrated users in my inbox blaming me for breaking something.

I don't know what the answer is. Perhaps a pop up saying "This website wants to see the location of your photos. Yes / No / Always / Never"? People get tired of constant prompts and the wording will never be clear enough for most users.

It looks like the only option available will be to develop a native Android app (and an iOS one?!) with all the cost, effort, and admin that entails. Android apps have a special permission for accessing geolocation in images.

If anyone has a working way to let Android web-browsers access the full geolocation EXIF metadata of photos uploaded on the web, please drop a comment in the box.

In the meantime, please leave a +1 on this HTML Spec comment.

Android now stops you sharing your location in photos

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's Android has now broken that.

On the web, we used to use:

<input type="file" accept="image/jpeg">

That opened the phone's photo picker and let the use upload a geotagged photo. But a while ago Google deliberately broke that.

Instead, we were encourage to use the file picker:

<input type="file">

That opened the default file manager. This had the unfortunate side-effect of allowing the user to upload any file, rather than just photos. But it did allow the EXIF metadata through unmolested. Then Google broke that as well.

Using a "Progressive Web App" doesn't work either.

So, can users transfer their photos via Bluetooth or QuickShare? No. That's now broken as well.

You can't even directly share via email without the location being stripped away.

Literally the only way to get a photo with geolocation intact is to plug in a USB cable, copy the photo to your computer, and then upload it via a desktop web browser?

Why?!?!?

Because Google run an anticompetitive monopoly on their dominant mobile operating system.

Privacy.

There's a worry that users don't know they're taking photos with geolocation enabled. If you post a cute picture of your kid / jewellery / pint then there's a risk that a ne’er-do-well could find your exact location.

Most social media services are sensible and strip the location automatically. If you try to send a geotagged photo to Facebook / Mastodon / BlueSky / WhatsApp / etc, they default to not showing the location. You can add it in manually if you want, but anyone downloading your photo won't see the geotag.

And, you know, I get it. Google doesn't want the headline "Stalkers found me, kidnapped my baby, and stole my wedding ring - how a little known Android feature puts you in danger!"

But it is just so tiresome that Google never consults their community. There was no advance notice of this change that I could find. Just a bunch of frustrated users in my inbox blaming me for breaking something.

I don't know what the answer is. Perhaps a pop up saying "This website wants to see the location of your photos. Yes / No / Always / Never"? People get tired of constant prompts and the wording will never be clear enough for most users.

It looks like the only option available will be to develop a native Android app (and an iOS one?!) with all the cost, effort, and admin that entails. Android apps have a special permission for accessing geolocation in images.

If anyone has a working way to let Android web-browsers access the full geolocation EXIF metadata of photos uploaded on the web, please drop a comment in the box.

In the meantime, please leave a +1 on this HTML Spec comment.

Android now stops you sharing your location in photos

My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map.

Google's Android has now broken that.

On the web, we used to use:

<input type="file" accept="image/jpeg">

That opened the phone's photo picker and let the use upload a geotagged photo. But a while ago Google deliberately broke that.

Instead, we were encourage to use the file picker:

<input type="file">

That opened the default file manager. This had the unfortunate side-effect of allowing the user to upload any file, rather than just photos. But it did allow the EXIF metadata through unmolested. Then Google broke that as well.

Using a "Progressive Web App" doesn't work either.

So, can users transfer their photos via Bluetooth or QuickShare? No. That's now broken as well.

You can't even directly share via email without the location being stripped away.

Literally the only way to get a photo with geolocation intact is to plug in a USB cable, copy the photo to your computer, and then upload it via a desktop web browser?

Why?!?!?

Because Google run an anticompetitive monopoly on their dominant mobile operating system.

Privacy.

There's a worry that users don't know they're taking photos with geolocation enabled. If you post a cute picture of your kid / jewellery / pint then there's a risk that a ne’er-do-well could find your exact location.

Most social media services are sensible and strip the location automatically. If you try to send a geotagged photo to Facebook / Mastodon / BlueSky / WhatsApp / etc, they default to not showing the location. You can add it in manually if you want, but anyone downloading your photo won't see the geotag.

And, you know, I get it. Google doesn't want the headline "Stalkers found me, kidnapped my baby, and stole my wedding ring - how a little known Android feature puts you in danger!"

But it is just so tiresome that Google never consults their community. There was no advance notice of this change that I could find. Just a bunch of frustrated users in my inbox blaming me for breaking something.

I don't know what the answer is. Perhaps a pop up saying "This website wants to see the location of your photos. Yes / No / Always / Never"? People get tired of constant prompts and the wording will never be clear enough for most users.

It looks like the only option available will be to develop a native Android app (and an iOS one?!) with all the cost, effort, and admin that entails. Android apps have a special permission for accessing geolocation in images.

If anyone has a working way to let Android web-browsers access the full geolocation EXIF metadata of photos uploaded on the web, please drop a comment in the box.

In the meantime, please leave a +1 on this HTML Spec comment.

First Upload!

The verified Badge was issued to @Terence Eden

Thanks for adding your first bench! This badge shows that you've started your journey with OpenBenches.org

Earning Criteria: Uploaded a new bench and photo..
Issued on: 04/09/2026 18:35:29
Accepted On: 04/09/2026 18:45:00

Verify the Badge here.

#OpenBenches #IssuedByBadgeFed #_BadgeDrop

First Upload!

The verified Badge was issued to @Terence Eden

Thanks for adding your first bench! This badge shows that you've started your journey with OpenBenches.org

Earning Criteria: Uploaded a new bench and photo..
Issued on: 04/09/2026 18:35:29
Accepted On: 04/09/2026 18:45:00

Verify the Badge here.

#OpenBenches #IssuedByBadgeFed #_BadgeDrop

First Upload!

The verified Badge was issued to @Terence Eden

Thanks for adding your first bench! This badge shows that you've started your journey with OpenBenches.org

Earning Criteria: Uploaded a new bench and photo..
Issued on: 04/09/2026 18:35:29
Accepted On: 04/09/2026 18:45:00

Verify the Badge here.

#OpenBenches #IssuedByBadgeFed #_BadgeDrop

tagged some benches in Axminster today which (finally!) put me over 100 contributions on #openbenches 🎉

https://openbenches.org/contributors

🆕 blog! “OpenBenches hits 40k”

Back in November 2023, our crowdsourced website of memorial benches reached 30,000 entries. At the start of March this year, I was delighted when long-time contributor jrbray1 added this gorgeous memorial, taking us up to 40,000 benches catalogued:

You can read more about Dr Judy John and her work on biodiversity.

Using the power of advanced machine learning, it is …

👀 Read more: https://shkspr.mobi/blog/2026/03/openbenches-hits-40k/
⸻
#OpenBenches

OpenBenches hits 40k

Back in November 2023, our crowdsourced website of memorial benches reached 30,000 entries. At the start of March this year, I was delighted when long-time contributor jrbray1 added this gorgeous memorial, taking us up to 40,000 benches catalogued:

You can read more about Dr Judy John and her work on biodiversity.

Using the power of advanced machine learning, it is possible to plot the growth on an innovative form of data visualisation known as "a graph"!

That's the sort of "number go up" that investors like to see. I reckon someone will come along to give us a bazillion dollarydoos any minute now.

For those of you who like text rather than graphics, here are our historic milestones:

• 10K - December 2018
• 20K - August 2021
• 30K - November 2023
• 40K - March 2026
• 50k - ??? Probably September 2027 ???

Tell you what, when we get to fifty-thousand, we'll throw a big party and you'll all be invited 🥳

If you spot a lovely memorial bench while you're out and about, please take a geotagged photo and upload it to OpenBenches.org.

RE: https://bot.openbenches.org/posts/69aac1e2-90db-8107-8dad-2742b2b22b37.json

Happy to announce that #OpenBenches is now back on the Fediverse using a self-hosted bot platform.

Just added my first contribution to #OpenBenches. I think there are a few more around our home, so I'll see what else can be added!

https://openbenches.org/bench/41478

Thanks @openbenches @Edent !

🆕 blog! “OpenBenches at FOSDEM”

At the recent FOSDEM, I did a very quick lightning talk about our OpenBenches project.

Sadly, despite the best efforts of the AV team, the video had a missing section. I took my own audio recording and zipkid took some photos, so I was able to recreate it using the Flowblade video editor.

Enjoy!

Many thanks to Edward Betts for running the dev room and…

👀 Read more: https://shkspr.mobi/blog/2026/02/openbenches-at-fosdem/
⸻
#fosdem #OpenBenches

OpenBenches at FOSDEM

At the recent FOSDEM, I did a very quick lightning talk about our OpenBenches project.

Sadly, despite the best efforts of the AV team, the video had a missing section. I took my own audio recording and zipkid took some photos, so I was able to recreate it using the Flowblade video editor.

Enjoy!

Many thanks to Edward Betts for running the dev room and providing the display laptop.

🆕 blog! “The cost of running OpenBenches.org”

After my recent presentation at FOSDEM, someone asked a pretty reasonable question. What does it cost to run OpenBenches?

It is, thankfully, surprisingly cheap! In part, that's because it is a relatively simple tech stack - PHP, MySQL, a couple of API calls to external services. It was designed to be as low cost while …

👀 Read more: https://shkspr.mobi/blog/2026/02/the-cost-of-running-openbenches-org/
⸻
#fosdem #foss #money #OpenBenches

The cost of running OpenBenches.org

After my recent presentation at FOSDEM, someone asked a pretty reasonable question. What does it cost to run OpenBenches?

It is, thankfully, surprisingly cheap! In part, that's because it is a relatively simple tech stack - PHP, MySQL, a couple of API calls to external services. It was designed to be as low cost while also being useful. Here's the breakdown:

Hosting - £171 per year

Our biggest expense but, I think, our most reasonable. Krystal charges around £342 for a 2 year contract. That includes unlimited bandwidth and storage, as well as the domain name. We have nearly 400GB of photos and bot scraping means we can use over 900GB of bandwidth per month - so Krystal give us a rather good deal!

Use this affiliate link and code EDENT to get a small discount.

Stadia Maps - US$20 / month

Geocoding is surprisingly hard to do locally. We need to transform latitude and longitude into addresses, and then back again. Stadia Maps cost about the same as our hosting! What's rather annoying is that we only use about half the API calls in our plan. We need to find a cheaper solution.

Mapping - Free!

When we used Stadia for drawing maps, we regularly ran over our quota. So we switched to OpenFreeMap which produces gorgeous interactive maps.

The service has been rock solid and very responsive to bugs on GitHub.

Logo - US$5

I'm not a good designer, so we bought a logo from The Noun Project and then coloured it in. Bargain for a fiver!

Image CDN - Free!

Although we have unlimited bandwidth with Krystal, we're only located in one region - the UK. WeServ. It's also pointless serving full resolution images to small screens.

So WeServ offers free image resizing and global CDNs. Personally, I'm not a fan of CloudFlare (their CDN partner) so I'm looking to change provider.

OCR - Free!

People don't want to type in the inscription of the photo, so we use Google Cloud Vision.

We send less than 1,000 requests per month - so we're inside their free tier. If we get more popular, that'll get more expensive. But I don't know of a local-first OCR which is as good as Google's. Sadly, Tesseract is rubbish for extracting text from photos.

Authentication - Free!

We don't want to store anyone's passwords. The free tier of Auth0 allows us to do social login for up to 25,000 monthly users. Which is more than enough for us.

Sadly, Auth0 don't support the Fediverse, so I had to build my own "Log-in with Mastodon" service.

As much as we'd like to run social login locally, we simply don't want to be responsible for securing users' details & API keys.

Software - Free!

As per the OpenBenches colophon we use a lot of cool FOSS. Small JS libraries, big PHP frameworks, and everything in between.

Income

Thanks to GitHub Sponsors we make a whopping US$3 per month!

Similarly, our OpenCollective Sponsors brings in about £3 per month.

Merchandising! You can buy OpenBenches branded t-shirts, mugs, and hats. That nets us about £20 per year

Call it roughly £80 income. OK, it is better than nothing - but doesn't even cover a quarter of our costs. Sometimes people give us a higher donation privately, which is also very welcome. These people are listed on our README.

Total

On the assumption that our time is worthless (ha!) and that we only rarely go over our providers' API limits, and we get in some revenue, the cost of running OpenBenches is less than £300 per year.

That's not bad for a fun little hobby. People certainly spend more than that on Funkopops, vaping, and mechanical keyboards!

Nevertheless, I'm always slightly worried that we'll go viral and have an unexpectedly high bill from our API providers.

I would love to be able to hire a proper designer to make the site look a bit nicer. I also want to be able to buy a modern iPhone so that I can test it in the latest Safari.

If you have any suggestions for cutting costs, or non-scummy ways to help us raise funds, please drop a comment below.

🆕 blog! “Why do people leave comments on OpenBenches?”

I'm still a believer in the promise of Web 2.0. The idea that giving people a curated space to chat produces tiny sparks of magic.

My wife Liz and I have been running the OpenBenches project for about 8 years - it's a crowd-sourced repository of memorial benches. People take a geotagged photo of a bench's plaque,…

👀 Read more: https://shkspr.mobi/blog/2025/12/why-do-people-leave-comments-on-openbenches/
⸻
#OpenBenches #web

Why do people leave comments on OpenBenches?

I'm still a believer in the promise of Web 2.0. The idea that giving people a curated space to chat produces tiny sparks of magic.

My wife Liz and I have been running the OpenBenches project for about 8 years - it's a crowd-sourced repository of memorial benches. People take a geotagged photo of a bench's plaque, upload it to our site, and we share it with the world. Might sound a bit niche, but we have around thirty-nine thousand benches catalogued from all over the world.

From the start, we had a comment form under each bench. Of course, we pre-moderate any comments. That helps with our Online Safety Act obligations and prevents spam from being published. We don't collect any personal data, to reduce our GDPR exposure. Our comments are self-hosted using the excellent Commentics - which means we don't send people's data off to a 3rd party.

We thought that this would be used to tell us that an inscription was wrong, or if a bench had moved, or something like that.

We were completely wrong!

People use OpenBenches comments for all sorts of things. Of course, there are a few which provide details about the bench itself:

Other provide a little context about the person:

But those sorts of comments are hardly the majority. The comments break down (roughly) into these categories:

I want to know more about this person

I sat on this bench, searched for the inscription and found this site. I want to share my feelings

Thank you for putting a bench here

This has moved me

My heart has broken

I can't visit this bench, but I'm glad someone has shared a photo

Thank you for adding a photo

I don't know the person this bench commemorates, but I want to let them know they're still loved and remembered

That's nice

Hundreds of people sharing connections. Wanting to express their feelings. Understanding the terrible pain of loss and the hope that, someday, someone will think fondly of us.

You can view all the comments on OpenBenches.org.

🆕 blog! “OpenBenches 💖 OpenStreetMap”

When Liz and I created the OpenBenches website, it was just designed to be a fun way for people to record memorial benches. Since then things have got out of hand and we now have over thirty-nine thousand benches recorded!

Our plan was never to compete with something like OpenStreetMap. The OSM project is vast, complex, and…

👀 Read more: https://shkspr.mobi/blog/2025/11/openbenches-%f0%9f%92%96-openstreetmap/
⸻
#OpenBenches #OpenStreetMap

OpenBenches 💖 OpenStreetMap

https://shkspr.mobi/blog/2025/11/openbenches-%f0%9f%92%96-openstreetmap/

When Liz and I created the OpenBenches website, it was just designed to be a fun way for people to record memorial benches. Since then things have got out of hand and we now have over thirty-nine thousand benches recorded!

Our plan was never to compete with something like OpenStreetMap. The OSM project is vast, complex, and brilliant - we are small, simple, and differently brilliant. But, over the years, people have repeatedly asked if there's any way to combine the two data sets.

This has proved logistically complex for several reasons.

1. Our users aren't experienced mappers.
   • Most of our entries are uploaded with fairly fuzzy GPS co-ordinates. Mobile phones aren't always the best at accurate locations and, besides, people tend to stand away from the bench when taking its photo. So our data isn't quite at the level of quality rightly demanded by OSM.
2. OSM didn't have a tag specifically for memorial benches.
   • We started out site in 2017. OSM added the Tag:memorial=bench in 2021. Up until then, there wasn't a great way to record that a bench was a memorial.
3. Data licencing is complicated.
   • We chose the Creative Commons Attribution ShareAlike licence - it seemed like a good idea at the time! OSM use ODbL which is subtly incompatible. As such, OSM volunteers asked us to sign a waiver so they could use the data - which we happily did.
4. Adding or editing data on OSM can be complicated.
   • OpenBenches is designed to be an upload-and-forget process. It doesn't matter much to us if a bench is recorded a dozen metres away from its true location. But that isn't the way OSM works. We didn't want to bulk upload data which was inaccurate, incomplete, or inappropriate. Luckily, there are now tools to help with that!

Things have been working away in the background. Some people have manually added Key:openbenches:id to appropriate benches, and others have edited our database to make the locations closer to reality.

And now, thanks to the sterling work of the brilliant Pieter Vander Vennet we're moving to our next phase of increased collaboration!

Firstly, there are about 1,060 benches on OpenStreetMap which have an OpenBenches ID. I've taken all those OSM IDs and put them into our database. Which means that the OpenBenches website can display a button like this:

One click and you're looking at OSM - ready to investigate, edit, or admire.

But what about the other 38,000 benches? Well, that's where MapComplete comes in. MapComplete is sort of like Pokémon Go for maps. As you wander this Earth, you can complete little quests to help improve OpenStreetMap. For example, on the "Pubs" quest, you can add details of all the pubs you visit.

With the "Bench" quest, it is a little different. If an OpenBench is sufficiently nearby an OSM bench, you'll get the option to link the two with a couple of clicks.

But there are loads of benches we have discovered which aren't in the OSM database. In which case, you can add a new bench to OSM using the data from OpenBenches!

This has been a couple of years in the making - but it looks like most of the kinks are now sorted out. I'm sure there will be a few early problems, and no doubt a bit of late-night bug fixing, but I hope that this is the start of something long-lasting. The joy of decentralised sites using open data is that we can all build on each others' work in a spirit of fun and exploration.

#openbenches #openstreetmap

@Edent In reference to #OpenBenches, did you know the National Trust is logging bench information in #OpenStreetMap? Tidbit shared at #sofmeu25

Open Benches cumple 8 años. ¡Felicidades! En el sitio web de #OpenBenches pueden encontrar los bancos conmemorativos que hay en Málaga: https://openbenches.org. También los encontrarán en #OpenStreetMap. Los más característicos están en el Cementerio Inglés de Málaga. Si son colaboradores de #OpenStreetMap y de #OpenBenches, pueden añadir esta etiqueta a su página de usuario en el wiki: https://wiki.openstreetmap.org/wiki/Template:OpenBenches_contributor.

Decided to have an #OpenBenches cycle ride.

Found two that I can add when I get home.

@openbenches

🆕 blog! “Reverse Geocoding is Hard”

My wife and I run OpenBenches - a crowd-sourced database of nearly 40,000 memorial benches. Every bench is geo-tagged with a latitude and longitude. But how do you go from a string of digits to something human readable?

How do I turn -33.755780,150.603769 into "42 Wallaby Way, Sydney, Australia"?

Luckily, that's a (somewhat) solved …

👀 Read more: https://shkspr.mobi/blog/2025/04/reverse-geocoding-is-hard/
⸻
#geolocation #geotagging #OpenBenches

Reverse Geocoding is Hard

https://shkspr.mobi/blog/2025/04/reverse-geocoding-is-hard/

My wife and I run OpenBenches - a crowd-sourced database of nearly 40,000 memorial benches. Every bench is geo-tagged with a latitude and longitude. But how do you go from a string of digits to something human readable?

How do I turn -33.755780,150.603769 into "42 Wallaby Way, Sydney, Australia"?

Luckily, that's a (somewhat) solved problem. Services like OpenCage, StadiaMaps, OpenStreetMap, and Geocode.Earth all provide APIs which transform co-ordinates into addresses. Done! Let's go home.

Except… Not everywhere has an address. Some benches are in parks. They typically don't have a street number, but might have an interesting feature nearby to help with location. For example a statue or prominent landmark.

And… Not every address is relevant. Some benches are on streets. But we probably don't want to imply that the bench is inside or belongs to a specific nearby house.

Let's step back a bit. Why do we want to display a human-readable address?

We have two use-cases.

"As a visitor to the site, I want to:"

1. Read a (rough) textual representation of where the bench is.
2. Click on a component of the address to see all benches within that area.

The first is easy to explain:

The second is harder. Suppose a bench is in Wellington, New Zealand. We want to create a URl like openbenches.org/location/New Zealand/Wellington/. That way, users can click on the word "Wellington" and find all the benches nearby. A user can also manually edit that URl to increase or decrease precision.

Both of these are problems of precision.

Let's take a look at how one of the reverse geocoding services deals with transforming 51.476845,-0.295296 into an address:

Royal Botanic Gardens, Kew, Sandycombe Road, Kew, London Borough of Richmond upon Thames, London, Greater London, England, TW9 2EN, United Kingdom

That is too much address!

Yes, it is technically accurate. But it contains far too much detail for humans, the postcode is irrelevant, and the weird-subdivisions are nothing that a local person would use.

Looking at the full API response, we can see:

{  "place_id": 258770727,  "licence": "Data © OpenStreetMap contributors, ODbL 1.0. http://osm.org/copyright",  "name": "Royal Botanic Gardens, Kew",  "display_name": "Royal Botanic Gardens, Kew, Elizabeth Cottages, Kew, London Borough of Richmond upon Thames, London, Greater London, England, TW9 3NJ, United Kingdom",  "address": {    "leisure": "Royal Botanic Gardens, Kew",    "road": "Elizabeth Cottages",    "suburb": "Kew",    "city_district": "London Borough of Richmond upon Thames",    "ISO3166-2-lvl8": "GB-RIC",    "city": "London",    "state_district": "Greater London",    "state": "England",    "ISO3166-2-lvl4": "GB-ENG",    "postcode": "TW9 3NJ",    "country": "United Kingdom",    "country_code": "gb"  }}

Aha! Perhaps I can build a better address using just those components!

Except… Not every country has states. And not all states are used when giving addresses. Not every location is in a city. Some places have villages, prefectures, municipalities, and hamlets.

New York, New York is a valid address, but Berlin, Berlin is not!

There's an address formatter by OpenCage which is pretty sensible about stripping off irrelevant details. But, to go back to my first point, not every map location on OpenBenches is a street address and - even if it is on a street - it probably shouldn't have a house number.

Well, there's kind of a solution to that! Most mapping provider have a POI function - we can find nearby things of interest and use them as a location.

Here's a bench in Cook County, Illinois, USA. The POI address is:

{…   "name": "Central Park",   "coarse_location": "Des Plaines, IL, USA",…}

I assume there's only one Central Park in Des Plaines. Do people know that "Il" is Illinois? Would "Cook County" be useful?

On the subject of localisation, not everywhere speaks English. Do I want to display addresses like "原爆の子の像, 広島, 日本"? How about "原爆の子の像, Hiroshima, Japan"?

We're an international site, but most benches are in Anglophone countries.

Of course, just because something is physically near a POI, that doesn't mean it is logically close to it.

Consider a bench situated at the edge of this park

The nearest POI is "Gay's Creamery" - across the river. Is that what you'd expect? Is there any way to easily say "if a point is inside an amenity* then use that as the address?

I don't want the users of our site to have to select from a list of POIs or addresses, this should be as automated as possible.

The Plan

For each bench:

1. Use StadiaMaps to get the nearest POI.
2. Get the data in English.
3. Concatenate the name and coarse location.
4. Save the "address".
5. Wait for complaints?

Thoughts?

#geolocation #geotagging #OpenBenches

And I even found a bench that wasn't on #openbenches
https://openbenches.org/bench/36916

I added another bench to openbenches.org
#OpenBenches #Burntwood

https://openbenches.org/bench/36544

I added a bench to openbenches.org
#OpenBenches #Burntwood

https://openbenches.org/bench/36545

@openbenches.org Is it okay to share benches on #OpenBenches that commemorate events, @Edent? I thought they could only be commemorative benches dedicated to people. I have shared benches that commemorate people in Malaga: https://openbenches.org/user/9107. So far I have not uploaded those commemorating events (there are two or three of this type in Malaga). https://commons.wikimedia.org/wiki/File:Replica_of_a_Commemorative_Bench_to_the_Park_of_Malaga_03.jpg