Drone2Map Project Units vs. Display

Question

Using 2022.1.1 most current, and have great Model products using GCP's and Check Points.  Defined Project Coordinate System clearly at start in "UsFt" (Projected) and correct Z (Height) in UsFt.  After processing the DEM/DTM, checking a Point location is showing the Values are in METERS..... yet in fact they are the Correct for "UsFt".

Simply put, what have I missed to have Mensuration Results saying in METERS when the values are truly USFT ?  Attached image clip from project, and you can see the USFT curser values are SAME as the Mensuration Results that say METERS (± given pick point).

Having same issue with the Orthomosaic, and the 3D Point Cloud.

When I push output data to OpenRoads Designer (MicroStation DGN), the header units are saying METERS, so imports are not being placed correctly.

Any assistance on where I've defined incorrectly would be appreciated. Thanks, in advance.

Drone2Map-Hwy144-DTM_Units.gif

IaGeoff · Answer

Just to post for reference, if used a respective SPC (State Plane projection) in Meters, project data Exported and correctly Reprojected into DGN to UsFt in different projection desired (an Iowa RCS Zone).  Appears someone else in our organization ran into same issue as well...... so thought I'd mention.

IaGeoff · Answer

Thought I'd add details from the Processing Report (as defined for Project), just to support the DTM values that state METERS.... yet are truly the Projection defined in UsFT.

Coordinate Information
Image Coordinate System GCS_WGS_1984/VCS:EGM96 Geoid
Project Coordinate System NAD_1983_(2011)_IaRCS_zone_7/VCS:NAVD88 height (ftUS)
Control Points Coordinate System NAD_1983_(2011)_IaRCS_zone_7/VCS:NAVD88 height (ftUS)

IaGeoff · Answer

Appreciate reply, and comparison of Inputting Values vs. Importing file.   Definitely appreciate time.