Opened 11 years ago
Closed 8 years ago
#5180 closed enhancement (wontfix)
Expose FEATURE_COUNT parameter for WMS GetFeatureInfo request
| Reported by: | anyidea | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | default | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Since the parameter is not specified in the request, it always takes the default value of 1 It could be useful to expose this parameter in the API.
Change History (3)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
I am still willing to know a use case. I know that gdallocationinfo is sending GetFeatureInfo requests, would on increased FEATURE_COUNT help if the WMS layer is defined as a group layer or what do you have on your mind, anyidea?
comment:3 by , 8 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
It would be interesting to know an exact use case for this feature. For occasional use I would try a workaround by defining the base URL of the WMS service with &FEATURE_COUNT= in <ServerUrl> of the GDAL_WMS definition file http://www.gdal.org/frmt_wms.html.