Thanks for asking! It’s really a no-brand camera. Something like this: https://www.aliexpress.com/item/4000166920293.html (there are many similar models)

I agree that Mapillary is super useful, and coverage is indeed sparse where I am. I’ve started looking into it. So far, I’m taking single shots at locations that I find interesting for surveying, and I’ve uploaded the odd pic or two.
That’s not really what Mapillary is about, though. I’d rather take videos and convert those to ‘tracks’ on Mapillary. I have yet to figure out how to convert videos from my cam to single pics at appropriate time steps, with proper timestamps given to images. After that, correlating with GPX and upload to Mapillary should be straightforward.

But first of all, I need to wait for a day when I have time to go on a bike ride at daylight hours, with decent weather ;) Looks like this could take a while.

Thanks for your feedback! I didn’t expect to have an audience here, would’ve chosen my words more carefully if I had ;)

But since you’re asking: yes, I did try the wizard within JOSM. Good stuff. That’s how I learned the basics of Overpass coding. Your use case #1 got me started on the more advanced stuff: Groningen, unfortunately, is an ambiguous term, both a city and the province surrounding it. The city, apparently, takes precedence, which is why that search comes up empty; I need the province instead. That’s why I started messing with admin_levels.

While we’re talking, may I ask a related question? If I put a rough bounding box around my area of interest, does that make it easier or harder for the database to handle my request? Or does it not make a difference?
Say, I want to search for features within the province of Groningen. If I restrict the search for admin boundary with appropriate level and name to a bounding box, does that increase or decrease the workload on the server? It doesn’t matter much to me personally, just trying to be a good citizen / trying not to waste CPU time.