Hi Andy, If you look at the function definitions (\df ST_MakePoint*), all of the geometry constructor functions use double precision types. With Postgres, 'float' is taken to mean double precision.
As a related side note, single precision floats are called 'real' with an alias 'float4', but these aren't used in PostGIS 2.x where coordinate precision matters. Versions up to PostGIS 1.5 use float4 for bounding boxes. -Mike On 8 October 2014 13:41, Andy Becker <[email protected]> wrote: > Hi all - Sorry if this is a long-resolved design decision, but is there a > good reason that MakePoint accepts double precision inputs while MakePointM > only accepts single-precision floats? > > http://postgis.net/docs/ST_MakePoint.html > http://postgis.net/docs/ST_MakePointM.html > > In my use cases single-precision resolution is not fine enough, such that > MakePointM can't be used. My tables will accordingly need a > double-precision POINT geometry object and then a separate column for the > m-value. > > Thanks, > Andy _______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
