[prev in list] [next in list] [prev in thread] [next in thread]
List: postgis-devel
Subject: Re: [postgis-devel] [PostGIS] #817: Renaming old 3D functions to
From: "PostGIS" <trac () osgeo ! org>
Date: 2011-01-31 22:57:23
Message-ID: 058.a76a0a81ee3d2087de98f33799289d93 () osgeo ! org
[Download RAW message or body]
#817: Renaming old 3D functions to the convention ST_3D..........
---------------------+------------------------------------------------------
Reporter: nicklas | Owner: nicklas
Type: defect | Status: new
Priority: medium | Milestone: PostGIS 2.0.0
Component: postgis | Version: trunk
Keywords: |
---------------------+------------------------------------------------------
Description changed by robe:
Old description:
> Old name ---> should be
>
> ST_length3d ---> ST_3DLength
> ST_length3d_spheroid ---> ST_3DLength_Spheroid
> ST_perimeter3d ---> ST_3DPerimeter
> ST_MakeBox3d ---> ST_3DMakeBox
> ST_Extent3d ---> ST_3DExtent
>
> What about functions with explicit 2D, I guess they should follow the
> same convention:
>
> ST_length2d ---> ST_2DLength
> ST_length2d_spheroid ---> ST_2DLengthSheroid
> ST_perimeter2d ---> ST_2DPerimeter
> ST_area2d ---> ST_2DArea
> ST_MakeBox2d ---> ST_2DMakeBox
> st_box2d ---> ST_2DBox
>
> -- Those functions I think should keep their names because that tells
> something that they are forced towards 3D, 2D and 4D, not from.
> ST_force_2d
> ST_force_3dz
> ST_force_3d
> ST_force_3dm
> ST_force_4d
>
> Comments?
>
> Should we rename the C-functions at the same time where appropriate?
New description:
{{{
Old name ---> should be
ST_length3d ---> ST_3DLength
ST_length3d_spheroid ---> ST_3DLength_Spheroid
ST_perimeter3d ---> ST_3DPerimeter
ST_MakeBox3d ---> ST_3DMakeBox
ST_Extent3d ---> ST_3DExtent
What about functions with explicit 2D, I guess they should follow the same
convention:
ST_length2d ---> ST_2DLength
ST_length2d_spheroid ---> ST_2DLengthSheroid
ST_perimeter2d ---> ST_2DPerimeter
ST_area2d ---> ST_2DArea
ST_MakeBox2d ---> ST_2DMakeBox
}}}
-- Those functions I think should keep their names because that tells
something that they are forced towards 3D, 2D and 4D, not from.
{{{
ST_force_2d
ST_force_3dz
ST_force_3d
ST_force_3dm
ST_force_4d
}}}
Comments?
Should we rename the C-functions at the same time where appropriate?
--
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/817#comment:6>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer \
wiki, and a view into the subversion code repository of PostGIS project. \
_______________________________________________ postgis-devel mailing list
postgis-devel@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic