Opened 19 years ago
Closed 16 years ago
#1396 closed defect (fixed)
[WMS Server] Missing LatLongBoundingBox Warning
Reported by: | Owned by: | tomkralidis | |
---|---|---|---|
Priority: | high | Milestone: | 5.2 release |
Component: | WMS Server | Version: | 4.6 |
Severity: | normal | Keywords: | |
Cc: | assefa, dmorissette, jmckenna |
Description
For a WFS Server, when you do a GetCapabilities request on a layer with an incorrect data path you get the following warning: ******* - <!-- WARNING: Mandatory LatLongBoundingBox could not be established for this layer. Consider setting LAYER.EXTENT or wfs_extent metadata. --> ******* For a WMS Server the <LatlongBoundingBox> and <BoundingBox> sections are missing for the layer in the GetCapabilities, and no warning is displayed.
Change History (6)
comment:2 by , 16 years ago
Cc: | added |
---|
comment:3 by , 16 years ago
Cc: | added; removed |
---|---|
Owner: | changed from | to
Status: | new → assigned |
Done in r7719. Committed the same behaviour in mapwms.c and updated warning message (note that this is an optional and not mandatory parameter, per the OGC DTDs and schemas).
I do agree the error message can be misleading somewhat. In the code, I think it's the right warning to print (since it is testing for an extent). There is no checking in the code that the data exists.
Perhaps this should be a check done earlier to see if the data even exists.
Or should we simply extend the warning message to suggest "check that your data exists" type thing.
Comments?
comment:4 by , 16 years ago
Milestone: | → 5.2 release |
---|
comment:5 by , 16 years ago
I vote for extending the warning message.
If there's no objections, I will commit and close this one out.
comment:6 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Warning message extended in r7741. Closing.