AP_Terrain: Use SI units conventions in parameter units

Follow the rules from:
http://physics.nist.gov/cuu/Units/units.html
http://physics.nist.gov/cuu/Units/outside.html
and
http://physics.nist.gov/cuu/Units/checklist.html
one further constrain is that only printable (7bit) ASCII characters are allowed
This commit is contained in:
Dr.-Ing. Amilcar Do Carmo Lucas 2017-05-02 15:48:42 +02:00 committed by Andrew Tridgell
parent c417376ba8
commit 26771f5348

View File

@ -45,7 +45,7 @@ const AP_Param::GroupInfo AP_Terrain::var_info[] = {
// @Param: SPACING
// @DisplayName: Terrain grid spacing
// @Description: Distance between terrain grid points in meters. This controls the horizontal resolution of the terrain data that is stored on te SD card and requested from the ground station. If your GCS is using the worldwide SRTM database then a resolution of 100 meters is appropriate. Some parts of the world may have higher resolution data available, such as 30 meter data available in the SRTM database in the USA. The grid spacing also controls how much data is kept in memory during flight. A larger grid spacing will allow for a larger amount of data in memory. A grid spacing of 100 meters results in the vehicle keeping 12 grid squares in memory with each grid square having a size of 2.7 kilometers by 3.2 kilometers. Any additional grid squares are stored on the SD once they are fetched from the GCS and will be demand loaded as needed.
// @Units: meters
// @Units: m
// @Increment: 1
// @User: Advanced
AP_GROUPINFO("SPACING", 1, AP_Terrain, grid_spacing, 100),