[postgis-devel] ST_Area, ST_Area2D
robe.dnd at cityofboston.gov
Fri Jul 18 07:55:20 PDT 2008
Ditto for these too? ESRI and IBM just refer to this as ST_Length
--Docs have ST_Length2D and 3D but no ST_Length
Returns the 2-dimensional length of the geometry if it is a
linestring or multi-linestring.
Just replace with ST_Length()?
Both ST_Length() and ST_Length2d() map to -
Now ST_Length3D() maps to LWGEOM_length_linestring
Which on closer tests - gives me the same answer as ST_Length() for a
Is there a reason why we can't just have a single documented
ST_Length and state it works for both 2D and 3D strings? and in future
versions just have all 3 map to LWGEOM_length_linestring
and deprecate the 2D and 3D names?
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Paul
Sent: Friday, July 18, 2008 10:35 AM
To: PostGIS Development Discussion
Subject: Re: [postgis-devel] ST_Area, ST_Area2D
Undocument it, and note that it is deliberately undocumented in the
.sql.in file, so we don't go and re-document it in the future.
On Fri, Jul 18, 2008 at 5:36 AM, Obe, Regina <robe.dnd at cityofboston.gov>
> Can I scrap ST_Area2D from docs and just replace with ST_Area? or is
> ST_Area2D really the preferred name? They both map to
> LWGEOM_area_polygon, but
> the docs list the ST_Area2D one which seems a bit more verbose and
> Both IBM and ESRI on quick search just call it ST_Area
> IBM -
> and Esri
> The substance of this message, including any attachments, may be
> confidential, legally privileged and/or exempt from disclosure
> pursuant to Massachusetts law. It is intended
> solely for the addressee. If you received this in error, please
> contact the sender and delete the material from any computer.
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
postgis-devel mailing list
postgis-devel at postgis.refractions.net
More information about the postgis-devel