[postgis-devel] getPoint*_p and force_* bugs

strk at refractions.net strk at refractions.net
Tue Nov 22 12:40:15 PST 2005

I just discovered a bug in the getPoint*_p primitives.
The bug influences force_*() user-level functions:

	force_3dm('POINT(0 0 1)') =
	POINTM(0 0 1)

While it should be POINTM(0 0 0) 

I'm going to fix this before 1.0.5 scheduled
for Friday 25 November.

If you have any concerns wrt semantic (ie: you
think current semantic is right and actually using it)
let me know ASAP.


 /"\    ASCII Ribbon Campaign
 \ /    Respect for open standards
  X     No HTML/RTF in email
 / \    No M$ Word docs in email

More information about the postgis-devel mailing list