[Geoserver-devel] Bounding box differences in requests

GeoServer GeoServer Developer
1

Hi List,
While looking at my log for a single tile request, I see GeoServer is making four separate requests to Oracle, one for each layer. This is as expected.

The weird thing is that for every one of the requests, a different bounding box is supplied to Oracle. I have the following four (easiest to see with wide-screen no word-wrap).

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(410006.8,278115.6,411445.99999999994,279554.8))

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(410002.6,278111.39999999997,411450.19999999995,279559.0))

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(409999.8,278108.6,411452.99999999994,279561.8))

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(409998.39999999997,278107.19999999995,411454.39999999997,279563.2))

The difference between them is 9metres on both width and height.

Two thoughts:
a) Doesn’t this add scope for missing/adding features that shouldn’t be there? 9m is several buildings zoomed out to 1:5000, the max denominator on our detailed dataset.

b) Is there room for a (probably minor performance gain) optimisation to only create it once?

Cheers,
Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

2

The request may be adjusted to account for symboliser size at your current scale. If you have a symbol of 16.x16 pixels, we want to expand the request area for that layer by 8 pixels in each direction (in order to collect any features that are “just” off-screen, but may end up being visible when drawn.

Jody Garnett

On 15 October 2013 at 2:08:59 AM, Jonathan Moules (jonathanmoules@anonymised.com) wrote:

Hi List,
While looking at my log for a single tile request, I see GeoServer is making four separate requests to Oracle, one for each layer. This is as expected.

The weird thing is that for every one of the requests, a different bounding box is supplied to Oracle. I have the following four (easiest to see with wide-screen no word-wrap).

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(410006.8,278115.6,411445.99999999994,279554.8))

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(410002.6,278111.39999999997,411450.19999999995,279559.0))

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(409999.8,278108.6,411452.99999999994,279561.8))

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(409998.39999999997,278107.19999999995,411454.39999999997,279563.2))

The difference between them is 9metres on both width and height.

Two thoughts:
a) Doesn’t this add scope for missing/adding features that shouldn’t be there? 9m is several buildings zoomed out to 1:5000, the max denominator on our detailed dataset.

b) Is there room for a (probably minor performance gain) optimisation to only create it once?

Cheers,
Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation. ------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

3

Hi Jody,
I hadn’t considered that aspect.However three of those layers are symbolised as nothing more than regular polygons/lines. The highest stroke-width is 3.

The fourth layer reads line features which are then labelled.

In this circumstance should there be such adjustment to the bbox?
Cheers,
Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

···

On 17 October 2013 05:24, Jody Garnett <jody.garnett@anonymised.com> wrote:

The request may be adjusted to account for symboliser size at your current scale. If you have a symbol of 16.x16 pixels, we want to expand the request area for that layer by 8 pixels in each direction (in order to collect any features that are “just” off-screen, but may end up being visible when drawn.

Jody Garnett

On 15 October 2013 at 2:08:59 AM, Jonathan Moules (jonathanmoules@anonymised.com) wrote:

Hi List,
While looking at my log for a single tile request, I see GeoServer is making four separate requests to Oracle, one for each layer. This is as expected.

The weird thing is that for every one of the requests, a different bounding box is supplied to Oracle. I have the following four (easiest to see with wide-screen no word-wrap).

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(410006.8,278115.6,411445.99999999994,279554.8))

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(410002.6,278111.39999999997,411450.19999999995,279559.0))

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(409999.8,278108.6,411452.99999999994,279561.8))

MDSYS.SDO_GEOMETRY(2003,27700,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(409998.39999999997,278107.19999999995,411454.39999999997,279563.2))

The difference between them is 9metres on both width and height.

Two thoughts:
a) Doesn’t this add scope for missing/adding features that shouldn’t be there? 9m is several buildings zoomed out to 1:5000, the max denominator on our detailed dataset.

b) Is there room for a (probably minor performance gain) optimisation to only create it once?

Cheers,
Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation. ------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

4

On Thu, Oct 17, 2013 at 2:38 PM, Jonathan Moules <
jonathanmoules@anonymised.com> wrote:

Hi Jody,
I hadn't considered that aspect.However three of those layers are
symbolised as nothing more than regular polygons/lines. The highest
stroke-width is 3.

The stroke width is taken into account and used to enlarge the query bboxes.
Labels are not, no (easy) way to predict how long they can get

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

5

Ah Ok. It seemed weird, so worth asking. Sometimes it turns out to be innocuous, sometimes not.
Cheers,
Jonathan

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

···

On 17 October 2013 13:43, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Thu, Oct 17, 2013 at 2:38 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:

Hi Jody,
I hadn’t considered that aspect.However three of those layers are symbolised as nothing more than regular polygons/lines. The highest stroke-width is 3.

The stroke width is taken into account and used to enlarge the query bboxes.
Labels are not, no (easy) way to predict how long they can get

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it