<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I’m OK w/ a linestring. The type is just because I need something that is a geometry to hold what I care about, which is the actual box in the header. I think most people understand the “box” idea pretty well, but n-d boxes (particular in the geography case) can be just as confusing in their own right.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">P.</div> <div id="bloop_sign_1424955650713778944" class="bloop_sign">
<title></title>
<div>
<br>
</div>
-- <br>
Paul Ramsey<br>
http://cleverelephant.ca<div>http://postgis.net
</div>
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "em",
"name": "John Doe",
"jobTitle": "Graduate research assistant",
"affiliation": "University of Dreams",
"additionalName": "Johnny",
"url": "http://www.example.com",
"address": {
"@type": "PostalAddress",
"streetAddress": "1234 Peach Drive",
"addressLocality": "Wonderland",
"addressRegion": "Georgia"
}
}
</script>
</div> <br><p style="color:#000;">On February 26, 2015 at 4:30:52 AM, Sandro Santilli (<a href="mailto:strk@keybit.net">strk@keybit.net</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>I was looking for a way to expand a 4D point to use the resulting
<br>"nd-box" in an ND overlap query (&&&) and found the closest function
<br>to do that being ST_Expand(geometry).
<br>
<br>That function reurns a geometry of type POLYGON, but I'm thinking..
<br>what's the POLYGON representation for a 3D or 4D box ?
<br>Having 5 vertices makes it completely arbitrary where to put
<br>the MIN and the MAX values of each ordinate.
<br>
<br>Wouldn't it be less confusing to return a 2-vertices LINESTRING
<br>instead ?
<br>
<br>As noted in http://trac.osgeo.org/postgis/ticket/1329
<br>a 2-vertices LINESTRING might be the closest thing to
<br>an even less confusing "BOXND" type. It has a direction
<br>(contrary to a MULTIPOINT) that makes it clear what the
<br>min and max are (first and last points).
<br>
<br>Or would you prefer to have a new "BOX" geometry type ?
<br>Or even a new "BOXND" PostgreSQL type ?
<br>
<br>--strk;
<br>_______________________________________________
<br>postgis-devel mailing list
<br>postgis-devel@lists.osgeo.org
<br>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
<br></div></div></span></blockquote></body></html>