On Thu, Sep 4, 2014 at 3:07 AM, Stephen Brooke sbro...@mdacorporation.com
wrote:
I am using GeoServer 2.5.1 at the moment. I am wondering what support
GeoServer has for BigTiff files as I cannot find any mention of it in the
GeoServer documentation, although when I search “GeoServer BigTiff
Dear list,
sorry for cross-posting (see also: http://tinyurl.com/nwxvew6) but I am stuck. I am trying to style negative values in Geoserver via SLD and would like to know how the syntax in SLD should look like to do this. What I have is the following:
---snip---
?xml version=1.0
On Thu, Sep 4, 2014 at 10:46 AM, Jan Peters peters...@gmx.at wrote:
to this:
ogc:Literal-0.828977/ogc:Literal
But this doesn't work either (Geoserver tells me that my SLD is not
valid). I also reduced the number of rows in the PostGIS table to one and
tried positive and negative values for
On Thu, Sep 4, 2014 at 10:57 AM, Andrea Aime andrea.a...@geo-solutions.it
wrote:
On Thu, Sep 4, 2014 at 10:46 AM, Jan Peters peters...@gmx.at wrote:
to this:
ogc:Literal-0.828977/ogc:Literal
But this doesn't work either (Geoserver tells me that my SLD is not
valid). I also reduced the
On Thu, Sep 4, 2014 at 11:06 AM, Jan Peters peters...@gmx.at wrote:
Well, the double nested Literals is what QGis created automatically.
Eh, I would not trust QGis to generate SLDs GeoServer can interpret (and in
this case, not even valid SLDs at all,
regardless of what GeoServer can grok).
On Thu, Sep 4, 2014 at 11:12 AM, Jan Peters peters...@gmx.at wrote:
Ok, I won't tust it. What is the most trustable software to create SLDs
btw?
uDig, generates valid SLD 1.0 files that also have GeoServer own extensions
to the SLD syntax
(instead of QGis, which does SLD 1.1, sometimes
Jan, could you please keep the mailing list cc'ed?
About the error, try enabling verbose logging and then
see what the sql query being generated is.
Cheers
Andrea
On Thu, Sep 4, 2014 at 11:16 AM, Jan Peters peters...@gmx.at wrote:
Well, I now tried this SLD (Geoserver validated it now):
I am out of the office from Thu 04/09/2014 until Fri 05/09/2014.
If your enquiry is urgent please contact Paul Freeman, or the IT helpdesk
on 01382 438000.
Note: This is an automated response to your message Geoserver-users
Digest, Vol 100, Issue 12 sent on 04/09/2014 5:28:42.
This is the
Ah, this cannot work, or course:
SELECT
pk,
percentage_change,
encode(
ST_AsBinary (ST_Force_2D(the_geom)),
base64
) AS the_geom
FROM
public.trnsfrm_meta_outputmap_jan
WHERE
(
the_geom ST_GeomFromText (
POLYGON ((3972989.8359375 3248544.234375, 3972989.8359375 3270607.265625,
Looking at your style, there are still some - signs in the wrong places
Cheers
Andrea
On Thu, Sep 4, 2014 at 11:26 AM, Jan Peters peters...@gmx.at wrote:
Ah, this cannot work, or course:
SELECT
pk,
percentage_change,
encode(
ST_AsBinary (ST_Force_2D(the_geom)),
Ok, Andrea, I fixed the respective parts and now it works. So conclusio is:
1. use: ogc:Literal-0.828977/ogc:Literal for your negatives, not double nested Literal
2. turn on verbose logging in the Geoserver interface (Settings -- Global) if you have any similar problems
Thanks again
Jan
Hi,
We have a wfs and wms layer pointing to same table in Geoserver using
projection 29903 but the position of the features aren't in same location
when compared between the two. We wondered if this is because of inaccuracy
of GeoServer reprojecting the wms layer?
Has there been a change since
Hello,
i'm trying to create an image pyramid layer for images in a local coordinate
system using geoserver 2.5.2.
I created the image pyramid with gdal as described in the geoserver
documentation, but when i try to create the store and publish the layer, i get
an error message (see below).
I think the problem lies in the second exception showed in the bottom of your
trace stack:
Caused by: org.opengis.referencing.operation.OperationNotFoundException: No
transformation available from system EngineeringCRS[Wildcard 2D cartesian
plane in metric unit] to GeographicCRS[WGS84(DD)].
Dear all,
Configuring a cascading WMS, one has to provide Connection Info, for example
the Capabilities URL. Although I provide a full Capbilities URL to a WMS 1.3
service, the actual request sent to remote WMS has the string
REQUEST=GetCapabilitiesVERSION=1.1.1SERVICE=WMS tagged onto the end.
Hi,
Please check what you get back from the remote server if you send a
GetCapabilities request with VERSION=1.3.0. I bet it is sending back a
document in WMS 1.1.1 format because it does not support WMS 1.3.0. After that
Geoserver continues discussion with the WFS 1.1.1 protocol. This is by
Hi,
This may be TL;DR. However, names with special characters are an eternal
battle. If someone verifies that what I write makes sense it might be good to
include it in some place in Geoserver documentation.
Short version: WMS standard allows anything in layer names but WFS standard
puts
Hi,
As a simple workaround I would just claim that images are for example in some
UTM zone.
-Jukka Rahkonen-
Lähettäjä: Wilhelm, Dirk [mailto:wilh...@geomapping.de]
Lähetetty: 4. syyskuuta 2014 15:19
Vastaanottaja: 'Geoserver-users@lists.sourceforge.net'
Aihe: [Geoserver-users] Image pyramid
On Thu, Sep 4, 2014 at 3:12 PM, Rahkonen Jukka (Tike)
jukka.rahko...@mmmtike.fi wrote:
Hi,
Please check what you get back from the remote server if you send a
GetCapabilities request with VERSION=1.3.0. I bet it is sending back a
document in WMS 1.1.1 format because it does not support
Hi,
Thanks for your pointers. The upstream WMS server (SharpMap) ONLY supports WMS
1.3. Sending a proper, full GetCapabilities request version 1.3 to the upstream
WMS server using wget or the web browser, I get the proper document in
response.
The client here is GeoServer, as I am configuring
On Thu, Sep 4, 2014 at 3:47 PM, Edward Mac Gillavry
emacgilla...@hotmail.com wrote:
Hi,
Thanks for your pointers. The upstream WMS server (SharpMap) ONLY supports
WMS 1.3. Sending a proper, full GetCapabilities request version 1.3 to the
upstream WMS server using wget or the web browser, I
And the GetMap url in server GetCapabilities does not contain that
version=1.1.1 part?
-Jukka Rahkonen-
Lähettäjä: Edward Mac Gillavry [mailto:emacgilla...@hotmail.com]
Lähetetty: 4. syyskuuta 2014 16:48
Vastaanottaja: Andrea Aime; Rahkonen Jukka (Tike)
Kopio:
Hello and good day,
I have what I think is a simple question. I am trying to make a WCS
1.1.1 GetCoverage request to a Geoserver running version 2.5
That's right: the GetMap URL does not contain any reference to a version
number, not even 1.1.1.
Edward
From: jukka.rahko...@mmmtike.fi
To: emacgilla...@hotmail.com
CC: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Config cascading WMS 1.3: Capabilities req
params
Hi,
Will upgrade GS version and check whether issue persists.
Thanks,
Edward
Date: Thu, 4 Sep 2014 15:51:28 +0200
Subject: Re: [Geoserver-users] Config cascading WMS 1.3: Capabilities req
params overruled
From: andrea.a...@geo-solutions.it
To: emacgilla...@hotmail.com
CC:
Hi,
That feels odd. Unfortunately without URL to that server it is hard to help you
farther. Try to find some public ShapMap server which behaves similarly, or
test if you can repeat the issue with http://demo.opengeo.org/geoserver/wms or
http://demo.mapserver.org/wms.
Do not test with
I'm not going to be of much help on this.
I've noticed some very odd stuff with WCS.
http://sedac.ciesin.columbia.edu/geoserver/ows?SERVICE=WCSVERSION=1.1.1REQUEST=DescribeCoverageIDENTIFIERS=species-v1-global-amphibian-family-richness
Things I've observed are:
* The grid definition's axis
Hi,
It would be much easier for us if you can repeat the issue with some of the
Geoserver demo layers. Without your data we are somewhat blind.
Do you get correct pixel size with WCS 1.0.0 and resx + resy? I have not
played at all with WCS 1.1.0 yet and I not know when GridOffsets can be
Hi,
I've noticed both of your reports, but unfortunately I won't have an
occasion to look into them for some time,
as I'll be away.
The WCS 1.1 service is mostly tested from XML requests, KVP have oddities
(what is mandatory in
XML is not in KVP) I would not be surprised if there are issues
Excellent summary, probably should be in the docs or a blog post :)
I always view it as name being for machine to machine communication (never
shown to users) and title being human readable.
Jody Garnett
On Thu, Sep 4, 2014 at 6:16 AM, Rahkonen Jukka (Tike)
jukka.rahko...@mmmtike.fi wrote:
Good catch Jukka.
Kytt, your grid definition is citing this default grid type: 2dGridIn2dCrs
That means you'd have to use 4 values for your offsets. Also, keep your
signon the numbers. The grid knows how it's defined. You can see this
by describing the coverage. (The DescribeCoverage
Please email the user list haktan, if you are interested in direct email or
phone support GeoServer has a page for commercial support.
* http://geoserver.org/support/
The GeoServer project simply repackages the map fish printing module, any
questions about use are best directed there.
Jody
Hi haktan, can you share the config.yaml you are using?
Thanks
Mauro
2014-09-04 18:51 GMT+02:00 Jody Garnett jody.garn...@gmail.com:
Please email the user list haktan, if you are interested in direct email
or phone support GeoServer has a page for commercial support.
*
33 matches
Mail list logo
