NameError: name 'wgs84' is not defined in 1c-make-pix4d.py
See original GitHub issueHi again!
I’ve been trying to use this project on a custom aerial dataset (crop_field). I tried running 1c-make-pix4d.py
with
python3 1c-make-pix4d.py crop_field
and it yielded
Traceback (most recent call last):
File "/Users/ImageAnalysis/scripts/1c-make-pix4d.py", line 26, in <module>
pose.make_pix4d(image_dir, args.force_altitude, args.force_heading, args.yaw_from_groundtrack)
File "/Users/ImageAnalysis/scripts/lib/pose.py", line 229, in make_pix4d
wgs84.geo_inverse( cur[1], cur[2], next[1], next[2] )
NameError: name 'wgs84' is not defined
Am I missing a package or dependency? I’ve tried looking for a workaround but didn’t come across anything related
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
Converting EPSG:2263 to WGS84 using Python Pyproj
I'm trying to convert Projected bounds to WGS84 using Pyproj but getting strange results. The Projected Bounds are ...
Read more >coordinates conversion with pyproj - python - Stack Overflow
When I reverse and enter these coordinates in google maps they give me correct locations. So this is working fine. Now I have...
Read more >Getting Started - pyproj 3.4.1 documentation - GitHub Pages
Step 1: Inspect CRS definition to ensure proper area of use and axis order# · Step 2: Create Transformer to convert from CRS...
Read more >Transform Coordinates between Different Reference Systems ...
Transform Coordinates between Different Reference Systems using Python Pyproj Library |EPSG | WGS84 Transform Coordinates between Different ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, there is an issue there, the message is coming from the aura-props code when overlaying one tree on top of another. Likely the whole “mount” subtree is lost which means the project won’t default to the proper camera mounting (straight down.) I don’t fully understand why I haven’t seen this before and why this case isn’t accounted for in the aura-props code. I need to dig deeper and try to understand and refresh my memory on that, but I probably don’t have time today. For now I woudl recommend adding the following snippet to your ImageAnalysis/config.json file right after camera make, model lines (and before width):
The sequoia meta data for roll, pitch, and yaw is for the aircraft (and yaw is completely wrong all the time.) So you need to trigger the code --yaw-from-flighttrack and tell the system the mount offset of the camera when creating the pix4d.csv file.
My bad I should’ve been more clear about it. I meant the DJI dataset yields similar errors to the Sensefly dataset when I deleted the configuration files that came with them keeping only the images, to see if I could reproduce your results from scratch
When I run
It yields
And when I run
It yields this massive error
Which goes on until the last image