Re: [Therion] 3D model height

2021-02-23 Thread Balambér Hakapesz
The problem was that Therion used the Proj5 to transform the altitude even if it was above sea level, which did not need to be changed. This is now resolved. Balázs. On Tue, Feb 23, 2021 at 5:05 PM Balambér Hakapesz wrote: > A probléma abban volt, hogy a Therion a Proj5 segítségével akkor is >

Re: [Therion] 3D model height

2021-02-23 Thread Balambér Hakapesz
A probléma abban volt, hogy a Therion a Proj5 segítségével akkor is transzformálta a magasságot ha az tenger szint feletti magasság volt, amit nem kell változtatni. Ez most megoldódott. Balázs. On Tue, Feb 23, 2021 at 2:54 PM Martin Sluka via Therion wrote: > I’m not sure about your problem,

Re: [Therion] 3D model height

2021-02-23 Thread Martin Sluka via Therion
I’m not sure about your problem, but as I find the most accurate heights are those from DMR5 models for Slovakia and Czechia. But there are differences between DMR3 and DMR5 as you may see on screenshot. Martin ___ Therion mailing list

Re: [Therion] 3D model height

2021-02-22 Thread Balambér Hakapesz
No problem - just permission. On Mon, Feb 22, 2021 at 11:14 PM Balambér Hakapesz wrote: > 67fffb0 installation does not work on Windows7 > > Balázs. > > On Mon, Feb 22, 2021 at 10:28 PM Balambér Hakapesz < > holl.balaz...@gmail.com> wrote: > >> No, the issue is the difference between the

Re: [Therion] 3D model height

2021-02-22 Thread Balambér Hakapesz
67fffb0 installation does not work on Windows7 Balázs. On Mon, Feb 22, 2021 at 10:28 PM Balambér Hakapesz wrote: > No, the issue is the difference between the altitudes of the mean sea > level (geoid) and the ellipsoidal coordinates. > > Balázs. > > On Mon, Feb 22, 2021 at 10:22 PM Benedikt

Re: [Therion] 3D model height

2021-02-22 Thread Balambér Hakapesz
No, the issue is the difference between the altitudes of the mean sea level (geoid) and the ellipsoidal coordinates. Balázs. On Mon, Feb 22, 2021 at 10:22 PM Benedikt Hallinger wrote: > As far as i understood, when you tag your data to be in a certain > coordinate system that should include

Re: [Therion] 3D model height

2021-02-22 Thread Benedikt Hallinger
As far as i understood, when you tag your data to be in a certain coordinate system that should include all three data points when the coordinate system defines them. If you want an altitude offset, i would expect that we must manually convert. As an example: i tag my data to be wsg89, which

Re: [Therion] 3D model height

2021-02-22 Thread Tarquin Wilton-Jones via Therion
> If there is a real need for a switch between converting and not > converting the heights, let us know. At least here in the UK, a lot of rough and ready surveys seem to use Garmin handheld GPS units like the 66sr. These use barometric altitude, which you calibrate to a local benchmark. That

Re: [Therion] 3D model height

2021-02-22 Thread Balambér Hakapesz
Yes, it is necessary, we are forced to cheat at the Hungarian EOV coordinates. Thanks. I'm looking forward to the Windows installer. Balázs. On Mon, Feb 22, 2021 at 9:19 PM Martin Budaj wrote: > Hi, > > Proj 4 and 5 uses a different conversion than Proj 6+ resulting in the > height difference.

Re: [Therion] 3D model height

2021-02-22 Thread Martin Budaj
Hi, Proj 4 and 5 uses a different conversion than Proj 6+ resulting in the height difference. Actually, the behaviour of Therion was inconsistent: when doing internal conversions it transformed only x and y coordinates, but when creating e.g. KML output it transformed all x, y and z coordinates.

Re: [Therion] 3D model height

2021-02-19 Thread Balambér Hakapesz
therion 5.5.7+0df52bd+dev (2021-02-18) - using Proj 5.1.0, compiled against 5.1.0 On Fri, Feb 19, 2021 at 8:40 PM Balambér Hakapesz wrote: > latest Therion 5.5.7 (now install): > > > 19.00961011626948,47.52649337576408,*291*.08568208824045 >

Re: [Therion] 3D model height

2021-02-19 Thread Balambér Hakapesz
latest Therion 5.5.7 (now install): 19.00961011626948,47.52649337576408,*291*.08568208824045 19.00961011450532,47.52649337534078,281.08568208855468 19.00962225574169,47.52658294585592,281.08562306819113 19.00975449765885,47.5265747689,281.08549506128293 On Fri, Feb 19, 2021 at 8:19 PM

Re: [Therion] 3D model height

2021-02-19 Thread Martin Budaj
Hi, which version of Therion and Proj are you using? I get 19.00961002698361,47.52649340144701,262.00 in the kml export with the latest Therion and Proj 7.2.1 Best wishes Martin On Fri, Feb 19, 2021 at 11:25 AM Balambér Hakapesz wrote: > thconfig: > #cs long-lat > #fix 0

Re: [Therion] 3D model height

2021-02-19 Thread Benedikt Hallinger
Well then i'm out of ideas, however i do not get weird results here when invoking proj manually: echo "647151 242509 262" | cs2cs EPSG:23700 EPSG:4326 47d31'35.376"N 19d0'34.596"E 262.000 echo "47.526453 19.009617 262" | cs2cs EPSG:4326 EPSG:23700 647151.52 242504.51 262.00 When using

Re: [Therion] 3D model height

2021-02-19 Thread Balambér Hakapesz
The error only occurs when using the EOV (EPSG: 23700) coordinate system. Mentes a vírusoktól. www.avg.com

Re: [Therion] 3D model height

2021-02-19 Thread Balambér Hakapesz
# 2021.02.08 created by TopoDroid v 5.0.79 #source "../th/kml.th" source "kml.th" layout topodroid legend on symbol-hide group centerline symbol-show point station debug station-names endlayout export map -layout topodroid -o kml-p.pdf -proj plan export map -layout topodroid -o

Re: [Therion] 3D model height

2021-02-19 Thread Benedikt Hallinger
What does the survex/aven file give you, is the error there also apparent? What is your full thconfig file for generating the kml and aven .3d? Dies the problem also exists when specifying this: cs EPSG:4326 fix 0 19.009617 47.526453 262 Am 2021-02-19 11:25, schrieb Balambér Hakapesz:

Re: [Therion] 3D model height

2021-02-19 Thread Balambér Hakapesz
If I were to enter the ellisoid height, the error of Proj4 would still remain on the EOV projection. I could work in a UTM coordinate system, but it would be much simpler if Therion didn’t recalculate anything. (There is no height issue between UTM and WGS84 because there is no conversion) This

Re: [Therion] 3D model height

2021-02-19 Thread Balambér Hakapesz
thconfig: #cs long-lat #fix 0 19.009617 47.526453 262 cs EPSG:23700 # Hungarian EOV fix 0 647151 242509 262 kml: 19.00961011626948,47.52649337576407,291.08568208889801 291-262 = 29 m = 44m geoid height - 15m Proj4 error

Re: [Therion] 3D model height

2021-02-19 Thread Benedikt Hallinger
Isn't EGM84 the reference ellipsoid currently used by WGS84? What you get with GPS is *not* sea level, but the altitude above that reference geoid (which takes into account gravital anonalys). If you calibrate your barometric altimeter to the hieght given by a height coordinate of WGS84 (like

Re: [Therion] 3D model height

2021-02-19 Thread Balambér Hakapesz
Very rarely can anyone work at ellipsoidal heights. In local coordinate systems, it only makes sense for upper geodetic calculations. Only for GPS measurements we get an ellipsoidal altitude, even there the devices can immediately calculate the altitude of the EGM96 model with an altitude above

Re: [Therion] 3D model height

2021-02-19 Thread Benedikt Hallinger
Hi there, if you measure the altitude with a barometric device, you do not get the altitude above the ellipsoid. You have to account for that at the input of your data. With the "cs" command you define your input data to be in a specific coordinate system, and also your altitude has to be

[Therion] 3D model height

2021-02-18 Thread Balambér Hakapesz
Hi! When generating 3D models, Proj4 transforms between different coordinate systems. This also transforms the ellipsoidal altitude, but the data always refer to altitude above sea level and should not be changed. The finished models do not fit the topography, you have to cheat with the height to