Hi FabKzo, Am Freitag, 10. November 2017 00:16:19 UTC+1 schrieb FabKzo: > > You're right but the farthest I see, the greatest the error : report an > error of 3cm per pixel at 20km on a 10k px wide pano , and you'll get a > difference of 300 meters for the whole distance represented by the v/hfov . > While working with 0.01 it would only represent 30 meters, which is > negligible for such distance, from my point of view ... >
You have already corrected it. So with current resolution of 0.1 deg you get 30 m resolution at 20 km distance on 10000 wide pano. So these 30 m apply to a spacing of nearly 50 km!!! So I think these are only numerical values. In praxis you won't achieve this resolution. There are * air movement * inaccuracy in your equipment (how good is the lens corrected and how precise is this distortion known, focus breathing, ..) * a photo is always a 2D projection of a 3D space. With our example (50 km spacing between point A and B, and this spacing in 20 km distance): if the distance from camera to point A differs by only 40 m (on 31 km distance) the spacing between A and B changes by 30 m. This is the resolution above. So I don't think you won't get this resolution from a (standard) photo. To achieve this high resolution you will probably need other devices (e.g. a theodolit) and do several measurements from different points. So IMHO the displayed resolution is more then high enough. Thomas -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/4da4b496-d7ac-4b87-8e4c-80e4d009630e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
