@eesger wrote:
SfM lat/lon not in API
With the API and the Mapillary JS a Mapillary.Viewer node has two lat/lon pairs
- the “Structure from Motion” lat/lon (default!)
- the original lat/lon
I red up on the SfM system (cool!) BUT
The information I get via json calls like:
$.getJSON("https://a.mapillary.com/v3/images?client_id="+client_ID+"&"+“closeto=”+lon+","+lat+"&radius=100",.…The lat/lon information are all “original” lat/lon values, NOT the SfM lat/lon values!
Wouldn’t it be much, much more logical to use the SfM values here also?
(or am I doing something wrong?)
example:
http://geoarchief.nl/mapillery-test.html
(shows original location on map: light blue and SfM location: dark blue)http://geoarchief.nl/mapillary.html
(the location information from the API are the dots in view, the link looks at the dot that should be below)…Now that I am on a roll with this post. SfM repositioning the lat/lon: cool!!
But if you guys are that smart to calculate the right lat/lon, why not automaticaly correct the horizon and compass angle along with it? The last link in this post clearly shows that the compass angle is a bit off (and that my camera isn’t that good… I know… but I am in a test phase here, planing on buying a good one, but first I want the basics to go right)
Lat/lon question
When the “Mapillary system” is that smart with re-positioning… is it necessary to spend (a lot of) time trying to have the EXIF data of the images set as good as possible?
)Posts: 20
Participants: 2