Skip to content

Commit fac3c92

Browse files
committed
rebase + add info about CRS EPSG:4979
1 parent 58da15e commit fac3c92

16 files changed

Lines changed: 64 additions & 20 deletions

src/gis/elevations/index.md

Lines changed: 63 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ When collecting data in the field, <MobileAppName /> provides information about
1111

1212
An *orthometric* height is a physical height referred to a *geoid*, a special surface that resembles the mean sea level. The difference between ellipsoidal and orthometric height is called the *geoid separation* (also known as geoid height or undulation) and it can be applied to transform between these heights.
1313

14-
When transforming elevations from ellipsoidal to orthometric, <MainPlatformNameLink /> uses the EGM96 geoid model by default. However, it is also possible to use another geoid model as described in the [Using custom geoid](#using-custom-geoid) section. This may be especially useful when conducting more precise surveys or when a specific vertical reference system is required.
14+
When transforming elevations from ellipsoidal to orthometric, <MainPlatformNameLink /> uses the EGM96 geoid model by default. However, it is also possible to use another geoid model as described in the [Using custom vertical reference system](#custom-vertical-reference-system) section. This may be especially useful when conducting more precise surveys or when a specific vertical reference system is required.
1515

1616
:::warning Learn more
1717
Height systems and elevations are complex topics. If you want to get more insight, we recommend going through some explanatory resources, such as [Height Systems](https://geodesy.science/item/height-systems/) by the International Association of Geodesy.
@@ -27,16 +27,16 @@ Information about the altitude and geoid separation (if available) are displayed
2727

2828
![GPS info panel](../../field/mobile-app-ui/mobile-app-gps-info.webp "GPS info panel")
2929

30-
There are some differences in the functionality and available details depending on the GPS provider, the OS of the mobile device and the connection setup, namely the type of elevation provided, available [position variables](../../layer/variables/#position-variables) and whether it is possible to use [custom geoid](#using-custom-geoid).
30+
There are some differences in the functionality and available details depending on the GPS provider, the OS of the mobile device and the connection setup, namely the type of elevation provided, available [position variables](../../layer/variables/#position-variables) and whether it is possible to use [custom vertical reference system](#custom-vertical-reference-system).
3131

3232
## Internal provider (no external device)
3333

3434
### Android
3535
On Android, the [internal (fused)](../../field/mobile-app-ui/#gps-settings) GPS provider is used by default. It reports ellipsoidal heights that <MainPlatformName /> transforms to **orthometric heights using the EGM96 geoid model** by default and displays them in the [GPS info panel](../../field/mobile-app-ui/#current-position-and-gps-info).
3636

37-
**Position variables**: :white_check_mark: *ellipsoidal elevation*, *orthometric elevation*, *geoid separation* values are available and can be stored using [position variables](../../layer/variables/#position-variables).
37+
**Position variables**: :white_check_mark: *Ellipsoidal elevation*, *orthometric elevation*, *geoid separation* values are available and can be stored using [position variables](../../layer/variables/#position-variables).
3838

39-
**Custom geoid**: :white_check_mark: It is possible to use the <QGISPluginNameShort /> to [set up a different geoid model](#using-custom-geoid) and transform the elevation to a different vertical reference system.
39+
**Custom vertical CRS**: :white_check_mark: It is possible to use the <QGISPluginNameShort /> to transform the elevation to a different [vertical reference system](#custom-vertical-reference-system).
4040

4141
### iOS
4242
On iOS, the GPS provider can provide orthometric and ellipsoidal heights.
@@ -48,25 +48,25 @@ If ellipsoidal height **is not** available, <MainPlatformName /> does not transf
4848
- :white_check_mark: *orthometric elevation* is available and can be stored using [position variables](../../layer/variables/#position-variables)
4949
- :no_entry_sign: *ellipsoidal elevation* and *geoid separation* values are **not** available
5050

51-
**Custom geoid**: :no_entry_sign: It is not possible to use custom geoid model.
51+
**Custom vertical CRS**: :no_entry_sign: It is not possible to transform elevations to a different vertical reference system.
5252

5353
#### Ellipsoidal height available
5454
If iOS provides also the ellipsoidal heights, <MainPlatformName /> transforms them to **orthometric elevations using the EGM96 geoid model** by default and displays them in the [GPS info panel](../../field/mobile-app-ui/#current-position-and-gps-info).
5555

5656
**Position variables**: :white_check_mark: *ellipsoidal elevation*, *orthometric elevation*, *geoid separation* values are available and can be stored using [position variables](../../layer/variables/#position-variables).
5757

58-
**Custom geoid**: :white_check_mark: It is possible to use the <QGISPluginNameShort /> to [set up a different geoid model](#using-custom-geoid) and transform the elevation to a different vertical reference system.
58+
**Custom vertical CRS**: :white_check_mark: It is possible to use the <QGISPluginNameShort /> to transform the elevation to a different [vertical reference system](#custom-vertical-reference-system).
5959

6060

6161
## External provider - Bluetooth
6262
<Badge text="Android only" type="tip"/>
6363
On Android, external GPS can be connected [using Bluetooth](../../field/external_gps/#how-to-connect-external-gps-receiver-in-android-via-mergin-maps-mobile-app-recommended). If possible, we recommend using this option.
6464

65-
If there is no [user-defined transformation](#using-custom-geoid), the <MobileAppNameShort /> uses data reported by the GPS provider as-is, including the ellipsoidal height and geoid separation. <MainPlatformName /> does not receive information about the geoid model used; this information should be supplied by the GPS provider.
65+
If there is no [user-defined transformation](#custom-vertical-reference-system), the <MobileAppNameShort /> uses data reported by the GPS provider as-is, including the ellipsoidal height and geoid separation. <MainPlatformName /> does not receive information about the geoid model used; this information should be supplied by the GPS provider.
6666

6767
**Position variables**: :white_check_mark: *ellipsoidal elevation*, *orthometric elevation*, *geoid separation* values are available and can be stored using [position variables](../../layer/variables/#position-variables).
6868

69-
**Custom geoid**: :white_check_mark: It is possible to use the <QGISPluginNameShort /> to [set up a different geoid model](#using-custom-geoid) and transform the elevation to a different vertical reference system. The defined geoid model is displayed in the <MobileAppNameShort />.
69+
**Custom vertical CRS**: :white_check_mark: It is possible to use the <QGISPluginNameShort /> to transform the elevation to a different [vertical reference system](#custom-vertical-reference-system). The defined geoid model is displayed in the <MobileAppNameShort />.
7070

7171
## External provider - Network
7272
External GPS can be connected using network connection on both iOS and Android. We recommend using this option.
@@ -78,30 +78,74 @@ The functionality is the same as described above in [External provider - Bluetoo
7878
Mock location should be only used if you are unable to connect the external GPS directly in the <MobileAppNameShort />. Because of system limitations, both Android and iOS send only a subset of available data. Some [position variables](../../layer/variables/#position-variables) may not be available.
7979

8080
### Android
81-
If there is no [user-defined transformation](#using-custom-geoid) (custom geoid), the <MobileAppNameShort /> uses data reported by the GPS provider as-is.
81+
If there is no [user-defined transformation](#custom-vertical-reference-system) (custom geoid), the <MobileAppNameShort /> uses data reported by the GPS provider as-is.
8282

8383
**Position variables**:
8484
- :white_check_mark: *orthometric elevation* is available and can be stored using [position variables](../../layer/variables/#position-variables)
8585
- :no_entry_sign: *ellipsoidal elevation* and *geoid separation* values are **not** available
8686

87-
**Custom geoid**:
88-
- :warning: It is possible to use the <QGISPluginNameShort /> to [set up a different geoid model](#using-custom-geoid) and transform the elevation to a different vertical reference system. However, it is necessary to **set up the mock app to report ellipsoidal heights**, otherwise the geoid separation would be applied twice leading to incorrect elevation values.
89-
- :white_check_mark: If custom geoid is used, the *orthometric elevation*, *ellipsoidal elevation* and *geoid separation* variables are available and can be stored using [position variables](../../layer/variables/#position-variables).
87+
**Custom vertical CRS**:
88+
- :warning: It is possible to use the <QGISPluginNameShort /> to transform the elevation to a different [vertical reference system](#custom-vertical-reference-system). However, it is necessary to **set up the mock app to report ellipsoidal heights**, otherwise the geoid separation would be applied twice leading to incorrect elevation values.
89+
- :white_check_mark: If custom vertical reference system is used, the *orthometric elevation*, *ellipsoidal elevation* and *geoid separation* variables are available and can be stored using [position variables](../../layer/variables/#position-variables).
9090

9191
### iOS
92-
If there is no [user-defined transformation](#using-custom-geoid) (custom geoid), the <MobileAppNameShort /> uses data reported by the GPS provider as-is.
92+
If there is no [user-defined transformation](#custom-vertical-reference-system) (custom geoid), the <MobileAppNameShort /> uses data reported by the GPS provider as-is.
9393

9494
**Position variables**:
9595
- :white_check_mark: *orthometric elevation* is available and can be stored using [position variables](../../layer/variables/#position-variables)
9696
- :no_entry_sign: *ellipsoidal elevation* and *geoid separation* values are **not** available
9797

98-
**Custom geoid**:
99-
- :warning: It is possible to use the <QGISPluginNameShort /> to [set up a different geoid model](#using-custom-geoid) and transform the elevation to a different vertical reference system. However, it is necessary to **set up the mock app to report ellipsoidal heights**, otherwise the geoid separation would be applied twice leading to incorrect elevation values.
100-
- :white_check_mark: If custom geoid is used, the *orthometric elevation*, *ellipsoidal elevation* and *geoid separation* variables are available and can be stored using [position variables](../../layer/variables/#position-variables).
98+
**Custom vertical CRS**:
99+
- :warning: It is possible to use the <QGISPluginNameShort /> to transform the elevation to a different [vertical reference system](#custom-vertical-reference-system). However, it is necessary to **set up the mock app to report ellipsoidal heights**, otherwise the geoid separation would be applied twice leading to incorrect elevation values.
100+
- :white_check_mark: If custom vertical reference system is used, the *orthometric elevation*, *ellipsoidal elevation* and *geoid separation* variables are available and can be stored using [position variables](../../layer/variables/#position-variables).
101+
102+
## Custom vertical reference system
103+
104+
Vertical reference system can be specified in [<MainPlatformName /> Project Properties](../../manage/plugin/#mergin-maps-project-properties) in QGIS. The grid shift file will be packaged with the project based on the selected vertical reference system.
105+
106+
In the <MobileAppNameShort />, the info about the custom vertical system is displayed in the [GPS info panel](../../field/mobile-app-ui/#current-position-and-gps-info).
107+
108+
1. Open your <MainPlatformName /> project and navigate to the <MainPlatformName /> tab in **Project Properties**
109+
110+
2. Check the *Report height in a specific vertical CRS* option :heavy_check_mark:
111+
![Mergin Maps QGIS plugin vertical CRS](./plugin-vertical-crs.webp "Mergin Maps QGIS plugin vertical CRS")
112+
113+
3. Select a vertical CRS from the list or use the **Select CRS** button to choose from predefined CRS.
114+
115+
Use the filter to narrow the search using a keyword or the EPSG code.
116+
117+
Select a CRS and click **OK**.
118+
![Select target vertical CRS in QGIS](./plugin-target-vertical-crs.webp "Select target vertical CRS in QGIS")
119+
120+
5. **Apply** the changes in **Project Properties** and synchronise your changes.
121+
![Mergin Maps QGIS plugin defined vertical CRS](./plugin-set-vertical-crs.webp "Mergin Maps QGIS plugin defined vertical CRS")
122+
123+
When recording and displaying heights in the <MobileAppNameShort />, this vertical system will be used instead of the default EGM96 model.
124+
125+
::: tip Transformations
126+
When transforming elevations to another reference system, <MainPlatformName /> expects WGS 84 (EPSG: 4979) as the source CRS.
127+
128+
To transform elevations to another CRS, make sure that the correct datum transformation is defined in the **Transformations** tab in **Project Properties** where:
129+
- **Source CRS**: EPSG: 4979 (WGS 84)
130+
- **Destination CRS**: the reference system of your choice
131+
132+
![QGIS Project Properties Transformations](./qgis-project-properties-transformations.webp "QGIS Project Properties Transformations")
133+
134+
:::
135+
### Multiple datum transformation available
136+
For some vertical CRS, there may be multiple datum transformations available. If this is the case, you will get a warning when selecting the CRS.
137+
138+
![Mergin Maps QGIS plugin datum transformation warning](./plugin-transformation-warning.webp "Mergin Maps QGIS plugin datum transformation warning")
139+
140+
To make sure that <MainPlatformName /> uses the correct operation, make sure that the datum transformation you want to used is defined in the **Transformations** tab in **Project Properties**.
141+
142+
### Downloading grid shift files
143+
Some specific vertical CRS transformations may not be included in QGIS by default (see [custom projections in QGIS](../proj/#custom-projections-in-qgis)). In this the case, the <QGISPluginNameShort /> will display a warning that it needs to download the geoid grid file.
101144

102-
## Using custom geoid
145+
Use the **click here** link to download the grid.
103146

104-
The geoid model can be specified in [<MainPlatformName /> Project Properties](../../manage/plugin/#mergin-maps-project-properties) in QGIS. The grid shift file will be packaged with the project based on the selected vertical reference system.
147+
![Mergin Maps QGIS plugin geoid grid download](./plugin-download-grid-shift.webp "Mergin Maps QGIS plugin geoid grid download")
105148

106-
In the <MobileAppNameShort />, the info about the custom geoid model is displayed in [GPS info panel](../../field/mobile-app-ui/#current-position-and-gps-info).
149+
The geoid grid will be downloaded and packaged with your project.
107150

151+
![Mergin Maps QGIS plugin geoid grid download](./plugin-grid-shift-downloaded.webp "Mergin Maps QGIS plugin geoid grid download")
21.8 KB
Loading
63.3 KB
Binary file not shown.
13.8 KB
Loading
46.7 KB
Binary file not shown.
49.1 KB
Loading
213 KB
Binary file not shown.
31.1 KB
Loading
160 KB
Binary file not shown.
20.1 KB
Loading

0 commit comments

Comments
 (0)