nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Voeg een instelling voor hoogte boven ellipsoïde toe voor RTK-foto's.

JamesBurton1

Ik zou graag een instelling voor hoogte boven ellipsoïde willen bij het opzetten van een nieuw project. Onze RTK-foto's verwijzen naar de ellipsoïdehoogte, maar ik wil dat onze 3D-producten worden uitgevoerd in orthometrische/geoidhoogten. Ze komen op de juiste hoogte uit bij gebruik van grondcontrole, maar ik wil niet bij elke klus grondcontrole hoeven te doen, vooral niet als de RTK er al zo goed uitziet. Het aanpassen van de hoogte na verwerking is geen volledige oplossing en is niet mogelijk voor alle producten. Als je die lagen dan publiceert, moet je die hoogteaanpassing opnieuw doen in AGOL. Ik wil mijn producten na verwerking op de juiste hoogte voor 3D-scènes hebben.<\/P>

Vind meer berichten getagd met

Closed

Status: Closed

Reacties

MarkBarker1

Hi @JamesBurton1 ,

When are you initially adding the imagery to the new project page what coordinate systems are you defining for the image coordinate system?

Assuming this is the same project you were posting about in the other community post, then you are currently accepting the default of GCS: WGS_1984/VCS: EGM96 Geoid. Your RTK drone is likely collecting in a specific vertical ellipsoidal coordinate system, so the first step before you do anything else would be to make sure that you are defining both horizontal and vertical image coordinate systems correctly.

Once the image coordinate system is defined, you would then define the project coordinate systems. Drone2Map will automatically apply a transformation when processing, so products go from the image coordinate system to this project coordinate system.

The difference between your RTK image vertical coordinate system (ellipsoidal) and the project vertical coordinate system (orthometric) is the height above ellipsoid. So, if you are seeing the offsets as you mention that would be the first thing to review.

Are you able to provide a processing report from a project processed without ground control?

Regards,

Mark

JamesBurton1

Hey @MarkBarker1,

Appreciate the reply, can't attach a PDF in an idea post. I am working with several projects at this point which were flown with RTK corrections from the State of Utah CORS network (TURN). I have processed my data using the default GCS (WGS_1984) and VCS (EGM96 Geoid). I am trying to output my data in PCS:NAD 1983 (2011) State Plane Utah Central Meters and VCS:NAVD88 Height (meters). I continually get an output that is 17 m, give or take, below the orthometric web scenes. I've stopped using the Fixed Images for RTK since it didn't appear to work, and it appears that would force my data to have an offset by using the ellipsoid height.

Beyond that configuration, I have tested other GCS and VCS like the TURN networks (NAD83 (2011)) to try and use an ellipsoidal VCS instead of the EGM96 Geoid. Keep getting this negative vertical offset unless I use ground control.

Feel free to follow up outside this thread.

James Burton

jburton@msd.utah.gov

JamesBurton1

This Idea is no longer needed. The solution to the ellipsoid to geoid projection not working is the following link. You must have the ArcGIS Coordinate System Data program installed. https://community.esri.com/t5/arcgis-drone2map-questions/rtk-ellipsoid-height-to-orthometric-geoid-height/m-p/1328360#M1382

Doe mee aan het gesprek

Meld je aan om te posten, content te volgen en meer. Nieuw hier? Registreer gratis.