Nice write up and thanks for the details!

Exactly there is no compatible copyright license for this data therefore it can’t be used in any way for OpenStreetMap. Even CC BY sources need a waiver to be compatible per highfligher74’s link to which sources are compatible.

Extend the vote period, ask for more people to vote? I’m not sure it does get tricky when there is almost equal split each way.

Which app did you use? It would be nice if OSMTracker for Android https://github.com/labexp/osmtracker-android supported logging a vibration value with each GPS location.

@RobJN That’s right the LG360 doesn’t include a GPS, so when using the official LG app it uses a wifi connection to grab the GPS coordinates from the phone and apply these to the photos.

However this was not reliable, often consecutive photos would get the same coordinates or there would be large gaps where the connection was lost, plus it wasted my phone battery by needing to leave bluetooth and wifi on.

So I save a GPS log with “OSMTracker for Android” and then use gpscorrelate-gui to add the geotagging back in to the images, it works much better.

Some tips for the LG 360 (R105)

1. The default wifi password is 00 followed by the last six digits of the serial number (also shown on the wifi access point name).
2. To reset the wifi password to the default, “hold down the power button and shutter button for about 4 seconds (there will be a beep)”

The documentation on creating a quick fix challenge is at https://github.com/osmlab/maproulette3/wiki/Creating-Quick-Fix-Challenges

I had the opposite conclusion about the built in GPS actually. I have a Sony HDR AS300 with inbuilt GPS but since the GPS accuracy is much worse than my phone GPS (which has the advantage of using Google’s wifi data to help get a position especially in the city’s urban canyon), combined with the faster battery drain with GPS enabled, I disable the inbuilt GPS, record a trace on the phone with “OSMTracker for Android” and use the gpscorrelate-gui program later. In hind sight the cheaper Sony AS50 was a better option (which works great).

An update since I posted this, I’ve also tested out mounting the 360 camera on a helmet, which I found works well too. Sample image https://www.mapillary.com/map/im/s4btF9pO_QKG-3WhuUulRw

Pros: * The camera is high enough to still capture a good view (not as high as a pole) * Your’ slightly more incognito compare to riding with a long pole. * Less worry about hitting tree branches

Cons: * Feels heavy on the head, but overall it’s okay.

I was originally worried about the tilt and head turning compared to on a pole, but to be honest most of the time you’re looking forward so I’m yet to see that as an issue.

For us, the hardest part was trying to block a moving target. Since a new account was added for every single POI they created.

I agree, which is one of the reasons we decided in Australia to just revert straight away. For me this is a big reason to maintain a central blacklist so at least we know which OSM usernames are linked to this kind of SEO spam.

It was a lot of effort to chase down the source of the edits, but I think it was worth it in the end.

I did think about this, but yes it would be a lot of effort. It was great that you were able to have some success doing this!

Just saw your SOTM US talk. We see the exact same thing here in Australia. Our local community decided we’ll immediately revert the changeset. The changesets all follow he same pattern so we are fairly sure this is the same dodgy SEO company and not the real business owner who maybe just made some mistakes.

I applaud your efforts to try to reform the source of these bad edits, as what we do now is really just a bandaid solution.

I would like to create blacklist of usernames that mappers can add to when they revert these changesets, so it’s easier to keep track, do you think that’s useful? Do you know of a list already?

By including the wikidata id on each object (like in this case), you’re then able to upload many photos to wikimedia commons and link to a selection of photos.

Great write up StephaneP, glad to see this getting more attention in the OSM world, indeed it’s an important problem.

Which solution to quite simply store not just lat,lon, but also time, as in time when those lat/lon coordinates where recorded from the GPS, or time epoch when the imagery was captured?

Then either client side or server side, all those coordinates from different datums could be transformed into a single epoch based on the local transformations and plate shifts.

I think this is called a dynamic datum, but the only real change OSM need to make is storing that time value for each coordinate.

I’m interested in checking this out, is there a link to your code?

Eventually you’ll run into the issues at https://blog.openstreetmap.org/2017/03/31/osm-plate-tectonics/

Shame we didn’t get permission to use the speed limit dataset

Based on the waiver osm.wiki/File:OSM_CCBY_Consent-MainRoadsWA.pdf we can use any CC BY 4.0 licensed dataset from https://catalogue.data.wa.gov.au/organization/main-roads-western-australia