[Geoserver-devel] Remove bounding box from regionated KML query?

Hi,

I was trying to throw more data at our KML regionating stuff and ran into the query below, which occurs when someone asks for a tile and the H2 database has already been built.

null
Translator error
Could not aquire feature:org.geotools.data.DataSourceException: Error Performing SQL query:
... query ...
ERROR: Operation on two geometries with different SRIDs

This database doesn't have anything but 4283 in it, so I am somewhat curious what makes this error happen, but more importantly can we just remove the bounding box filter? The result appears to be the same, and no complaints from Postgis.

It's probably not cheap, and we shouldn't need it anyway I think. I'm guessing at line 417 in KMLTransformer.java

-Arne

SELECT "ogc_fid", encode(asBinary(force_2d("geometry"),'XDR'),'base64'), "gid", "pin", "class", "identifier", "purpose", "vesting", "name", "name_stat", "legal_area", "clw_code", "category", "iucn" FROM "public"."DEC-007" WHERE (((TRUE AND TRUE) AND "geometry" && GeometryFromText('POLYGON ((90 -45.000000042821874, 90 0, 135 0, 135 -45.000000042821874, 90 -45.000000042821874))', 4283)) AND ("ogc_fid" = '1') OR ("ogc_fid" = '101') OR ("ogc_fid" = '102') OR ("ogc_fid" = '103') OR ("ogc_fid" = '104') OR ("ogc_fid" = '105') OR ("ogc_fid" = '1078') OR ("ogc_fid" = '1079') OR ("ogc_fid" = '129') OR ("ogc_fid" = '1343') OR ("ogc_fid" = '1344') OR ("ogc_fid" = '1719') OR ("ogc_fid" = '1720') OR ("ogc_fid" = '1827') OR ("ogc_fid" = '1839') OR ("ogc_fid" = '1886') OR ("ogc_fid" = '1887') OR ("ogc_fid" = '1888') OR ("ogc_fid" = '225') OR ("ogc_fid" = '691') OR ("ogc_fid" = '720') OR ("ogc_fid" = '721') OR ("ogc_fid" = '722') OR ("ogc_fid" = '815') OR ("ogc_fid" = '816') OR ("ogc_fid" = '817') OR ("ogc_fid" = '833') OR ("ogc_fid" = '834') OR ("ogc_fid" = '835') OR ("ogc_fid" = '836'));

(The data is available if you ssh to atlas, then connect to -h db.opengeo.org -d landgate , username and pass can be found on the wiki page for demo.opengeo.org )

Arne Kepp ha scritto:

Hi,

I was trying to throw more data at our KML regionating stuff and ran into the query below, which occurs when someone asks for a tile and the H2 database has already been built.

null
Translator error
Could not aquire feature:org.geotools.data.DataSourceException: Error Performing SQL query:
... query ...
ERROR: Operation on two geometries with different SRIDs

This database doesn't have anything but 4283 in it, so I am somewhat curious what makes this error happen, but more importantly can we just remove the bounding box filter? The result appears to be the same, and no complaints from Postgis.

Yeah, we could... but the bbox is there also for normal kml
requests, and it seems we're failing to reproject the filter...
odd, I'll have a look at it.

Can you open a jira issue for this?

Cheers
Andrea