On Fri, 8 Apr 2011 21:46:24 +0200, Andrea Aime
wrote:
> On Fri, Apr 8, 2011 at 8:51 PM,
> wrote:
>> Hi Everyone,
Hello Andrea,
We'd be interested in learning more about "parallelism for a single
request".
Would you please advise us as to how to learn more about this
subject.
On Fri, Apr 8, 2011 at 8:51 PM, wrote:
> Hi Everyone,
>
> We are using GeoServer 2.0.2 and serving a layer group which
> combines raster (i.e. image mosaic) and vector data. Our performance is
> really slow at the "10th" zoom level when our data isn't entirely
> cached. (Caching this lay
Hi Everyone,
We are using GeoServer 2.0.2 and serving a layer group which
combines raster (i.e. image mosaic) and vector data. Our performance is
really slow at the "10th" zoom level when our data isn't entirely
cached. (Caching this layer would take way too long).
We are using S
Hi Again,
sorry for the private reply, I just forgot to add the list.
If this got removed after 2.0, then this was probably done with good
reason. But maybe the attributes should be removed from the
documentation in that case.
I am now using DescribeFeatureType.
Have a nice weekend,
Mirko
On
Hi Mirko,
(Please keep all correspondance on the public list)
It is kind of complex but essentially when you do see attributes in that
list it is an artifact of that feature type coming form an older (pre 2.0)
data directory. If you really want the details see this bug report:
http://jira.codeha
Hi Mirko,
Yeah the way geoserver uses these attributes is kind of tricky. Depending on
how you have your feature type configured you may get attributes in this
list, or you may not. The norm is to keep the list empty which means to
generate attributes from the schema of the underlying data source.
Hello,
I am looking for a way to get the attributes of a feature type with the
REST configuration API. After looking at the documentation I thought
that I could use a call like
"/workspaces//datastores//featuretypes/[.]" to get
this Information, as it is returned in the example documents (e.g.
On Fri, Apr 8, 2011 at 12:23 PM, Christian Seewald
wrote:
> I am using GeoServer version 2.0.1. I am having a problem in WFS 1.1.0 with
> axis ordering in a BBOX filter (also tried 2.1 RC 3, same problem).
>
> A WFS 1.1.0 capable map client issues an http-POST GetFeature request,
> including a spa
Hi Jukka,
Thanks for your help. I should have figured it out myself by carefully reading
http://docs.geoserver.org/latest/en/user/services/wfs/basics.html, but
unfortunatelly did not. I do not have control over the wfs client but I can
inform the developers to change this detail in order to be
Hi,
Geoserver is in some places using the traditional axis order with EPSG:4326 in
order to make old applications to function. I would have a try by giving
srsName as urn:x-ogc:def:crs:EPSG:4326 but I cannot guarantee that it works.
-Jukka Rahkonen-
L
Hi Alex,
I did as u explained, first created datastore without , it got created
successfully and then used PUT as
$ curl -v -XPUT -u admin:geoserver -H 'Content-type: text/plain' -d
'file:data/bluemarble.tif'
"http://localhost:8084/geoserver/rest/workspaces/Apna/coveragestores/bluemarble/bluemar
I am using GeoServer version 2.0.1. I am having a problem in WFS 1.1.0 with
axis ordering in a BBOX filter (also tried 2.1 RC 3, same problem).
A WFS 1.1.0 capable map client issues an http-POST GetFeature request,
including a spatial constraint:
http://www.opengis.net/wfs";>
http://gkin
Hello Christian,
I have raster images in oracle 11g georaster tables. I need to add these
images dynamically to my application. I could add a coverage store using
rest api and curl but how do I publish the layer or add the coverage now?
--
View this message in context:
http://osgeo-org.1803224.
13 matches
Mail list logo
