Forum

Author Topic: Geoid import problem. DHHN2016 (GCG2016)  (Read 3104 times)

JFakin

  • Newbie
  • *
  • Posts: 2
    • View Profile
Geoid import problem. DHHN2016 (GCG2016)
« on: February 09, 2023, 09:54:27 AM »
Hi I want to convert the picture coordinates to geographical CS UTM32 and vertical CS DHHN2016. The problem is that my Geoid for DHHN2016 is defined in ETRS89 and in Metashape I can only chose the Geographic CS for the Geoid that is the same in which it converts. So I can use the Geoid to convert to ETRS89 DHHN2016 but not UTM32 DHHN2016. Does anyone know how to solve this problem?

Geoid file (GCG2016.txt) sample:
55.979166667  3.44375 43.0990
55.979166667  3.45625 999999
55.979166667  3.46875 999999
55.979166667  3.48125 999999

Paulo

  • Hero Member
  • *****
  • Posts: 1323
    • View Profile
Re: Geoid import problem. DHHN2016 (GCG2016)
« Reply #1 on: February 13, 2023, 06:11:42 PM »
Hi JFakin,

i suggest you define ETRS89/UTM32 Projected CS and from there define the compound CS using the DHHN2016 geoid.. It should work..
Best Regards,
Paul Pelletier,
Surveyor

JFakin

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Geoid import problem. DHHN2016 (GCG2016)
« Reply #2 on: February 23, 2023, 12:08:37 PM »
Thanks for the Anwser. I did manage to import the Ascii file but the resulting Tiff File is plain white, and in a Test project with 6 GCP i get good 2d accuracy +-3cm but the Height is 4m off. Im speaking of using the GCPs as Controll Points and the Reference was onlly the fotos.  So i assume the Geodi wasnt imported correctly. I followede this instructions: https://agisoft.freshdesk.com/support/solutions/articles/31000148332-how-to-use-height-above-geoid-for-the-coordinate-system

« Last Edit: February 23, 2023, 12:14:31 PM by JFakin »

Paulo

  • Hero Member
  • *****
  • Posts: 1323
    • View Profile
Re: Geoid import problem. DHHN2016 (GCG2016)
« Reply #3 on: February 24, 2023, 05:26:51 PM »
Hi,

it should work. If your GCPs are referred to same Vertical datum then accuracy should be in cm range not m. Maybe double check your GCPs ...
Best Regards,
Paul Pelletier,
Surveyor