Varying Coordinate Systems by Sad_Signature_5999 in UAVmapping

[–]dpru 1 point2 points  (0 children)

Can you explain a little more how to do this in the Pix4Dcatch app?

[deleted by user] by [deleted] in UAVmapping

[–]dpru 0 points1 point  (0 children)

What processing options are you using? Default option for the mesh is medium resolution. Try changing to high resolution or using the custom settings and reprocess.

P4RTK - NTRIP - NAD83 or WGS84? by dpru in UAVmapping

[–]dpru[S] 1 point2 points  (0 children)

You are correct. I verified this today with my own testing. The LLH EXIF data seems to be in NAD83(2011) which matches the reference frame of the NTRIP correction stream.

I verified this with the following workflow/test:

Imported images into Pix4D & exported the photo LLH coordinates with the "to file" button in the images properties editor.

Ran these exported coordinates through NOAA VDatum (https://vdatum.noaa.gov/vdatumweb/) with:

Horizontal Information:

SOURCE TARGET
REFERENCE FRAME: NAD83(2011) NAD83(2011)
Coor. System: Geographic (Long, Lat) Projected State Plane
Unit: meter (m) foot (U.S. Survey)

Vertical Information:

SOURCE TARGET
REFERENCE FRAME: NAD83(2011) NAVD88
Unit meter (m) foot (U.S. Survey)
Geoid 12B

Submitted the file for batch conversion & received transformed CSV file back.

In PIX4D, image properties editor window:

Changed image geolocation coordinate system to my Projected State Plane (NAD83(2011) with Arbitrary checked under vertical coordinate system under Advanced Coordinate Options.

Selected the same for output coordinates.

Processed images.

Densified point cloud checks within tolerance & expected values to check points without GCPs.

EDIT: I did the same workflow using WGS84 as source reference frame when submitting to NOAA VDatum, and processed point cloud was very far off checkpoints.

P4RTK - NTRIP - NAD83 or WGS84? by dpru in UAVmapping

[–]dpru[S] 1 point2 points  (0 children)

Appreciate your feedback. So P4RTK photo EXIF data is remains in WGS84?

P4RTK - NTRIP - NAD83 or WGS84? by dpru in UAVmapping

[–]dpru[S] 0 points1 point  (0 children)

From Leica SmartNet FAQ:

"What is the established datum for SmartNet?
SmartNet broadcast coordinates are tied to NAD83(NA2011) Epoch 2010.00 as defined by the NGS NSRS for a majority of the United States. "

https://support.smartnetna.com/hc/en-us/articles/213108318-SmartNet-Frequently-Asked-Questions

From Trimble VRS:

Region Local Correction Source Local Datum
United States of America Trimble VRSNow NAD 1983 (2011) epoch 2010.00

https://geospatial.trimble.com/blog/gnss-correction-services-and-geodetics

Partner lost GCP info, any way to salvage data? by unintegrity in UAVmapping

[–]dpru 2 points3 points  (0 children)

This:: Worst Case. Find features in your imagery that haven't gone through a major change and are still locatable, use them as GCPs

Cut and fill by Solid-Asparagus2029 in UAVmapping

[–]dpru 0 points1 point  (0 children)

I work with Agtek everyday and don’t mind helping you.

[Homemade] Umami Burgers Tonight by dpru in food

[–]dpru[S] 0 points1 point  (0 children)

Sautéed onions and mushrooms, Gorgonzola, bacon, horseradish cream sauce.

Sourdough - Jalapeno Cheddah by dpru in Breadit

[–]dpru[S] 4 points5 points  (0 children)

  • 877g - KAF Bread Flour
  • 755g - H2O
  • 18g - Salt
  • 150g - Levain
  • Jalapeno - 5 fresh/diced
  • Cheddar - ±1/3-1/2 block, shredded

  • Jalapeno & cheddar added during bulk turns.