Changes between Version 12 and Version 13 of Processing/laguserguide

Timestamp:

May 24, 2012, 4:07:45 PM (13 years ago)

Author:

jaho

Comment:

--

Processing/laguserguide

@@ -62 +62 @@
 LAG currently supports UTM and latlong (or longlat: x = longitude, y = latitude) projections. By default files in both formats will be displayed using UTM coordinates. You can change it by going to //Tools >> Use latlong coordinates//.
 
-Latlong is generally a preferred projection because it doesn't require additional zone information. Latlong files can be saved as both latlong and UTM, while UTM files should not be converted, unless they contain projection information in the header's VLR geo keys. Alspp produced UTM files don't contain this information so this conversion should be avoided for the time being. Also latlong files seem to have higher precision than UTM files (up to about a 10th of a milimeter), which is probably much higher than the actual lidar precision. By default this values are rounded to precision of 1 centimeter when converting latlong to UTM. To prevent precision loss you can select // Use full precision // option on file saver dialog, however this will result in slightly bigger files.
+Latlong is generally a preferred projection because it doesn't require additional zone information. Latlong files can be saved as both latlong and UTM, while UTM files should not be converted, unless they contain projection information in the header's VLR geo keys. Alspp produced UTM files don't contain this information (they do but under wrong GeoKey) so this conversion should be avoided for the time being. Also latlong files seem to have higher precision than UTM files (up to about a 10th of a milimeter), which is probably much higher than the actual lidar precision. By default this values are rounded to precision of 1 centimeter when converting latlong to UTM. To prevent precision loss you can select // Use full precision // option on file saver dialog, however this will result in bigger files.
 
 == Other Options ==