Opened 10 years ago
Closed 9 years ago
#2959 closed defect (wontfix)
Make function definitions for ST_MakePoint* consistent
Reported by: | acbecker | Owned by: | robe |
---|---|---|---|
Priority: | low | Milestone: | PostGIS 2.1.8 |
Component: | documentation | Version: | 2.1.x |
Keywords: | Cc: |
Description
Currently the documented function definitions for MakePoint and MakePointM
http://postgis.net/docs/ST_MakePoint.html http://postgis.net/docs/ST_MakePointM.html
use a mix of "float" and "double"-type arguments to the functions. These should be consistent across all functions in the documentation.
Change History (5)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Milestone: | PostGIS 2.1.5 → PostGIS 2.1.6 |
---|
comment:3 by , 10 years ago
Milestone: | PostGIS 2.1.6 → PostGIS 2.1.7 |
---|
comment:4 by , 10 years ago
Milestone: | PostGIS 2.1.7 → PostGIS 2.1.8 |
---|
comment:5 by , 9 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
don't care. Too lazy to fix this.
Note:
See TracTickets
for help on using tickets.
Also ST_Point uses
float
.As a side note, the manual uses three different notations for the same data type:
double precision
,float
, andfloat8
. However, I'm not suggesting that everything should be renameddouble precision
(e.g. ST_Affine has 12float
parameters).