Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
GEOPACKAGE Column id ambiguity when using BBOX #5858
We are using a geo package as a data source, the layer contains the column id.
We are not in control of the manufactured geo package.
example layer config
Is there a solution or workaround?
With kind regards,
Could you help us by attaching a small geopackage to test with? By a quick look to the query I can't understang the problem. The join seems to use the internal perceel.ROWID column for the join and perceel.id should not have any effect.
When using a GeoPackage table that has a 'id' column, in some circumstances, MapServer composes internally a SELECT statement, but fails to prefix the id column with the table name, which causes an ambiguity when joining with the spatial index RTree table that has also a id column.