-
Hello everyone, Firstly, I want to express my gratitude for the fantastic work on the ogr_fdw extension. It's an invaluable tool for integrating geospatial data into my Postgres databases. I'm encountering an issue while connecting to a WFS server using ogr_fdw. The aim is to access planning data from a municipality, but I'm running into a snag with a specific column. Here's how I set up the server and foreign table: CREATE FOREIGN TABLE IF NOT EXISTS hessen.bplan_biedenkopf( When I attempt to select data from this table, I get the following error:
The "pdf" column is supposed to store links to downloadable PDF files and seems to be causing the issue. I've tried several configurations, including setting ARRAY_AS_STRING=YES, but the error persists. Excluding this column does fix the error, but the links in the "pdf" column are crucial for my project.When I load the WFS in QGIS for testing purposes, the issue with the column does not occur. I would greatly appreciate any advice on handling or circumventing this OGR array issue. If anyone could suggest a workaround or solution to include the "pdf" column, it would be incredibly helpful. Thank you so much for your time and help! Lukas |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Well, ogr_fdw definitely does not support arrays, so there's no configuration fix at that level. Your attempt with |
Beta Was this translation helpful? Give feedback.
Well, ogr_fdw definitely does not support arrays, so there's no configuration fix at that level. Your attempt with
ARRAY_AS_STRING
is along the correct path, try to get OGR to paper over the difference. I'd tend to think that a server definition using that option combined with a table definition that just says the column type is 'varchar' would be the thing most likely to work. I'd experiment with ogr2ogr or ogrinfo a little to make sure you're actually getting plain strings out of OGR, as getting exactly the right option string into exactly the right OGR variable can be tricky.