Hi,
The direct integration creates a cache on disk that don't expires,
(geowebcache direct integration), while caching headers tell the browser to
cache the tiles for a period of time on the client. So they are 2 different
levels of cache. When you update the data, you have to empty the cache on
Hi Sandro,
it think you can have a better answer in the GeoTools mailing list.
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
Anyway, I guess you can get the envelope of the grid and check the
coordinates on it.
File file = new File(/home/xxx/grid.asc);
AbstractGridFormat
well, I am trying to learn...
I created this bug report: https://jira.codehaus.org/browse/GEOS-6474
-Jakob
jody.garnett wrote
That sounds like a bug :) Are you comfortable reporting it to the
geoserver issue tracker?
--
Jody Garnett
On 29 April 2014 at 3:44:34 pm, Jakob Ventin (
Hello All,
I've looked about but I haven't found any thread discussing this, so forgive me
if it has been covered and please point me to the post.
When I use GetFeature I find floating point numbers are being rounded, but only
when I have the parameter outputFormat=CSV. I am using GeoServer
Hi,
At least it seems that the demo layers do not behave like that. The
topp:states has plenty of double fields and values look the same with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0request=getfeaturetypename=topp:statesoutputformat=JSON
and with
Hi,
You must push the beast into the corner and then you can catch it. Eliminate
one possibility at a time. I would start by converting your data into
shapefile and creating a test layer from that. If it fails in a similar way you
can make a minimal shapefile with couple of features and send
Hello Jukka,
I'm using GeoServer 2.4.5. Interesting that that the demo data behaves
correctly. My data is not from a shapefile. Rather, we have a custom routine
which loads a database from various files, and the layer is defined as a view
in that database.
Raj
-Original Message-
But doesn't the fact that the view works for JSON and XML output suggest that
the view is not the problem?
But your suggested methodology (pushing the beast into the corner, I like
that!) is quite sound. I shall have to figure out how to make a shapefile of it.
Thanks for the suggestion!
*Hi list:*
*I'm trying to run python script done through WPS but geoserver does not
recognize the existence of geoprocesses I created.*
*I'm following the instructions:*
http://docs.geoserver.org/stable/en/user/community/scripting/py/index.html
Hi,
Geoserver WFS should make a zipped shapefile for you with outputformat
SHAPE-ZIP.
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0request=getfeaturetypename=topp:statesoutputformat=SHAPE-ZIP
I don't know why Firefox did not save the URL for me, but the DownThemAll
plugin
Hi,
maybe I need to rephrase my question but before I do that - is there
really no one that could give us any hint what we could to to approach that
in any way ?
Karsten
--
View this message in context:
Hey Pablo,
The python scripting stuff doesn't come by default with the wps module, so
if building from sources you'll have to enable it separately. Instead build
with this command.
mvn clean install -P wps,script,script-py
That should enable the basic scripting functionality plus the python
Maybe you have to set a valid default value in the sql view parameters
table below the view (one existing column) to allow geoserver to validate
the query and check the type of the attribute.
For instance, if your table has the following columns:
gid,value1, value2, the_geom
try to set value1
13 matches
Mail list logo
