After installing OSMTracker v0.7 on my Android SmartPhone on the Ides of March, then using it the next day for the first time, I discovered that not only did it not track (a touch of an existential issue for a GPS Tracker - how come no-one noticed that before?) but photos taken with the App also were lacking almost all GPS info within the metadata, making them useless for Mapillary.
~/DCIM/Camera$ identify -verbose IMG_20190316_092818.jpg | fgrep GPS
It was a short session and only 43 photos, but I did not want to waste them if it could be helped. Somewhere in my searching I came across two really old plugins for JOSM which worked to fix that absence:
My phone is a cheap model from Vodaphone (SmartPrime-7, model VFD 600, Andoid 6.0.1) and has been able to add a full set of GPS tags to the photos that it takes with the built-in utility from the get-go, let alone when using OSMTracker. Even so, after taking photos under OSMTracker-0.7 and exporting a GPX (track-file), even though the gpx contained lat/long/compass for each photo, the photos themselves did not.
April update: Location needs to be switched on for BOTH the smartphone and the camera. They are independent actions within my model.
Configure available plug-ins
We now have the ability to load photos on to JOSM as an Image layer and then to place the photos at the place where the photographer was standing, and to register the direction that the camera was facing. Those GPS details can then be placed into the file metadata. This is easy to do but, since it has to be done one-file-at-a-time and cannot be scripted, it is incredibly tedious to do (I only had 43 photos to process and it took me a couple of hours; imagine if there were 43,000 photos!).
This is the step-by-step:–
menu: File | Open…
Files of Type:
Image Files (*.jpg)
Correlate images with GPS track
menu: Windows | Layers…
Jump to next marker
Write coordinates to image layer
You will have spotted an option to mass-tag photos using a GPX track but that was NOT available to me since the track had failed as well. Sigh. Well, at least I got these 43 geo-tagged and later uplifted into Mapillary. Then Mapillary vandalised them with unnecessary blurs, again. So I used the blur editor, again, to remove all unnecessary blurs (most of them). And Mapillary completely ignored the fact that I had done this, so none of that work will be enacted, either. Again.
Well, that’s it for me with Mapillary. Does anyone have any other suggestions to replace Mapillary? What is OpenStreetCam like?
Comment from mds08011 on 11 April 2019 at 17:23
I enjoy using OpenStreetCam but you might be frustrated as it struggles with similar blurring issues: https://github.com/openstreetcam/openstreetcam.org/issues/162