GCP interface WGS84 LAT/LON loosing decimal places


#1

File Containing My Ground Control in WGS84 EPSG 4326:

+proj=longlat +datum=WGS84 +no_defs
-93.093155866304 34.425438198628 135.972323823458 1655.87 1000.59 DSC00798.JPG 4
-93.093155866304 34.425438198628 135.972323823458 1977.85 2119.13 DSC00797.JPG 4
-93.093155866304 34.425438198628 135.972323823458 1785.70 3058.08 DSC00818.JPG 4
-93.092677448247 34.425650221945 135.776944647647 1516.74 2419.22 DSC00801.JPG PLStrip
-93.092677448247 34.425650221945 135.776944647647 1329.68 1375.76 DSC00802.JPG PLStrip
-93.092677448247 34.425650221945 135.776944647647 2019.79 1576.71 DSC00815.JPG PLStrip
-93.092108529526 34.425955574617 134.981711777615 1547.12 1729.01 DSC00807.JPG PumpStation
-93.092108529526 34.425955574617 134.981711777615 1882.35 2330.70 DSC00809.JPG PumpStation
-93.092108529526 34.425955574617 134.981711777615 1738.79 1256.34 DSC00810.JPG PumpStation
-93.092420870471 34.425391808292 134.205376737381 1328.27 2635.81 DSC00822.JPG 3
-93.092420870471 34.425391808292 134.205376737381 1098.61 604.72 DSC00824.JPG 3
-93.092420870471 34.425391808292 134.205376737381 2465.55 2287.95 DSC00831.JPG 3
-93.092420870471 34.425391808292 134.205376737381 4292.84 2094.18 DSC00833.JPG 3
-93.092420870471 34.425391808292 134.205376737381 4143.53 1305.02 DSC00834.JPG 3
-93.09224178135 34.425548178913 133.851499634236 1927.48 2551.29 DSC00824.JPG 1
-93.09224178135 34.425548178913 133.851499634236 1771.60 1541.38 DSC00825.JPG 1
-93.09224178135 34.425548178913 133.851499634236 1549.76 675.64 DSC00826.JPG 1
-93.09224178135 34.425548178913 133.851499634236 1772.65 2722.77 DSC00829.JPG 1
-93.09224178135 34.425548178913 133.851499634236 1753.19 1395.86 DSC00830.JPG 1
-93.09224178135 34.425548178913 133.851499634236 1772.33 248.47 DSC00831.JPG 1

After matching images to My GCP file I Export (save) the new GCP file containing GCP’s and x, y from images:

+proj=longlat +datum=WGS84 +no_defs
-93.09 34.43 135.972323823458 1655.87 1000.59 DSC00798.JPG 4
-93.09 34.43 135.972323823458 1977.85 2119.13 DSC00797.JPG 4
-93.09 34.43 135.972323823458 1785.70 3058.08 DSC00818.JPG 4
-93.09 34.43 135.776944647647 1516.74 2419.22 DSC00801.JPG PLStrip
-93.09 34.43 135.776944647647 1329.68 1375.76 DSC00802.JPG PLStrip
-93.09 34.43 135.776944647647 2019.79 1576.71 DSC00815.JPG PLStrip
-93.09 34.43 134.981711777615 1547.12 1729.01 DSC00807.JPG PumpStation
-93.09 34.43 134.981711777615 1882.35 2330.70 DSC00809.JPG PumpStation
-93.09 34.43 134.981711777615 1738.79 1256.34 DSC00810.JPG PumpStation
-93.09 34.43 134.205376737381 1328.27 2635.81 DSC00822.JPG 3
-93.09 34.43 134.205376737381 1098.61 604.72 DSC00824.JPG 3
-93.09 34.43 134.205376737381 2465.55 2287.95 DSC00831.JPG 3
-93.09 34.43 134.205376737381 4292.84 2094.18 DSC00833.JPG 3
-93.09 34.43 134.205376737381 4143.53 1305.02 DSC00834.JPG 3
-93.09 34.43 133.851499634236 1927.48 2551.29 DSC00824.JPG 1
-93.09 34.43 133.851499634236 1771.60 1541.38 DSC00825.JPG 1
-93.09 34.43 133.851499634236 1549.76 675.64 DSC00826.JPG 1
-93.09 34.43 133.851499634236 1772.65 2722.77 DSC00829.JPG 1
-93.09 34.43 133.851499634236 1753.19 1395.86 DSC00830.JPG 1
-93.09 34.43 133.851499634236 1772.33 248.47 DSC00831.JPG 1

The Lat and LON have lost significant precision


#2

I’d recommend using UTM as a CRS for GCPs. We have some work to do to improve GCP support and this is one of the problems. https://github.com/OpenDroneMap/OpenDroneMap/issues/828

Can you convert the coordinates to UTM and try again?


#3

Yep, Thanks


#4

It processed using UTM, but as on the other post, I’m back to the scale being off:

image

Again, X and Y dropped to only 2 decimal places

My GCP file:

+proj=utm +zone=15 +datum=WGS84 +units=m +no_defs
3 491507.911389015 3809328.08667974 134.2
PLStrip 491484.361944006 3809356.76260682 135.78
PumpStation 491536.66764989 3809390.57422016 134.98
1 491524.382773379 3809345.4109657 133.85
4 491440.381027897 3809333.2925389 135.97

GCP file generated from WebODM:

+proj=utm +zone=15 +datum=WGS84 +units=m +no_defs
491507.91 3809328.09 134.2 4144.64 1304.98 DSC00834.JPG 3
491507.91 3809328.09 134.2 1328.18 2636.61 DSC00822.JPG 3
491507.91 3809328.09 134.2 1100.54 604.75 DSC00824.JPG 3
491507.91 3809328.09 134.2 2467.37 2289.96 DSC00831.JPG 3
491507.91 3809328.09 134.2 4294.50 2094.75 DSC00833.JPG 3
491440.38 3809333.29 135.97 1656.81 1001.08 DSC00798.JPG 4
491440.38 3809333.29 135.97 1978.99 2118.70 DSC00797.JPG 4
491440.38 3809333.29 135.97 1786.00 3057.25 DSC00818.JPG 4
491484.36 3809356.76 135.78 1516.61 2420.56 DSC00801.JPG PLStrip
491484.36 3809356.76 135.78 1329.88 1375.55 DSC00802.JPG PLStrip
491484.36 3809356.76 135.78 2019.00 1576.46 DSC00815.JPG PLStrip
491536.67 3809390.57 134.98 1545.61 1729.21 DSC00807.JPG PumpStation
491536.67 3809390.57 134.98 1882.75 2330.25 DSC00809.JPG PumpStation
491536.67 3809390.57 134.98 1739.73 1257.14 DSC00810.JPG PumpStation
491524.38 3809345.41 133.85 1771.29 1540.42 DSC00825.JPG 1
491524.38 3809345.41 133.85 1549.62 673.37 DSC00826.JPG 1
491524.38 3809345.41 133.85 1773.30 2721.77 DSC00829.JPG 1
491524.38 3809345.41 133.85 1753.26 1395.95 DSC00830.JPG 1
491524.38 3809345.41 133.85 1773.50 250.75 DSC00831.JPG 1


#5

Both the scale and coordinate precision issues look like bugs. Could you open an issue on https://www.github.com/OpenDroneMap/WebODM/issues attaching a copy of the images + GCP file (and options used to process the dataset)?


#6

I corrected the GCP file to reflect accurate (more than 2 decimal places) and am processing now. I’ll post the results in a few minutes.

UPDATE: Same result, I can see the difference the more accurate GCP’s make, yet the scale is still off.