You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 2, 2025. It is now read-only.
In the preceeding example, `12.35` is the western longitude bound, `41.8` is the southern latitude bound, `12.65` is the eastern most longitude bound, and `42` is the northernmost latitude bound of the rectangular area of the desired geoTIFF file.
20
+
In the preceeding example, `12.35` is the western longitude bound, `41.8` is the southern latitude bound, `12.65` is the eastern most longitude bound, and `42` is the northernmost latitude bound of the rectangular area of the desired GeoTIFF file.
21
21
22
22
To clean up stale temporary files and fix the cache in the event of a server error use:
23
23
@@ -33,4 +33,4 @@ The excellent elevation data set is generated by a technique known as [Synthetic
33
33
The dataset for the elevation API backing the `eio clip` was generated by the (Space) [Shuttle Radar Topography Mission](https://en.wikipedia.org/wiki/Shuttle_Radar_Topography_Mission#Highest_Resolution_Global_Release) conducted in the year 2000. In 2015 a high resolution global [digital elevation model](https://en.wikipedia.org/wiki/Digital_elevation_model), derived from the SRTM dataset, covering most of the world was released to the public without restriction. This DEM derived from the SRTM mission has a high resolution of 1-arc second (approx 30 meters). [Studies](https://www.sciencedirect.com/science/article/pii/S2090447917300084) have shown the vertical accuracy of the datapoints are very good, with error being observed to be within +/- 10 meters, despite the +/- 16 meters figure which was published in the SRTM data specification
34
34
35
35
## Improvement
36
-
OpenAthena can accept DEM geoTIFF files of higher resolution or accuracy than the SRTM dataset, if provided by the user. Newer synthetic aperature radar datasets and LIDAR datasests are likely availible to those with significant resources
36
+
OpenAthena can accept DEM GeoTIFF files of higher resolution or accuracy than the SRTM dataset, if provided by the user. Newer synthetic aperature radar datasets and LIDAR datasests are likely availible to those with significant resources
"pip3" and "python3" may just be called "pip" and "python" depending on the configuration of your system
@@ -110,16 +110,16 @@ This software is in pre-alpha and results are not guaranteed to be accurate. Use
110
110
111
111
### parseImage.py
112
112
113
-
[parseImage.py](./playground/parseImage.py) can perform automatic extraction and use of EXIF/XMP sensor information from drone photos. This allows for the automatic extraction and use of data including the aircraft camera's lat/lon, altitude, azimuth, and angle of declenation (theta). OpenAthena (if provided [terrain elevation data](./EIO_fetch_geotiff_example.md)) will extract and use these values automaticaly to find the location on the ground in the exact center of the image
113
+
[parseImage.py](./src/parseImage.py) can perform automatic extraction and use of EXIF/XMP sensor information from drone photos. This allows for the automatic extraction and use of data including the aircraft camera's lat/lon, altitude, azimuth, and angle of declenation (theta). OpenAthena (if provided [terrain elevation data](./EIO_fetch_geotiff_example.md)) will extract and use these values automaticaly to find the location on the ground in the exact center of the image
114
114
115
115
[](drone_sensor_data_blurb.md)
116
116
117
117
118
118
More info [**here**](drone_sensor_data_blurb.md)
119
119
120
-
### geotiff_play.py
120
+
### parseGeoTIFF.py
121
121
122
-
Run python geotiff_play.py (while in the playground directory) for a demonstration of [geoTIFF](https://en.wikipedia.org/wiki/GeoTIFF)[DEM](https://en.wikipedia.org/wiki/Digital_elevation_model) parsing. The file `Rome-30m-DEM.tif` is provided in the `playground` directory as an example. A DEM covering a customized area can be [easily obtained](./EIO_fetch_geotiff_example.md) using the python `elevation` API
122
+
Run python parseGeoTIFF.py (while in the src directory) for a demonstration of [GeoTIFF](https://en.wikipedia.org/wiki/GeoTIFF)[DEM](https://en.wikipedia.org/wiki/Digital_elevation_model) parsing. The file `Rome-30m-DEM.tif` is provided in the `src` directory as an example. A DEM covering a customized area can be [easily obtained](./EIO_fetch_geotiff_example.md) using the python `elevation` API
123
123
124
124
125
125
(counterintuitively, the x and y axis are backwards in the standard notation of a position via [latitude , longitude])
@@ -128,8 +128,8 @@ Run python geotiff_play.py (while in the playground directory) for a demonstrati
128
128
129
129
130
130
```
131
-
user@mypc:~/projects/OpenAthena/playground$
132
-
python geotiff_play.py
131
+
user@mypc:~/projects/OpenAthena/src$
132
+
python parseGeoTIFF.py
133
133
```
134
134

135
135
@@ -142,10 +142,10 @@ Then, exit the picture window that appears. You will now be prompted in the comm
142
142
getTarget.py searches along the constructed line (emmitted from the camera center) for a terrain match
143
143
144
144
145
-
To start, `cd` into the `playground` directory, then run getTarget.py:
145
+
To start, `cd` into the `src` directory, then run getTarget.py:
@@ -156,7 +156,7 @@ Which GeoTiff file would you like to read?
156
156
Enter the GeoTIFF filename:
157
157
```
158
158
159
-
You can clip [your own geoTIFF file](./playground/EIO_fetch_geotiff_example.md) from the [elevation API command line](http://elevation.bopen.eu/en/stable/quickstart.html#command-line-usage), or just use the provided example file `Rome-30m-DEM.tif` which contains the elevation data of the city of Rome, Italy and its outlying area
159
+
You can clip [your own GeoTIFF file](./EIO_fetch_geotiff_example.md) from the [elevation API command line](http://elevation.bopen.eu/en/stable/quickstart.html#command-line-usage), or just use the provided example file `Rome-30m-DEM.tif` which contains the elevation data of the city of Rome, Italy and its outlying area
Google Maps: https://maps.google.com/?q=33.835283,-84.521997
222
222
223
223
NATO MGRS: 16SGC2930646654
224
+
MGRS 10m: 33TUG03953105
225
+
MGRS 100m: 33TUG039310
224
226
225
227
```
226
228
@@ -246,7 +248,7 @@ The values should be tested for correctness and not totally relied upon in the c
246
248
`Google Maps:` a link to the previous lat/lon on Google Maps. Each rounded to 6 decimal places
247
249
248
250
249
-
`NATO MGRS:` represents the target location in the [NATO Military Grid Reference System (MGRS)](https://en.wikipedia.org/wiki/Military_Grid_Reference_System), which is simmilar to [UTM](https://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system). This coordinate system does not include the altitude of the Target
251
+
`NATO MGRS:` represents the target location in the [NATO Military Grid Reference System (MGRS)](https://en.wikipedia.org/wiki/Military_Grid_Reference_System), which is simmilar to [UTM](https://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system). This coordinate system does not include the altitude of the Target
Copy file name to clipboardExpand all lines: drone_sensor_data_blurb.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ The consumer models of some drones do not display their position, altitude, came
4
4
5
5
### parseImage.py
6
6
7
-
[parseImage.py](./playground/parseImage.py) has an experimental feature for automatic extraction and use of EXIF/XMP sensor information from drone photos
7
+
[parseImage.py](./src/parseImage.py) has an experimental feature for automatic extraction and use of EXIF/XMP sensor information from drone photos
8
8
9
9
parseImage.py can be run in an **interactive** mode, or **headless** mode based on how many arguments are given after `python parseImage.py`. **Interactive** is designed for use by humans with one or more images, **headless** is designed for use by automation with one or more images. The output of **headless** mode is subject to change in future versions
10
10
@@ -27,7 +27,7 @@ python parseImage.py bartow.tif
27
27
28
28

29
29
30
-
Enter the full file path of the drone image if it is not in the `playground` directory. Otherwise, just input the image filename and press **RETURN**
30
+
Enter the full file path of the drone image if it is not in the `src` directory. Otherwise, just input the image filename and press **RETURN**
31
31
32
32
Multiple images can be processed at once in **interactive** mode. When you're finished inputing images, type **`done`** to begin processing
0 commit comments