[postgis-users] ST_MakePoint vs. ST_MakePointM

[Andy Becker]

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