<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Erick<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 27 Mar 2019, at 01:09, E. Ndava via qgis-za-user <<a href="mailto:qgis-za-user@lists.osgeo.org" class="">qgis-za-user@lists.osgeo.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">Hi List</div><div class=""><br class=""></div><div class="">This is not really a QGIS specific question/ issue, just that I am trying to achieve something within QGIS.</div><div class=""><br class=""></div><div class="">The Case:</div><div class="">I have data (geopackage attached) with crs WGS84, EPSG:2643 </div></div></div></div></blockquote><div><br class=""></div><div>you mean 4326</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">which I have gone through hoops and loops to no avail, to re-project to EPSG:2048. The result I am getting is to the effect that the data is flipped over the equator.</div></div></div></div></blockquote><div><br class=""></div><div>That’s perfectly correct and to be expected. 2048 is south-facing (wsu or west south up). If you want a north-facing or east north up one use ‘ZANGI HBKNO19’.</div><div><br class=""></div><div>There are a bunch of new SA CRSs in the latest EPSG database that duplicate the south facing ones that were already there and add north facing variants (so the ZANGI ones can be retired). However they have issues: 102482 (should match 2048 but it doesn’t. It uses k=-1 which does the wrong thing and is deprecated) and 102562 (same effect as ZANGI HBKNO19 except 102562 uses k=1 which does nothing and is deprecated). So I would avoid using the new ones.</div><div><br class=""></div><div>Gavin</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">An workarounds/ methodology / pointers to something I am missing?</div><div class=""><br class=""></div><div class="">PS: I have worked through shapefiles, geopackage and PostGIS...same result.</div><div class=""><br class=""></div><div class="">Thanks</div><div class="">Erick.</div><div class=""><br class=""></div>-- <br class=""><div dir="ltr" class="gmail_signature"><div dir="ltr" class=""><div class="">----------------------------------------------------------------------------------------------------------------------------------------<br class="">| @erickndava | <a href="http://erickndava.github.io/" target="_blank" class="">http://erickndava.github.io/</a> |<br class=""><br class="">Thou art my hiding place; thou shalt preserve me from trouble; thou shalt compass me about with songs of deliverance. Selah. Psalm 32:7</div></div></div></div></div>
<span id="cid:f_jtqe6hdb0"><points_in_wcape.gpkg></span>_______________________________________________<br class="">qgis-za-user mailing list<br class=""><a href="mailto:qgis-za-user@lists.osgeo.org" class="">qgis-za-user@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/qgis-za-user<br class=""></div></blockquote></div><br class=""></body></html>