It is an interesting problem, kind of a limitation of these OGC HTTP protocols I guess.
I wonder if we could generate the export via a WPS process (which provides the idea of a long running process and "later" retrieval). -- Jody Garnett On 4 September 2015 at 14:46, Jim Proctor <jproc...@lclark.edu> wrote: > Greetings - I’m running GeoServer 2.7, and have to date successfully > downloaded an .mbtiles version of a raster file via Layer Preview only > once—which suggests that all .mbtiles extensions are correctly installed, > but something else is going on. In all other cases I get a 502 error (after > one minute), which I assume is some form of timeout in this case. > > When I look at the log file, it appears that GeoServer is generating a > series of 256x256 tiles, and the process simply takes too long to complete > prior to timeout (one log download included 324 instances, taking place > over two minutes). Is the problem simply that it is taking GeoServer too > long to generate the .mbtiles file, and if so, what do you recommend? (I > did e.g. purge GeoServer memory first via Server Status panel.) > > Btw, if you’re interested why we are doing this, we’re looking for a > workaround for TileMill (no longer supported) to export layers in .mbtiles > format for upload to Fulcrum survey app as offline base layers. > > Regards, > > Jim P. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Geoserver-users mailing list > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
