You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now database geometry types are created with shape and srid, which gives following errors if SRID is not specified:
Geometry SRID (0) does not match column SRID (3346)
So in order to fix that, client now must specify SRID:
SRID=4326;POINT(-44.3 60.1)
But this breaks backward compatibility, so clients should still be able to write data without SRID, and SRID should be added automatically using value specified in manifest file.
Currently, SRID is not specified on writes, for example if following data are received from client:
it is passed to database as is. But after fixing a bug with geometry type arguments:
ccc7ab1#diff-ef698dfa7530dce56bc8139a272f35940c59a01449c3c23bfe5fbb538effe5cc
Now database geometry types are created with shape and srid, which gives following errors if SRID is not specified:
So in order to fix that, client now must specify SRID:
But this breaks backward compatibility, so clients should still be able to write data without SRID, and SRID should be added automatically using value specified in manifest file.
spinta/tests/dtypes/test_geometry.py
Line 140 in 9a3d584
API should accept both cases, with SRID and without.
The text was updated successfully, but these errors were encountered: