Setting LAYER EXTENT with OGR VRT Data Source doesn't stop check for layer extent

MapServer / MapServer-import

3 stars 2 forks source link

Setting LAYER EXTENT with OGR VRT Data Source doesn't stop check for layer extent #1804

Open tbonfort opened 12 years ago

tbonfort commented 12 years ago

Reporter: tims@commenspace.org Date: 2006/06/20 - 01:49

It looks like setting an EXTENT at the LAYER level should stop LayerGetExtent
from getting called.  I have an OGRVRTLayer with a MySQL data source.  The LAYER
EXTENT is specified in the mapfile, but the MySQL Query log still shows two
queries being made to the database.  I'm assuming this means that the layer
extent is still being checked.  Defining "wms_extent" metadata for the layer
also doesn't stop the duplicate query.

tbonfort commented 12 years ago

Author: dmorissette Date: 2006/06/20 - 15:31

Frank, any idea on this?

tbonfort commented 12 years ago

Author: fwarmerdam Date: 2006/08/16 - 21:50

I'll take this one, and see if I can reproduce it.

tbonfort commented 12 years ago

Author: hobu Date: 2006/08/27 - 20:30

All LayerGetExtent calls should be short circuited if LAYER EXTENT is set.  I
don't think this is being done at all currently.  I know we wanted to do this,
but it must have been pushed off to wait for the vtable stuff first.

tbonfort commented 12 years ago

Author: warmerdam Date: 2007/08/04 - 01:09 I have tested WMS GetCapabilities requests with a slight variation of this file. I have established that:

if wms or ows extent metadata is set, this is used and no further extent request is made.
if wms/ows extent metadata is not set, but the EXTENT keyword is used to set the layer extent, this is used and no further extent request is made.

As far as I can tell, everything is now working fine. Please re-open if there is a specific problem that can be demonstrated.