Sorry I don't have this on a public endpoint. I'll try to put up a public
endpoint somewhere when I get a chance.
I tried using a WMS 1.1.1 and GeoServer is showing the native SRS EPSG:3857
that is currently published.
Next I declared EPSG:4269 and selected "re-project native to declared."
When I check GeoServer GetCapabilities 1.3.0, I see the following which
appears to be what I want:
.
.
<CRS>EPSG:42304</CRS>
<CRS>EPSG:42303</CRS>
<CRS>CRS:84</CRS>
-<EX_GeographicBoundingBox>
<westBoundLongitude>-180.0</westBoundLongitude>
<eastBoundLongitude>180.0</eastBoundLongitude>
<southBoundLatitude>-85.0</southBoundLatitude>
<northBoundLatitude>85.0</northBoundLatitude>
</EX_GeographicBoundingBox>
-<Layer queryable="0">
<Name>test:Aerial</Name>
<Title>Aerial</Title>
<Abstract/> <KeywordList/>
<CRS>EPSG:4269</CRS>
<CRS>CRS:84</CRS>
-<EX_GeographicBoundingBox>
<westBoundLongitude>-180.0</westBoundLongitude>
<eastBoundLongitude>180.0</eastBoundLongitude>
<southBoundLatitude>-85.0</southBoundLatitude>
<northBoundLatitude>85.0</northBoundLatitude>
</EX_GeographicBoundingBox>
<BoundingBox maxy="180.0" maxx="85.00000000006392"
miny="-180.0" minx="-85.00000000006392" CRS="EPSG:4269"/>
</Layer>
</Layer>
It looks good until I try a GetMap Request:
http://localhost:8080/geoserver/test/wms?service=WMS&version=1.3.0&request=G
etMap&layers=test:Aerial&styles=&bbox=35,-105,40,-100&width=500&height=500&c
rs=EPSG:4269&format=image/jpeg
which returns a service error report:
<ServiceException>
Error rendering coverage on the fast path
java.net.ConnectException: Connection refused: connect Connection refused:
connect
</ServiceException>
Thanks for the help.
Randy
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Andrea Aime
Sent: Monday, August 01, 2011 1:02 PM
To: Randy George
Cc: [email protected]
Subject: Re: [Geoserver-users] native SRS for WMS Cascading
On Mon, Aug 1, 2011 at 8:14 PM, Randy George <[email protected]> wrote:
>
>
> Id like to use the cascade proxy capability of GeoServer 2.1.1 for a
> simple in house WMS service. The service defines a test layer with an
> EPSG:3395 CRS, which Id like GeoServer to recognize as the native SRS
> when publishing a test layer, but Im not having success. GeoServer is
> showing Native SRS as UNKNOWN.
>
>
>
> How does the Native SRS need to be indicated in a WMS 1.3.0 or 1.1.1
> GetCapabilities XML?
Did you try cascading it as a WMS 1.1 server instead?
GeoServer 2.1.1 is at least able to cascade some WMS 1.3 servers, but I
could not try it no more than 2-3 instances.
The epsg code you're mentioning is supported, so it _should_ work, no idea
why it's not working.
If you have that server available on the internet send me a links to its
capabilities documents and I'll have a look as spare time allows (weekends)
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
