- edited description
Different relations between map pixels and km not treated correctly
Depending on the map, the map coordinates and thus the relation between pixels and km vary. Cylindrical projection uses longitude/latitude as unit, whereas stereographic projections use meters.
This distinctions is important and several places in the code check for "lcc" and "stere" to treat it differently. This is not consistently used and the chance of< introducing errors increases drastically.
We should review the code for places where the projection is relevant for the behaviour and maybe encapsulate this.
We should add checks to the code where the distinction is important that the map type is known and covered.
See issue #245 for an example of the code not being careful about map projections.
Comments (7)
-
reporter -
Steps towards better general projection support
Repaired inserting points on lines for non-cylindrical projections.
See issue #246
→ <<cset 76e7188dfc42>>
-
- changed milestone to 1.7.0
-
reporter - changed milestone to 1.8.0
-
- changed milestone to 1.9.0
Depending on the map, the map coordinates and thus the relation between pixels and km vary. Cylindrical projection uses longitude/latitude as unit, whereas stereographic projections use meters.
This distinctions is important and several places in the code check for "lcc" and "stere" to treat it differently. This is not consistently used and the chance of< introducing errors increases drastically.
We should review the code for places where the projection is relevant for the behaviour and maybe encapsulate this.
We should add checks to the code where the distinction is important that the map type is known and covered.
See issue
#245for an example of the code not being careful about map projections. -
- changed milestone to 1.10.0
-
- changed milestone to 2.0.0
- Log in to comment