Hi Babis, Thank you for your reply. You are right; I am referring to that bug. Hopefully it'll get fixed in the future (or I might do so myself) but for now I will work around it. Best regards, Dennis On 12-11-2013 12:05, Charalampos Nikolaou wrote:

Hi Dennis,

you are referring to this bug then, http://bugs.monetdb.org/show_bug.cgi?id=2815. Currently, in MonetDB, information about the SRID of a geometry is not stored at all. In particular, functions that take an extra argument for the SRID ignore that argument. See for example here: http://dev.monetdb.org/hg/MonetDB/file/aa2e3065be7e/geom/monetdb5/geom.mal

Regards, Babis

On Tue, Nov 12, 2013 at 11:17 AM, Dennis Pallett wrote:

...

Hello all,

I'm working with the GeoSpatial extension of MonetDB and I might have run into a bug with regards to the spatial reference ID of objects. When adding a new object I specify the spatial reference ID but when retrieving the same object the correct spatial reference ID is not returned. The following queries demonstrate the bug:

# Create a new spatial table CREATE TABLE trees (id INT, shape POINT);

# insert a new Point object in spatial reference system 4326 (WGS 84) INSERT INTO trees VALUES ( 1, PointFromText('POINT (30 10)', 4326) );

# Retrieve the Spatial Reference ID from the just inserted Point object SELECT SRID(shape) FROM trees;

I expect the result to be 4326 but instead it is always 0.

Is this a bug in MonetDB / GeoSpatial or am I misunderstanding something?

Best regards, Dennis Pallett _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

---

users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list