Hi Thomas,
We're working with gps ( with ~3m error) to limit that and we can have a
lot of precise positionned landmarks at such distances ( above 20 kms) to
adjust our panos on 180° hfov with ~125px/degrees for the less resoluted,
that's why we can note and correct those errors ; the work is gre
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/hf
I correct my error : at this resolution working with 0.01° should represent
~3.5 meters at 20km...
--
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
Hi Thomas,
I use Hugin since version 2009 - and I never saw that :-/
But we are talking from different things: this is the angle per pixel, but
> HFOV is the angle for the full pano. If you pano is not only 10 pixels wide
> the resolution per pixel is better then a hundredth of a degree given the
Hi Gunter,
Am Donnerstag, 9. November 2017 20:02:02 UTC+1 schrieb Gunter Königsmann:
>
> But you are right in the last nightly build in the "move" tab of the
> fast panorama preview there no more are arrows for the angle.
>
The thread opened has written from the field of view. Nobody mentioned
Hi FabKzo,
Am Donnerstag, 9. November 2017 19:59:31 UTC+1 schrieb FabKzo:
>
> Indeed I just have tested with Hugin 2017.0.0.eac5e8cc546e and it indeed
> does display fov with thenth degree rounded - and that's very cool ; I was
> previously on 2014 then 2016 versions.
>
But this hasn't changed l
> @Gunter: I don't know to which arrow buttons you refer. Or are you
> referring to the slider in the fast preview window? A change of 1 deg in
> fov translate to change in the pixel range when relating to the monitor
> width (this is what you see in the fast preview window). So a step width
> of 0
Hi T.Modes,
Indeed I just have tested with Hugin 2017.0.0.eac5e8cc546e and it indeed
does display fov with thenth degree rounded - and that's very cool ; I was
previously on 2014 then 2016 versions.
But I'm working with distances equiv. to ~20km , at this distance a simple
pixel represents ~ 3.5 m
Hi,
sorry.
Some people seems to be using another Hugin version. Current version is
displaying fov for the the pano to tenth degree rounded (not truncated!).
This is IMHO more than precise.
And there seems to be excessive expectation to the precision.
One example: Take a pano 1 pixels wide (a
I also consider useful to have more/configurable display precision, also
for translations (TrX, TrY, camera). Would help to clone & place missing
sky patchs and especially not well shot nadirs.
2017-11-09 8:28 GMT-02:00 bugbear :
> Fabrice Kerzerho wrote:
>
>> @Sean : Many thanks, I'll try i
Fabrice Kerzerho wrote:
@Sean : Many thanks, I'll try it asap . Would be great to be a display option
in expert mode; how can I ask for it?
@Gunter : Cool to discover that someone else need it ; I would increase it to
work with hundredth of degrees : the farthest the objects are in my panoramas
@Sean : Many thanks, I'll try it asap . Would be great to be a display
option in expert mode; how can I ask for it?
@Gunter : Cool to discover that someone else need it ; I would increase it
to work with hundredth of degrees : the farthest the objects are in my
panoramas the accuratest I have to be
Actually (perhaps because panoramas tend to be quite big, not sure) the
arrows that change the angle by a full degree at a time always are a little
bit too coarse to be useless => one Democratic vote from me, too, to
display another digit and to make the arrows change the angles only by a
tenth of
On Wed, Nov 08, 2017 at 10:44:12AM +0100, Fabrice Kerzerho wrote:
> Hi,
>
> No, I mean displaying decimal angular values for the whole panorama, not
> for each photos; I work in expert mode with a French interface - I may have
> done a bad translation. I need accurate angular values to conform a
>
Hi,
No, I mean displaying decimal angular values for the whole panorama, not
for each photos; I work in expert mode with a French interface - I may have
done a bad translation. I need accurate angular values to conform a
topographic grid on a panorama, I have to work with decimal values.
BR,
On
On 11/07/2017 06:41 PM, Sean Greenslade wrote:
On Tue, Nov 07, 2017 at 12:58:57AM -0800, FabKzo wrote:
Hi all,
Could it be possible to perform this type of modification in the interface ?
In fact I need complete angular datas with decimal values to work on
panoramas I produce; while all decim
On Tue, Nov 07, 2017 at 12:58:57AM -0800, FabKzo wrote:
> Hi all,
>
> Could it be possible to perform this type of modification in the interface ?
>
> In fact I need complete angular datas with decimal values to work on
> panoramas I produce; while all decimal values are considerated to
> cal
Hi all,
Could it be possible to perform this type of modification in the interface ?
In fact I need complete angular datas with decimal values to work on
panoramas I produce; while all decimal values are considerated to
calculate panoramas pixel width and height with no problem ( I can apply
18 matches
Mail list logo
