Need to understand how it could be used for Mapillary (already asked help in support).
My first attempt was to use it as 360 (in horizontal plane) panoramic camera.
I wrote a converter to Equirectangular projection.
Here is result (original)
My current goal to use it as regular action camera, to crop a band across border ( pixel here are very low quality) and to transform some how from fish eye projection to good one for Mapillary.
mapillary has tools to undistort fisheye projections, however they might only be limited to known cameras/lenses.
I think there was some sort of 3rd party software available to remove the distortion as well
Hi @eesger and @4004
Thank you for joining this topic!
Converter is not too complex task as I used algorithm from Internet.
I already make test in Hugin, it looks not bad but I loose top 2 floor of the building.
@eesger will be your man for Hugin questions. it certainly can do batch processing, but might take a while depending on your pc.
it is a shame to not have panoramic view, but consider how usable it would be for what you plan to do with it. ultimately a high res 110fov image is better than a low res 220 in my book
I agree that it more nice to see the same count of pixel in lesser FOV.
But 180° panorama could provide correct direction of object on the left and right instead of all is ahead and it could be useful, e.g. when you would like to see the photo of amenity in OsmAnd.
It looks like quality became worse (if compare the same photo on panellum viewer).
Also there is black color on the back. Could Hugin generate not 360 panorama but partial?
Update 2019-12-16: The reason for quality was incorrect selected dimension. Now quality is almost the same as on raw photo from this camera. I will delete this photo because it is in wrong location and the same photo is published as part of sequence
Hmmm, hoped that the exif would contain 180 / 220 degrees… and/or that Mapillary would detect via the perfect black colour that it wasn’t a full 360…
I do not know if Mapillary detects this at a later point in time
when uploading 2:1 ratio images mapillary seems always interpret it as 360 pictures, even with my mobile phone using such resolution. I normally cut some pixels left/right to avoid perfect 2:1 ratio as I dont want to show it as 360 image
That’s correct. But you can define the viewing angle in EXIF also (among other things). So it should be possible to set a viewing angle of 180/200/220 (etc) degrees
After setting “Fit crop to images” on Sticher tab I received good photo without black area, metadata also has coorect value in GPano:CroppedAreaImageWidthPixels and GPano:CroppedAreaLeftPixels.
Now it is in processing but already could by viewed
Dimension is 3438x2825 pixel. Quality is good to see big house numbers.
Next step is apply template for several images in batch.
I created *.pto file for each images (using power shell script) and proceesed all succesful (initialy there was error
ERROR: Project file contains no images. > FATAL: (C:\Prog\Hugin\dynamic_vs2017\hugin-hg\src\hugin_base\panodata\Panorama.cpp:2177)
HuginBase::Panorama::readData(): (): Could not parse the data input successfully.
It was caused by unicode format of pto file, I fixed by adding “-Encoding ASCII” into powershell script.
Now I will continue investigate how to process a set of photo from camera to mapillary. I will post update when it will be ready.
@eesger please ignore my question from previous post, the reason was unicode encoding of file, it looks like Hugin could work only with ANSI, i fix it in powershell script.
For now I have uploaded 1 sequence
I will publish workflow instruction later.
A few conclusions:
It could be used for Mapillary if you already owns it or you are very limited in money and found it by lowest price (I bought it for 25$ at the end 2018)
It cannot be used for reading house addresses (there is example with 2 plates on the left and on the right side but both are unreadable )
You could use it for house levels, traffic signs and all other amenity (except any reading if distance longer then 2-3 m, you could found best result here)
It give us 180 degree by vertically and more then 180 (probably 190-200) degree by horizontally. So it show total picture of place better then regular smartphone shots.
I found Mapillary shows my partial panoramas in new way. Previously there was black colour but now it shows as full panorama without black screen, like they just cut out black scene and stretched my 200 degree to 360 degree. Geometric proportion was keeped, but sight direction is incorrect now.
I think it is wrong. That is why using such fish-eye cameras is less useful then previously.