<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Roberto Ribeiro kirjoitti 23.11.2017 klo 20:43:<br>
<blockquote type="cite"
cite="mid:CANTZQ+y5B+ChPpr4yymXzDHDDqBJVt3QnkibwqddJn537jNx2A@mail.gmail.com">
<div dir="ltr">In OGR, the GetGeometry() method from the Geometry
class returns a bounding box in the (xmin, xmax, ymin, ymax)
structure. However, the SetSpatialFilterRect() method from the
Layer class expects a bounding box in the (xmin, ymin, xmax,
ymax) structure. This is a problem that can be worked around,
but it does generate confusion. Any reason why this couldn't be
standardized?<br>
</div>
</blockquote>
<br>
There are also for example in gdal_translate also "xoff yoff xsize
ysize", i.e., (xmin, ymin, xmax-xmin, ymax-ymin) and "ulx uly lrx
lry", i.e., (xmin, ymax, xmax, ymin).<br>
<br>
I guess the main reason is that changing the interface is a major
change. So, perhaps this could be put on the list of things to
consider changing in GDAL 3.0.<br>
<br>
Ari<br>
<br>
<blockquote type="cite"
cite="mid:CANTZQ+y5B+ChPpr4yymXzDHDDqBJVt3QnkibwqddJn537jNx2A@mail.gmail.com">
<div dir="ltr"><br>
Also, on a similar note, having SetSpatialFilterRect expect an
array of coordinates, instead of coordinates as individual
arguements, seems more logical to me, as it's how every other
GIS package returns bounding box info afaik, including OGR's
GetGeometry.<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gdal-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/gdal-dev">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a></pre>
</blockquote>
<br>
</body>
</html>