This Issue is related to Issue 30. Initially the raster download calculation
was incorrect in that it was being too restrictive. After Aleda's change it is
not sometimes being too permissive. We want to keep our pipe from getting too
busy, also GeoServer's currently set memory limit can result in no raster being
downloaded.
To tease out what's going on multiple requests would need to be made of various
datalayers at various scales, to see by the formula what the MB should be, then
compare to the actual download size. Firebug doesn't show the bare request to
GeoServer but it's possible that the actual request could be seen in the
haproxy log.
At this point we don't want to put in the time to investigate further. This is
being documented in case we pick it up again. Aleda has some notes in email
that could be used as well.
Original issue reported on code.google.com by Aleda.Fr...@state.ma.us on 9 Jan 2012 at 9:14
Original issue reported on code.google.com by
Aleda.Fr...@state.ma.uson 9 Jan 2012 at 9:14