Opened 20 years ago
Last modified 15 years ago
#842 closed defect
WMS GetFeatureInfo beyond scale? — at Version 3
Reported by: | Owned by: | dmorissette | |
---|---|---|---|
Priority: | high | Milestone: | 6.0 release |
Component: | WMS Server | Version: | 4.2 |
Severity: | normal | Keywords: | |
Cc: | assefa, dmorissette |
Description (last modified by )
I don't know if I would call this a bug, but the current behaviour of MapServer's WMS GetFeatureInfo is to allow a request to be made even when the layer is not shown on the map (outside of its scale range). I think that the scale dependencies of a layer should be respected for both the GetMap and GetFeatureInfo requests, and a request made using BBOX where the layer wouldn't be visible should return an exception.
Change History (3)
comment:2 by , 20 years ago
looking into this. When I quickly checked the code It seemed that this shoudl not be happen (the map extents/width are modified before the query is done so the query should have failed if layer was out of sacale). BTW : before I check this I just checked the gml file returned from your requests and there seems to be no geometry component in it ? Is this a problem with the data ? That could explain why we do not see anything in the GetMap request. Can you please check this aspect for me ? <msGMLOutput xmlns:gml="http://www.opengis.net/gml" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ROADS_layer> <ROADS_feature> <gid>61520</gid> <streetname>Nelson St</streetname> <aliasname></aliasname> <rd_class>local</rd_class> <rd_classid>8</rd_classid> </ROADS_feature> ...
comment:3 by , 17 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Milestone: | → 5.2 release |
Owner: | changed from | to
I have had reports that scale is ignored by GetFeatureInfo in MapServer 5.0.
This would be nice to fix in 5.2.
Note:
See TracTickets
for help on using tickets.