Feature: IVEA projection#3
Conversation
|
Leaving open for reference, but will require reworking to be compatible with new approach that uses conway meta to cut up the polyhedron and a definition for the parents net |
|
|
||
| polyhedral::load_triangles(Q, decakis_dodecahedron::SPH_TRI, nets::dsea::icosahedron::FACE_TRI); | ||
| polyhedral::set_orient_from_angles(Q, ISEA_STD_LAT_DEG, ISEA_STD_LON_DEG, IVEA_AZ_DEG); | ||
|
|
There was a problem hiding this comment.
@felixpalmer Curious about this (IVEA_AZ_DEG) here...
Is that the azimuth from DSEA's perspective?
If so, that might be problematic if trying to override +proj=ivea with +azi from ISEA/IVEA's perspective?
Is that positioning the vertices of the icosahedron at ISEA_STD_LAT_DEG, ISEA_STD_LON_DEG, or the vertices of the dodecahedron?
Also wondering if you updated this PR already or it still needs refactoring (it shows no conflict)?
There was a problem hiding this comment.
No this PR is out of date, no point keeping it as the other branch has diverged too much
2 participants
Overview
This PR is stacked on top of the root PR: OSGeo#4758 - please see there before reviewing
Projecting with
DSEAonto a icosahedral net yields a better result (less cusps) that usingISEA. This approach has been referred to asIVEAin some places, for example https://dggal.org/The purpose of this PR is to show how an alias can be added for an existing projection to make it easier for end users - some of whom may find it confusing that a dodecahedral projection can be unfolded onto an icosahedral net.
Change list
Example renders
IVEANote cusps compared to IVEA