Opened 16 years ago
Closed 13 years ago
#769 closed enhancement (wontfix)
Automatically calculate bounds for WMS
Reported by: | zspitzer | Owned by: | |
---|---|---|---|
Priority: | medium | Milestone: | |
Component: | WMS Interface | Version: | |
Severity: | major | Keywords: | |
Cc: | External ID: |
Description
following up on http://www.nabble.com/WMS-GetCapabilities-td20519654.html
apparently MapGuide requires bounds to be defined for publishing via WMS.
When bounds aren't defined, these could be simply calculated (and cached)
see #768
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 15 years ago
Version: | 2.0.2 |
---|
Removing version from enhancement request. If this enhancement request has been addressed or is no longer required, please close ticket.
comment:3 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Client tools (ie. Maestro) can do this
Note:
See TracTickets
for help on using tickets.
I remember asking for this when this feature was first developed. I believe the argument against doing this was that these values would get stale if the data was updated. Then of course, there was the issue of having enough time to do it in the first place.