<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">
<p>Why not using PRIMEM, for example like below?</p>
<blockquote>
<pre>GEODCRS["WGS 84 (anti-meridian)",
DATUM["World Geodetic System 1984",
ELLIPSOID["WGS 84", 6378137, 298.257223563, LENGTHUNIT["metre",1.0]]],
PRIMEM["Anti-meridian", 180, ANGLEUNIT["degree",0.01745329252]],
CS[ellipsoidal,2],
AXIS["latitude",north,ORDER[1]],
AXIS["longitude",east,ORDER[2]],
ANGLEUNIT["degree",0.01745329252]]</pre>
</blockquote>
<p>It should create a CRS with longitude in -180 to 180° range,
but where 0° is at 180° from Greenwich (I not sure if this is
what you wanted).<br>
</p>
<p>Martin</p>
<p><br>
</p>
<p>Le 12/04/2020 à 23:53, David Hoese a écrit :</p>
</div>
<blockquote type="cite"
cite="mid:d3da8820-5cbe-73f1-9a4b-fe11213b3fad@gmail.com">>There's
no way in standard WKT to express a longitude of origin != 0 for a
GeographicCRS. If you export to WKT1_GDAL, a EXTENSION[] node
captures this however. Or if you re-export back to PROJ string the
CRS object built from "+proj=latlong +lon_0=45", you'll get back
the original string.
<br>
<br>
So if I use WKT2 as my standard in-memory/serialized version of a
CRS, is there any standard way to handle a geotiff that goes over
the anti-meridian (-180/180)? In the past I've played around with
`+over` or changing with `+lon_0=X`, but those won't work here it
seems.
<br>
</blockquote>
</body>
</html>