OpenStreetMap logo OpenStreetMap

On Tour in the Netherlands

Posted by b-unicycling on 20 January 2025 in English. Last updated on 31 January 2025.

Street-level imagery

Since last Thursday, I’m touring the Netherlands with the band I’m in. I brought the GoPro Max sponsored by Meta, because I thought it would be a great opportunity to get lots of footage for Panoramax which has little coverage in the Netherlands so far. We’re staying in the same place all the time, near Epe in Gelderland and fan out for the gigs almost all over the Netherlands. We’ll be playing until the 31st of January.

Screenshot from Panoramax showing the progress on 2025-01-31

Unfortunately, it’s been very foggy since we arrived, so the imagery is not the best. It is also very cold, and the third trip (to Zutphen, if I remember correctly), the metal on the holder hinge shrunk and the camera tilted back, so that footage was fairly useless.

I upload the images to mapillary first, after all, they sponsored the camera, so it takes a while to get them onto Panoramax, and the internet at the accommodation doesn’t seem as quick as what I’m used to.

Here’s a link to the footage gathered footage on Panoramax, but it’s still a work in progress, of course.

Mapping by survey

Of course, I can’t stop myself from mapping from the van window or walking around that little bit between sound check and gig. I’m mostly adding bicycle parking (I know it’s a clichee that the Netherlands are great for cycling, but good Lord, are they!), post boxes, defibribrillators, missing shops and whatever else. I’ve also added a bit of roof:material=thatch, because I find it fascinating how much is still around, compared to Ireland. Even though I was told by our sound engineer that some of it is made of plastic. Disgusting. But since I can’t see that from afar, I’ll still map it as roof:material=thatch.

Mapping theatre details

Every night, apart from when we’re off like today, we’re in a different theatre, and usually we don’t know what to expect in amenities. Some of them are fairly large theatres with a corresponding large backstage area with many amenities like showers, microwaves, washing machine and tumble dryer, games etc. We don’t have a self-service washing machine at the accommodation which I had expected, so I would personally like to know beforehand what to expect at a theatre. For future reference, I have started adding the facilities with a backstage prefix such as at Het Kruispunt in Barendrecht: OSM Screenshot with backstage tags I know this is very niche micro-mapping, but why not?

Mapping from satellite imagery

If you follow my journey, you’ll know that I have a big interest in history. How interesting to find that the start_date of the houses is mapped everywhere! From what I could see, there was a huge import of buildings (only the larger ones, no sheds or garages) with their addresses and start date in 2014. Needless to say, that has become quite outdated. I’ve added a couple of the cabins, static caravans or whatever they are around where we are staying. But it must have made such a difference for OSM Netherlands to have that open data. Something we can still only dream about in Ireland, but it goes to show that there is always work in catching up to do.

Location: Zuuk, Epe, Gelderland, Netherlands, 8161 RE, Netherlands
Email icon Bluesky Icon Facebook Icon LinkedIn Icon Mastodon Icon Telegram Icon X Icon

Discussion

Comment from Taya_S on 21 January 2025 at 06:44

Welcome to the Netherlands! I hope you and your band enjoy your time here!

Even though I was told by our sound engineer that some of it is made of plastic. Disgusting.

So this is how I learn that’s apparently a thing. As far as I’m aware it’s not a super common at least. Or at least not where I live as far as I’m aware. Plastic can’t replace a good weathered looking thatched roof.

From what I could see, there was a huge import of buildings (only the larger ones, no sheds or garages) with their addresses and start date in 2014

That data is actually still continuously being imported. New houses still get imported. But as you pointed out, the data on sheds, static caravans, and other such objects can be a bit lacking. Interestingly enough, it does have pretty good data on static boats

Comment from b-unicycling on 21 January 2025 at 18:42

Thank you for your comment, Taya_S! We’re enjoying ourselves a lot, thanks!

Comment from Peter Bremer on 27 January 2025 at 21:41

So cool, great to see some more track in the Netherlands on Panoramax. I’m making tracks around Eindhoven, whenever I’m in the country. (Only the last time on Panoramax.)

the metal on the holder hinge shrunk and the camera tilted back, so that footage was fairly useless.

Since it’s a 360 camera, any tilt (in any direction) can be corrected. I’m doing that before I upload my images, with a combination of ffmpeg, ImageMagik and ExifTool.

Comment from b-unicycling on 28 January 2025 at 07:28

@Peter Bremer: Thanks for you comment. I deleted that sequence already, thankfully I’ll have another chance going that direction. Are there any how-tos or videos out there you would recommend to explain how to fix the centre of the 360 imagery? (I know there’s a word for it; I just can’t remember it.)

Comment from Peter Bremer on 3 February 2025 at 10:28

I should write a diary entry about it, but I never get around to it… 🙄

I use the Windows command-line, because it is quicker to just copy & paste code than clicking many buttons when there are many images to correct. (So I don’t know if there are any graphic programs that can do the same.)

There are two ways to go about this:

  1. Insert parameters into the image (metadata) to indicate how much the camera was tilted. This is very fast, as it doesn’t modify the actual image, but in my last test Mapillary didn’t support this at all and Panoramax mis-interpreted some of the parameters.
  2. Modify the actual image. This requires resampling the whole image and takes much more time, but it’s also much better supported as you basically create a new, corrected, image.

So I do the last, and I use the following apps: ffmpeg (https://www.ffmpeg.org), Exiftool (https://exiftool.org), and for Panoramax I also need ImageMagick (https://imagemagick.org). In addition I use RenderStuffs 360° Panorama Viewer (https://renderstuff.com/tools/360-panorama-web-viewer/) to view my images.

On the command-line, change into a folder that contains the photos (eg, cd 2025-01-01 if 2025-01-01 is the name of the folder). The converted images will be put in a subfolder convert, the original images won’t be modified, so that I can re-run the process if I discover I made a mistake. Here comes the magic:

md convert & cd convert & (for %a in (..\*.jpg) do ffmpeg -hide_banner -loglevel warning -i "%a" -vf v360=pitch=<pitch>:roll=<roll>:yaw=<yaw>:output=e -update 1 -qscale:v 2 -y "%~nxa") & magick mogrify -sampling-factor 4:2:2 * & exiftool -TagsFromFile ..\%f.jpg -overwrite_original .

Here you need to replace <pitch>, <roll> and <yaw> with the amount of tilt the images need to be corrected. You’re using the same amounts for the whole folder, so split up the folder if the tilt changed halfway. Pitch is the degrees the photo needs to be tilted up, from 90 to -90. If for example the camera was pointing straight up to the sky, you enter -90 for <pitch>, to correct the image downwards. Roll is tilt left/right, from 90 to -90, which corrects a slanted horizon (enter a positive roll to turn the horizon clockwise) and yaw is looking left/right, from 180 to -180, which corrects a straight road not going to the center of the image (enter a positive yaw to move the centre of the image to the right).

Now comes a final problem, Panoramax has trouble reading some of the rotated images. I need to run the following command in the folder of converted images:

magick mogrify -sampling-factor 4:2:2 *

It’s been a few months ago that I last did some adjusting, so I hope everything still works as it did back then.

Kudos to David G. of Trek View for his article that pointed me in the right direction: https://www.trekview.org/blog/calculating-heading-of-gopro-video-using-gpmf-part-2/

Comment from Peter Bremer on 3 February 2025 at 11:05

I see now that the last bit of code was already included in the long line of code, so you can ignore that last command:

magick mogrify -sampling-factor 4:2:2 *

Comment from b-unicycling on 3 February 2025 at 12:49

Thanks very much! I hope I won’t ever need to follow these instructions, but it’s good to have them.

Log in to leave a comment