Opened 18 years ago
Last modified 13 years ago
#1905 closed enhancement
missing bounding boxes in wms getcapabilities — at Version 5
Reported by: | Owned by: | mapserverbugs | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | WMS Server | Version: | 4.6 |
Severity: | minor | Keywords: | |
Cc: | tomkralidis |
Description (last modified by )
When offering several spatial reference systems in a mapfile by e.g. using:
"wms_srs" "EPSG:31467 EPSG:31466 EPSG:31468 EPSG:31469 EPSG:25832 EPSG:4326"
bounding box tags for each spatial reference system are missing for at least the root layer in the corresponding wms getcapabilities.
Although this is an optional tag regarding to the wms specification, it should be possible to generate these bounding boxes in the capabilities with mapserver. WMS Clients sometimes use them.
Change History (5)
comment:1 by , 18 years ago
Status: | new → assigned |
---|
comment:2 by , 18 years ago
op_sys: | Solaris → All |
---|---|
rep_platform: | Sun → All |
comment:3 by , 16 years ago
Cc: | added |
---|
comment:4 by , 16 years ago
Description: | modified (diff) |
---|
Do we really want/need this? Imagine for instance a server which advertizes 50 SRS and contains 50 layers... thbose are fairly low numbers for WMS services but would result in 2500 bbox entries, most of them possibly invalid because the bbox is outside the projections' mathematical limits and the reprojection of the bbox results in invalid values.
If you do this then that should be done in a smart way to avoid unnecessarily bloating the Capabilities output, either generate bboxes only for some selected SRS (listed in a new metadata entry), or there should be some limit to the number of bboxes that are generated, or make this disabled by default, or ???
comment:5 by , 16 years ago
Description: | modified (diff) |
---|
is this still a desired enhancement? I can look into this...