v0.1.30-pre-alpha

v0.1.30-pre-alpha hotfix

Changes

• Significant improvements to user prompts and help text
• Fix output formatting when running using Windows
• Significant improvements and bug fixes which improve target resolution accuracy

Full Changelog: v0.1.29-pre-alpha...v0.1.30-pre-alpha

v0.1.29-pre-alpha

What's Changed

• Important fixes to formatting and operation on Windows computers
• Update documentation for parseImage.py, including recommendation to calibrate drone magnetometer (compass) before every flight
• Fix a formatting bug for SK42 Gaus Krüger output when the the last 5 digits are less than 10k (values now have leading zeros)

Full Changelog: v0.1.28-pre-alpha...v0.1.29-pre-alpha

v0.1.28-pre-alpha

What's Changed

• Remove GDAL library, replace with Python geotiff library by @mkrupczak3 in #19
• find_me_mode.py allow location to be changed during software operation by @mkrupczak3 in #20
• MAJOR REGRESSION: OpenAthena is no longer able to detect if a given GeoTIFF DEM file is rotated or skewed. This should not affect operation when using GeoTIFF clips of the SRTM dataset. Improper use of a rotated or skewed GeoTIFF DEM will now cause undefined software behavior, resulting in bad output values

Full Changelog: v0.1.27-pre-alpha...v0.1.28-pre-alpha

v0.1.27-pre-alpha

What's Changed

• Add find_me_mode.py: display targets' relative bearing, distance, and 𝚫elevation by @mkrupczak3 in #17

Changelog

Full Changelog: v0.1.26-pre-alpha...v0.1.27-pre-alpha

v0.1.26-pre-alpha

What's Changed

• Add Soviet SK-42 6° Gauss-Krüger Coordinates by @mkrupczak3 in #16
• Change interactive output format, provide SK-42 in degrees, minutes, seconds as well as Gauss-Krüger grid ref
• Underline grid values and altitude for both NATO and SK-42 interactive mode output to make user operation easier
• Fix a bug which causes image parsing to fail on images taken by Autel drones with newer firmware

Full Changelog: v0.1.25-pre-alpha...v0.1.26-pre-alpha

v0.1.25-pre-alpha

What's Changed

• Add a prominent warning about sensor inaccuracy when parsing data from Autel Robotics drone images
• SK-42 (A.K.A CK-42) soviet reference system support by @mkrupczak3 in #14
• Docker support

Changelog

Full Changelog: v0.1.24-pre-alpha...v0.1.25-pre-alpha

• Add prominent warning to parseImage.py output whenever using a Autel Robotics drone image. Sensor inaccuracy with this drone make can lead to in-accurate and potentially dangerous position resolutions cfa745d
• Add SK-42 (A.K.A CK-42) soviet reference coordinates to output c507f29
  • functionality adapted from this code by @rafasaurus licensed under the GPLv2
  • A.K.A "Krasovsky 1940 ellipsoid"
  • A.K.A "Systema koordinat"
  • A.K.A "Система координат 1942 года"
  • The SK-42 reference system is built on a different ellipsoidal projection than the common WGS84
  • Measured in degrees, but will differ from the corresponding WGS84 values
  • A legacy coordinate system established by the former Soviet Union in 1942
  • May be in use by multiple post-Soviet nations (and their militaries) with legacy maps, equipment, and processes
• Dockerfile support 2e3be05, 4e28b87, 6ed7417
  • Add a Dockerfile that can be used to build Docker images
  • image available at https://hub.docker.com/repository/docker/t3l3tubie/openathena/
  • Includes all dependencies, ready-to-go
  • May be useful for automation
  • ENTRYPOINT is python parseImage.py
  • mounts a VOLUME by default at /home/user
  • try it out:
    • docker pull t3l3tubie/openathena:v0.1.25-pre-alpha then docker run -it openathena cobb.tif
    • type DJI_0419.JPG then press the enter key
    • type done then press the enter key
    • can also be run in headless mode with command docker run openathena cobb.tif DJI_0419.JPG
    • output will be available as the file DJI_0419.ATHENA in the container's /home/user directory (and associated volume)
    • it is possible to mount your drone images and GeoTIFF files as a volume for use with OpenAthena running in a container

v0.1.24-pre-alpha

Changes

• Some important fixes to parseImage.py headless output mode
• Add experimental support for Autel and Parrot drone makes
• Add a prominent user warning for possible in-accurate target results from Autel photo(s) metadata
  • This is likely due to poor quality sensor data from this make, but not yet confirmed
• Add support for varied XMP metadata from images of varying firmware versions for Autel and Skydio drones
• Improve README.md and other documentation

Credit

• Thanks to numerous contributors for their assistance in providing good test images from various drone makes and models
  • LaunchedPix and somewhereinusa in the SkydioPilots forum:
  • Matt from Nebraska in the AutelPilots forum
  • reddit user /u/GeekOnTheWing, multiple Autel images, subreddit drones.reddit.com
  • Vaakefjell from 🇳🇴, in the ParrotPilots forum for good 🦜 drone image samples, model spec. information, and drone image metadata

See you space cowboy...

v0.1.23-pre-alpha

Minor release version

• Cleaned up project files and assets
• renamed geotiff_play.py to parseGeoTIFF.py to keep convention
• renamed playground directory to src
• replaced documentation images in kind

v0.1.22-pre-alpha

Changelog:

• Fix a bug that could result in incorrect results in rare cases for images taken by Skydio drones
• Fix a bug that could cause EXIF drone make data to fail to be recognized

v0.1.21-pre-alpha

Minor version update over v0.1.2

Changelog:

parseImage.py has been enhanced for extensibility. Skydio drone photos are now supported in addition to DJI. Skydio photo parsing is experimental and needs more testing