Part of my question may be academic but, like many technical things, it
becomes practical when getting into the details. I currently have 20 - 30
GB used by geowebcache for SRS 900913 (total for about 12 raster layers).
When a request comes in using 3857, it will not use the 900913 cache. To
use
Hi Jens,
I think you cannot. What about a separate geowebcache instance that tiles
while your geoserver serves up the tiles. Then you can do these things on a
process level.
Cheers
Christian
-
Dr Christian Maul
Project Manager
Information Services Branch
Dep
John,
a truly academic question. Yes - in theory. However, the widespread use of
900913 is a result of the Cinderella treatment of Google by the spatial
fraternity and the past confusion with EPSG:3587 and EPSG:3857.
What geowebcache uses as a default is entirely up to you because in the
geowebca
Nhan,
GeoServer is by default permissive when it comes to namespaces.
Please paste the entire request GET URL into an email so we can see it.
Or the query part (after "?") at least if you do not want to disclose
the host.
Also, note that the schemaLocation in your request is wrong: the WFS 2
Hi, I'm trying to feed Geoserver with the date contained in a Postgresql data
base. I've been reading about how to do this, and I find about the
"Harvesting", so now I know is possible to do what I wanted to do. But I
haven't seen any example or method to do this.
Anyone can give me some directio
Hi ,
we where not able to make progress on this since last week. We are using
GeoServer version 2.3.1 on Ubuntu.
Is there anyone who successfully had GeoServer output polygons that extruded
successfully in Google earth that can share any insight ?
Maybe I can rephrase the question to try to find
I've been starting to use GeoServer caching (geowebcache) more often and
have a question regarding the caching for the web mercator or Google
projection.
The "official" EPSG code for the web mercator projection is EPSG:3857.
GeoServer does support this by default. However, geowebcache uses 9009
When an SLD (containing a rule with a PropertyIsBetween filter) is applied on
a layer using GeoServer 2.1.1 the layer is rendered nicely. If this SLD is
applied on the same layer using GeoServer 2.3.5 the layer is not rendered
and the following error is logged:
Caused by: java.lang.NullPointerExcep
geowolf wrote
> You'll have to be more specific to have any chance to get an answer. Are
> you using app-schema in your feature type?
> Can you provide a detailed description of how that feature type is setup?
No, we are not using app-schema plugin. All our layers (feature types) are
based on tabl
Hi Andrea,
Thanks for the reply! Yes I've added &version=2.0.0, and as I
said it works for other elements like PropertyIsLike and
PropertyIsEqualTo, but for this spatial filter it does not work.
Here's the stack trace from geoserver log:
On 09/09/13 05:17, Andrew Walsh wrote:
> Hi Niels and Andrea,
>
> Thanks Neils so much for resolving this ticket and Andrea for his input.
> ( See https://jira.codehaus.org/browse/GEOS-5400 )
> The freemarker template is an important feature for us and others like the
> AODN.
>
> In fact I was hol
On Tue, Sep 10, 2013 at 1:50 PM, Nhan Vo wrote:
> I've done the same thing in URLs with other filter 2.0 elements like
> PropertyIsLike and PropertyIsEqualTo and they work for me. Could someone
> give me a hint? Thanks!
>
Making a guess here, did you remember to add &version=2.0 in your request
On Tue, Sep 10, 2013 at 1:46 PM, Roel De Nijs wrote:
> When I execute the GetFeature request [1] against a geoserver 2.1.1
> instance I get a gml-string with just 1 feature in the feature-collection
> (as expected). When I execute the same request against a geoserver 2.3.5
> instance the feature
Hi list,
I've tried the following filter in the Demo request page and it works
(even though some elements do not have namespace prefix):
http://www.opengis.net/wfs/2.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:gml="http://www.opengis.net/gml/3.2";
xmlns:fes="
When I execute the GetFeature request [1] against a geoserver 2.1.1 instance I
get a gml-string with just 1 feature in the feature-collection (as expected).
When I execute the same request against a geoserver 2.3.5 instance the feature
collection contains this feature 5 times for some reason.
[
Hi Frederik
During the last weekend I fixed a problem
https://jira.codehaus.org/browse/GEOT-4561
Maybe this will fix your issue too.
You can test with a nightly build or I can send you a jar file.
Christian
On Wed, Sep 4, 2013 at 11:41 AM, Christian Mueller <
christian.muel...@os-solutions.at
16 matches
Mail list logo
