1

I have a layer with the following bounding box:

bounding box before request

A bot (baidu spider) has been making the following request periodically: /geoserver/si-x/wms/kml?layers=si-x:zabelli_leaf_ncep

This request causes the bounding box to change to the following:

bounding box after request

Any ideas why? If I click "Compute from native bounds" and save the layer it will be fine until the bot hits the layer again at which point the bounds revert to the numbers in the second screen shot. If I make a similar request from a browser

http://myGeoserver/geoserver/wms/kml?&layers=gdd:agdd_50f

I don't receive an error, a .kml file downloads, and the bounds of the layer are messed up again. Any ideas on why this request would cause the Lat/Lon Bounding Box of the layer to change?

  • 1
    Sounds really odd and it would be interesting to reproduce the issue. What datastore do you use? – user30184 Jun 20 '16 at 20:49
  • The datastore is ImageMosaic using the Image mosaicking plugin. – apricity Jun 20 '16 at 21:02
  • I'd be really interested to know if anyone is successful or not in replicating this behavior. In my particular case the layers are time-series raster layers using imagemosaic. Imagemosaic looks to postgres to get the paths of daily geotifs which it then serves out. At this point I'm trying to figure out if it's a bug or a configuration issue. – apricity Jun 22 '16 at 17:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.