-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarification on the Relationship Between Georeferencing and X-Y Axis Position of Objects in the Map #2190
Comments
If your question is about the x and y axes: The origin, where the axes intersect, x=0, y=0, is determined by the map coordinates of the reference point. The orientation of the axes has the y axis north-south and the x axis west-east, with positive y values to the north and positive x values to the east. Because Mapper is for orienteering maps, the map orientation and its coordinate axes are magnetic. The map developer sets the declination in the Georeferencing dialog, which orients the map in relation to geographic directions, i.e. meridians of longitude and parallels of latitude. Georeferencing also determines a projected grid, by specifying a CRS (Coordinate Reference System) which may or may not agree with geographic directions. Mapper is able to display whichever of the 3 grids the user chooses: map, projected, or geographic. |
If the question is about the positioning of objects: Each map object has an x,y position. An object's geographic and projected coordinates are calculated as needed. The calculation is determined by the map's georeferencing parameters:
The calculation of projected coordinates from map coordinates uses:
The calculation of map coordinates from projected coordinates is the inverse, and uses the same parameters. The relationship between geographic and projected coordinates is a property of the CRS (Coordinate Reference System). Mapper relies on the PROJ library to make the correspondence. The difference between geographic north and projected north is the "convergence". The difference between geographic scale and the projection's scale is the "grid scale factor". Convergence and grid scale factor depend on the location of the reference point.
|
The object coordinates in the omap/xmap file are not an exact match for the displayed coordinates (in your example, 0,07 -1,09). The coordinates in the file are measured in thousandths of a mm, in other words in micrometers. In addition, the y coordinates in the file have their minus/plus switched. (This makes them better able to be drawn on the computer's screen, because the y coordinate at the top of the screen is 0.) So the object corner represented in the file as 101 1035, has x and y coordinates on the map of 0,101 -1,035 (mm). |
The grid scale factor and the auxiliary scale factor are small enough that there's usually no need to manage them. Many maps either have an auxiliary scale factor of 1.0, or have a combined scale factor of 1.0. |
Does this mean that the map is represented with an orthographic projection that matches the map grid? |
The map could represent the terrain using an orthographic projection. However, the user sets the projection when choosing a CRS in a georeferencing dialog. The normal recommendation is that the CRS match the CRS of a base map. Note that if the CRS/projection is orthographic, the relationship between map and geographic coordinates can be more direct, because the projection can be chosen so that the grivation and grid scale factor have no effect. In other words, the grivation would be 0° and the grid scale factor would be 1.0. |
The map drawing does not move when changing CRS (no stretching or deformation) so the drawing grid does not move, but it is the new projection grid that adjusts to it. When creating a new georeferenced map there is a grid scale factor taken into account in the combined scale factor, this means that mapper creates a custom orthographic projection centered at the reference point. Right? |
That is the effect of changing the CRS using the Georeferencing dialog. If the map drawing is already correctly georeferenced, then that method of changing the CRS is not suitable.
Mapper uses the grid scale factor as you say. Similarly it uses the convergence to orient the projected coordinates relative to the map's magnetic north y axis. The scaling and orientation are used to align the map coordinates with the projected coordinates which are given meaning by the CRS. For this purpose, a map's grid scale factor is a number close to 1.0, and its convergence is a number close to 0, plus or minus a few degrees.
The grid scale factor and convergence, being properties of the projection between ellipsoid and a 2-D plane, are not perfectly constant across the map. To deal with this, Mapper determines their values at the reference point, and uses those specific numbers to relate the map coordinates with the projected coordinates. Yes, Mapper centers on the reference point. But no, the grid scale factor and convergence do not depend on an orthographic projection. |
thanks for the answer. |
So what would be the right way? |
If a map is already correctly georeferenced, and you want to change the CRS to a different projection,
Step 2 uses the PROJ library to position the map objects, by transforming from projected coordinates in the old CRS to projected coordinates in the new. I tried an example just now. This careful method made a difference of only 0.5 m in the positioning of an object 3.5 km from the reference point. So it's often a small effect. What I said earlier was too strong. Simply changing the CRS in the georeferencing dialog may be suitable. |
Thanks a lot for this clarification. |
@pkturner I think there is a lot of valuable information provided here and it would be beneficial to expand the help for the program. It's not information that a beginner would probably appreciate, but it could be included somewhere so that even experienced mappers can find answers to their questions. |
It is not always like this, for example in my country |
I would like to seek clarification on the connection between georeferencing and the positioning of the x and y axes of objects in the map.
Thank you for response.
The text was updated successfully, but these errors were encountered: