ibis throws error on geometry column #7823
-
I have a column of type geometry in mssql server called Shape. When I try to read the table, I receive an error, but when I connect to a table without the geom column, I receive the data. Is there a way to either omit the geom column or cast it in the initial connection? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
Hey @carlsunderman -- can show us the schema for the table in question using Also, if you can paste the traceback that will also help. |
Beta Was this translation helpful? Give feedback.
-
I think this should work the data is in WKB and I normally need to do ST_AsText when selecting with sqlalchemy |
Beta Was this translation helpful? Give feedback.
-
SAWarning: Omitting index key for (Shape), key covers omitted columns. OperationalError: (pymssql._pymssql.OperationalError) (2809, b"The request for procedure 'GLB_SEISMIC_2DLINES_API' failed because 'GLB_SEISMIC_2DLINES_API' is a table object.DB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\n") but when i query a table without the shape column, it loads and like I said, if I connect via sqlalchemy and ST_AsText the shape column it loads there too |
Beta Was this translation helpful? Give feedback.
-
is there a way with ibis to omit or [SHAPE.]STAsText() this column on connecting? [SHAPE.]STAsText() works with create_engine using create_engine, without the above, I get the following pyodbc error |
Beta Was this translation helpful? Give feedback.
-
no problem, for this type of data I can use other methods then pass to ibis, thank you for your help |
Beta Was this translation helpful? Give feedback.
there is not. 😬