Markus Metz wrote:
How about reversing the current policy? Restrict both raster and vector
maps to the 180 degree lon and 90 degree lat limit, that avoids
duplicate features within a map. Allow the region to be set anywhere
between -360 and 360 lon but restrict the width of the
Glynn Clements wrote:
Markus Metz wrote:
Do you really mean 360 degrees plus the width of the window? That
would be max 720 degrees?
Wrong window ;)
I'm talking about the buffer/kernel/etc window, i.e. the size=
parameter for r.neighbors, 4 cells for r.proj method=cubic, etc.
Glynn Clements wrote:
Markus Metz wrote:
How about reversing the current policy? Restrict both raster and vector
maps to the 180 degree lon and 90 degree lat limit, that avoids
duplicate features within a map. Allow the region to be set anywhere
between -360 and 360 lon but restrict the
Glynn Clements wrote:
By Euclidified, I mean that the data is in a form such that code
which process it can treat -179 and +181 as being distinct points 360
units apart.
It seems that grass treats -179 and 179 as being 2 units apart, I do not
have to change it to 179 and 181. Latlon coords
Markus Metz wrote:
Requiring code to explicitly use specialised (spherical-aware)
functions in place of +,-,,,== etc is not a realistic strategy.
It seems the display does so when zooming out or panning. The Chukchi
Peninsula and other features are copied around and displayed on both
Glynn Clements wrote:
Markus Metz wrote:
I think my questioning started because the region settings including map
extends are restricted to the 180 degree lon and 90 degree lat limits
whereas vector operations can exceed these limits causing problems later
on. To make grass handling of
