topic Re: Drone2Map Project Units vs. Display in ArcGIS Drone2Map Questions

Drone2Map Project Units vs. Display

IaGeoff — Wed, 17 Aug 2022 12:36:50 GMT

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.

Re: Drone2Map Project Units vs. Display

JerryBartz — Wed, 17 Aug 2022 13:44:40 GMT

Did you input feet values in your table for control point elevation values?

Re: Drone2Map Project Units vs. Display

IaGeoff — Wed, 17 Aug 2022 14:01:07 GMT

Jerry, Absolutely. The Control Manager "Values" are correct, yet Property just says "Latitude" and "Longitude" despite the initial Project definition being defined.

What I'm wondering, when you Start a Project (Import Images, Define the Project Coordinate System, don't see where you define "UNITS" in that initial process. Only if you go to "Project -> Settings -> Units".

For this project, my Default Image Coordinate System was "GCS WGS 1984" and Z=EGM96 Geoid. Then defined desired "Project Coordinate System" at onset and Imported Control Points.

From the Processing Report, you can also see that the "Control" is clearly denotes as USft

Mean Reprojection Error / Sigma Naught (Pixel) 0.300 / 0.420
Ground Control Points RMSE (US ft) 0.004, 0.007, 0.005
Check Points RMSE (US ft) 0.015, 0.013, 0.011

Even shows as (US ft) in the Geolocation Details Table for report, for both the Ground CP's and the Check Points.

Re: Drone2Map Project Units vs. Display

JerryBartz — Wed, 17 Aug 2022 14:21:37 GMT

I have not had your problem, but I always input X, Y and Z values for control points; Z from a topo sheet..

Re: Drone2Map Project Units vs. Display

IaGeoff — Wed, 17 Aug 2022 14:45:44 GMT

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

Re: Drone2Map Project Units vs. Display

IaGeoff — Wed, 17 Aug 2022 15:02:10 GMT

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)

Re: Drone2Map Project Units vs. Display

IaGeoff — Thu, 25 Aug 2022 20:58:15 GMT

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.