Opened 15 years ago
Closed 13 years ago
#2959 closed defect (fixed)
MapServer Documentation - data input - PostGIS
Reported by: | davidfawcett | Owned by: | jmckenna |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Documentation - MapServer | Version: | 5.2 |
Severity: | normal | Keywords: | documentation postgis |
Cc: | havatv |
Description
I recently ran into an issue where I had a PostGIS layer that would draw, but when I tried to hit it with an nquery request, the query failed. Here is some language that I think might help others in this situation.
On this page: http://mapserver.org/input/vector/postgis.html
At the top of the Data Access / Data Connection section, I have a recommended change:
I would modify this paragraph:
The DATA parameter is used to specify the data used to draw the map. The form of DATA is “[geometry_column] from [table_name|sql_subquery] using unique [unique_key] using srid=[spatial_reference_id]”. The “using unique” and “using srid=” clauses are optional, but using them improves performance.
to say:
The DATA parameter is used to specify the data used to draw the map. The form of DATA is “[geometry_column] from [table_name|sql_subquery] using unique [unique_key] using srid=[spatial_reference_id]”. The “using unique” and “using srid=” clauses are optional when drawing features, but using them improves performance. If you want to make MapServer query calls to a PostGIS layer, your DATA parameter must include "using unique". Omitting it will cause the query to fail.
David.
Fixed for 6.0 and trunk in r11992. Also broke long lines and fixed some overfull lines in the PDF documentation (#3947).