[postgis-devel] [PostGIS] #576: 3d distance functions
PostGIS
trac at osgeo.org
Wed Sep 1 10:55:31 PDT 2010
#576: 3d distance functions
-------------------------+--------------------------------------------------
Reporter: nicklas | Owner: nicklas
Type: enhancement | Status: assigned
Priority: medium | Milestone: PostGIS 2.0.0
Component: postgis | Version: trunk
Keywords: |
-------------------------+--------------------------------------------------
Comment(by nicklas):
The functions I found from a quick scan that could be affected by changing
the naming convention is:[[BR]]
length3d[[BR]]
ST_length3d[[BR]]
length3d_spheroid[[BR]]
ST_length3d_spheroid[[BR]]
perimeter3d[[BR]]
ST_perimeter3d[[BR]]
MakeBox3d[[BR]]
ST_MakeBox3d[[BR]]
Extent3d[[BR]]
ST_Extent3d[[BR]]
st_box3d[[BR]]
st_box3d_extent[[BR]]
box3d[[BR]]
length2d[[BR]]
ST_length2d[[BR]]
length2d_spheroid[[BR]]
ST_length2d_spheroid[[BR]]
perimeter2d[[BR]]
ST_perimeter2d[[BR]]
area2d[[BR]]
ST_area2d[[BR]]
MakeBox2d[[BR]]
ST_MakeBox2d[[BR]]
st_box2d[[BR]]
st_box2d[[BR]]
box2d[[BR]]
-- Those functions I think should keep their names because that tells
something that they are forced towards 3D, 2D and 4D, not from.[[BR]]
force_2d[[BR]]
ST_force_2d[[BR]]
force_3dz[[BR]]
ST_force_3dz[[BR]]
force_3d[[BR]]
ST_force_3d[[BR]]
force_3dm[[BR]]
ST_force_3dm[[BR]]
force_4d[[BR]]
ST_force_4d[[BR]]
Then their is the internal functions. Since it is a major release maybe
the name convention should harmonize with the internal functions?[[BR]]
/Nicklas
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/576#comment:17>
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.
More information about the postgis-devel
mailing list