Opencamera is pretty much the only app I use, the intervalometer function is essential. And depending what I am doing (personal survey and such, instead of recording for Kartaview/mapillary), I really dig the stamp GPS coordinate feature so that I don’t have to open image properties to check out the exif tags.

I set the shutter speed, ISO and aperture manually, usually setting high shutter speed since I need to minimize movement blur during capture from a moving car. Shooting perpendicular to car movement (at higher speed) is almost hopeless though since the sensor readout is too slow to prevent blurring small details like street names etc, especially house numbers.

Another bonus is the ability to trip the shutter through bluetooth. A cheapo bluetooth transmitter only costs pennies these days.

I also have a sony a6000 that provided fabulous photos with tons of details, but I am pretty scared to use it extensively. I fear that its internals will be shaken to bits by car vibrations.

One thing to check with Opencamera - infinity focus doesn’t necessarily work with all phones. On mine ( older Mi Max) it is blurry. I have to either set manual focus, or focus lock on a distant object to get sharp photos. Of course, the included factory camera app is sharper but lacks other features you mentioned for OSM photo surveying.

In josm you can open photos with gps information. When you select and open a whole bunch of them (say after a road trip), they’ll show up on their own layer. Sometimes, some of the photos doesn’t really match with the location shown against aerial imagery in JOSM, especially those taken from inside a moving car. You can adjust the photo layer offset etc, but doesn’t really apply in my case since most of the other photos are accurately gps tagged.

So, it’s not really gps tagging on OSM like you asked, rather using gps tagged photos in an OSM editor to improve the map.

in my experience ‘local knowledge’ sometimes just mean that they map it from Google streetview. :)

My take.

1) how poor is poor? if it’s off by 10 meters, might as well try again some other time with better gps setup. But if it is going to be the only gps track for the trail then just go for it.

2) don’t know who has the power to do the long overdue cleanup. Probably going to face some serious protest from those uploaders.

3) not appropriate. imo..

4) see #2

I wonder if it’s the individualism trait prevalent in western societies that prevents the adoption of an official structured tagging schemes – you know the me, me part. Especially considering this is an ‘open’ project which many takes it as every contribution is equal unlike a company like google which can dictate how their data is tagged.
It’s sad really, there’s no shortage of database experts in osm world (for example bushmank) who already laid out instances on how tagging schemes/structures should look like.

There is Kartacam which seems to provide more detailed photos but i don’t know whether they sell them to the public. Personally, with the above setup I’d forego the 360 thing and just use 4 images with different camera directions.

Wonder how you get the boundary data for the district? In my country I don’t think there is any officially available district boundary data, and even then somehow people drew them (i knew where they got them though).

takde gambor weh..

Nobody. You’re lucky if you can even bring this up in the community forum.

I’d mostly map what I think OSM is initially made for - vehicle navigation and the corresponding poi/landmarks that’s useful for it. Don’t plan to make it pretty, but just functional and light enough so that it can be used on older phones. That’s how I try to avoid burnout.

I don’t know whether the base station data is available for the public for free.

When I was in surveying, the official JUPEM gps/surveyed data and whatnot requires a subscription - $1k/year if I am not mistaken. A private correction signal (sms/gprs) based is also available presumably to customers that bought South gps survey sets although we saw a tiny difference in recorded values compared to JUPEM’s.

The problem is (if I understand the recent issue correctly) that osmose is giving warning about low poly rivers, hence any new-ish mappers might start smoothing out bends and stuff..

I would just map 3 leisure pitches = tennis and be done with that. I like simple stuff :)

I think Gopro uses a twin lens solution compared to multiple camera setup of the streetview car. A single lens covering 180deg will always have problems with distortion/blurriness on the edges with current technology.

Let’s hope that nobody turn into Reddit mods.

Well, that’s what my initial thoughts are. Except, all these ‘corrections’ are done by corporate mapper beyond the Pacific ocean. I wish I could be arsed to track down and check all the little funny edits that they make.

Sorry if it was unclear. The first venture was just plain gpx data.

After that at a different location, I averaged a point for 5++ minutes and collected GNSS data using android’s gnss tools, then trying to ‘post process’ the gnss.log file using the open source GNSS analysis software. Failed to install this software despite repeated tries and various solutions available online, so currently I am giving it a rest.

That’s a common fact (educated observation) of mapping in these regions - using data from Google. A lot more probably comes from Streetview. Partly due to ignorance of copyright laws, and partly due to #dontgiveashit mentality. The clever ones put source = local knowledge, and then who are you to judge where they get their info from?

A conundrum for DWG for sure. My suggestion is just let things be unless they are so obviously copied from Google. If for some unforeseen reason that ABC called for a strikedown on those edits, then purge and redo.

Just ban this user for shits and giggles..