[postgis-users] ST_MakePoint vs. ST_MakePointM

[Sandro Santilli]

On Wed, Oct 08, 2014 at 05:10:19PM +1300, Mike Toews wrote:
> On 8 October 2014 13:41, Andy Becker <acbecker at gmail.com> 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
> 
> 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.

The documentation would indeed be better using consistent definitions.
Andy: do you feel like filing a ticket for that ?

--strk; 

 ()  ASCII ribbon campaign  --  Keep it simple !
 /\  http://strk.keybit.net/rants/ascii_mails.txt