Actually that was just an example of a polygon that would fail to render a raster (when I mentioned “think of a thin polygon following a vertical meridian and extending past both the North and South poles”).
GPlates is generally agnostic to the poles and the dateline (in its internal operations). So any rotation/reorientation of a problematic problem will still have the same issue in GPlates.
Thanks for that. I converted that output to a GPML file using PlateTectonicTools with python -m ptt.convert_xy_to_gplates -l -p polygon-breaks-raster.txt (after removing the last line and adding an empty line beginning with > at the top). Also note that PlateTectonicTools will soon be part of GPlately.
After loading it into GPlates I can see that while it can be filled (see image below) it cannot render a raster for the reason I stated in a previous post. It exceeds the internal limit of 162 degrees (it’s actually not 180 degrees as I mentioned earlier). And your polygon spans about 170 degrees. You can measure this with the Measure tool on the 3D orthographic globe by clicking two points near each end of the polygon (and then read the line distance).
In a future version of GPlates I am considering an alternate approach to avoid this issue.
