<br><font size=2 face="sans-serif">Hi Johan</font>
<br>
<br><font size=2 face="sans-serif">It is not on me to answer on your feature-request.
</font>
<br>
<br><font size=2 face="sans-serif">Maybe the following SQL-Statement is
helpfull for you. It delivers the</font>
<br><font size=2 face="sans-serif">Oracle-Metadata:</font>
<br>
<br><font size=2 face="sans-serif">select owner,table_name,column_name,d.*</font>
<br><font size=2 face="sans-serif">from all_sdo_geom_metadata m,</font>
<br><font size=2 face="sans-serif"> table(m.DIMINFO)
d</font>
<br>
<br><font size=2 face="sans-serif">Since the result of this query is
a simple relation (no oracle-objects) it</font>
<br><font size=2 face="sans-serif">can be used from any Oracle-Interface
(xDBC, ADOxxx, ...)</font>
<br>
<br><font size=2 face="sans-serif">By</font>
<br><font size=2 face="sans-serif">Benedikt</font>
<br>
<br><font size=2><tt>UMN MapServer Developers List <MAPSERVER-DEV@LISTS.UMN.EDU>
schrieb am 26.02.2006 12:53:04:<br>
<br>
> I hope you all understood that there still is a need for function
that<br>
> retrieves the layerextent from metadata if it's available (as Frank<br>
> mentions). In my case we have over a million records in the table
and to<br>
> calculate extent for the layer by go true all those records will take
to<br>
> much time.<br>
> <br>
> Best regards<br>
> Johan<br>
> <br>
> ___________________________________<br>
> <br>
> <br>
> Johan Hallgren<br>
> WM-data<br>
> <br>
> <br>
> Pelle Bergs backe 3<br>
> Box 1938, 791 19 Falun<br>
> Tel: 023-844 65 (int: +46-2384465)<br>
> Mobil: 070-588 44 28 (int: +46-705884428)<br>
> johan.e.hallgren@wmdata.com<br>
> http://www.wmdata.se<br>
> <br>
> -----Original Message-----<br>
> From: UMN MapServer Developers List [mailto:MAPSERVER-DEV@LISTS.UMN.EDU]<br>
> On Behalf Of Daniel Morissette<br>
> Sent: den 24 februari 2006 21:18<br>
> To: MAPSERVER-DEV@LISTS.UMN.EDU<br>
> Subject: Re: [UMN_MAPSERVER-DEV] OracleSpatial 10i GetExtent slow<br>
> <br>
> Sean Gillies wrote:<br>
> > On Feb 24, 2006, at 8:12 AM, Frank Warmerdam wrote:<br>
> > <br>
> >> Hallgren Johan E wrote:<br>
> >><br>
> >>> Hello<br>
> >>><br>
> >>> I have used the mapscript function getExtent for a layer,
to get the<br>
> >>> extent, that one was slow. Do you mean that the msOWSGetLayerExtent<br>
> >>> would be faster?<br>
> >>><br>
> >>> Could it be possible to change the logic so the function
I need<br>
> would<br>
> >>> run the msOWSGetLayerExtent instead?<br>
> >><br>
> >><br>
> >> Johan / others,<br>
> >><br>
> >> I'm no expert on this area of the code, but it definitely
seems like<br>
> we<br>
> >> ought to offer a mapscript mechanism that works like <br>
> >> msOWSGetLayerExtent,<br>
> >> using layer metadata if available.<br>
> >><br>
> >> In the meantime Johan, if you already know your extents (as
you<br>
> would <br>
> >> have<br>
> >> to for setting up OWS metadata on a layer) you could just
modify your<br>
> >> mapscript application to hardcode the extent or perhaps to
pull it <br>
> >> manually<br>
> >> from layer metadata.<br>
> > <br>
> > <br>
> > Layers have an extent just like the map, so that's probably better<br>
> than <br>
> > the metadata. layerObj.getExtent will preferentially return the<br>
> layer's <br>
> > extent attribute, and then fall back on a query of the datasource.<br>
> > <br>
> > I can't say for sure if this is implemented for the PHP mapscript.<br>
> > <br>
> <br>
> Yes, PHP MapScript's $layer->getExtent() calls msLayerGetExtent()
<br>
> directly the same way as the SWIG equivalent.<br>
> <br>
> Daniel<br>
> -- <br>
> ------------------------------------------------------------<br>
> Daniel Morissette
dmorissette@dmsolutions.ca<br>
> DM Solutions Group
http://www.dmsolutions.ca/<br>
> ------------------------------------------------------------<br>
</tt></font>