I would like to know how the the common SRS generated in the WMF GetCapabilities request. I am receiving the following in my response from WMS GetCapabilities request:
EPSG:
I would like to figure out what I have done to cause this since it causes problems for ESRI’s ArcMap.
Thank you,
Alan
On Mar 26, 2008, at 11:44 AM, Smith, Alan G. wrote:
I would like to know how the the common SRS generated in the WMF GetCapabilities request. I am receiving the following in my response from WMS GetCapabilities request:
<!--common SRS:-->
<SRS>EPSG:</SRS>
I would like to figure out what I have done to cause this since it causes problems for ESRI's ArcMap.
I took a look at the handleRootSRSAndBbox method in:
http://svn.codehaus.org/geoserver/tags/1.6.2/geoserver/wms/src/main/java/org/vfny/geoserver/wms/responses/helpers/WMSCapsTransformer.java
and saw (and tested) that if your GeoServer has no registered feature types (e.g. you just have coverages registered), then you'll get a common EPSG string of "EPSG:". I'd file a bug.
Looking at the code, you'll also hit this condition if your layer has an empty string SRS, but off hand I am not sure if that is possible.
Cheers,
Ryan
Hi Alan,
From what I can tell it is generated from the "first" feature type encountered... which is not really defined. So I would perhaps look for a layer which does not have an SRS set on it.
Could you include your capabilities document. It might help.
-Justin
Smith, Alan G. wrote:
I would like to know how the the common SRS generated in the WMF GetCapabilities request. I am receiving the following in my response from WMS GetCapabilities request:
<!--common SRS:-->
<SRS>EPSG:</SRS>
I would like to figure out what I have done to cause this since it causes problems for ESRI's ArcMap.Thank you,
Alan!DSPAM:4007,47ea99e1243181804284693!
------------------------------------------------------------------------
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace!DSPAM:4007,47ea99e1243181804284693!
------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users!DSPAM:4007,47ea99e1243181804284693!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin:
Based on Ryan’s response, I submitted a bug:
http://jira.codehaus.org/browse/GEOS-1832
Thank you,
Alan
-----Original Message-----
From: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Sent: Wed 3/26/2008 5:47 PM
To: Smith, Alan G.
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] How is the common SRS generated in the WMS GetCapabilities request?
Hi Alan,
From what I can tell it is generated from the “first” feature type
encountered… which is not really defined. So I would perhaps look for
a layer which does not have an SRS set on it.
Could you include your capabilities document. It might help.
-Justin
Smith, Alan G. wrote:
I would like to know how the the common SRS generated in the WMF
GetCapabilities request. I am receiving the following in my response
from WMS GetCapabilities request:EPSG:
I would like to figure out what I have done to cause this since it
causes problems for ESRI’s ArcMap.Thank you,
Alan!DSPAM:4007,47ea99e1243181804284693!
Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace!DSPAM:4007,47ea99e1243181804284693!
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users!DSPAM:4007,47ea99e1243181804284693!
–
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Hi Alan,
thanks for the bug report, the issue should be solved now.
I've commented on the issue but may be some more explanation is worth:
On the early days, when we didn't support reprojection nor rasters on the WMS,
we tried to figure out if there were a common SRS used by all the available
feature types in order to state it in the capabilities.
The very bug was not taking into account there might be no feature types at
all.
Then reprojection support came in and the list of all supported SRS's was
added, but the "guess common crs" code stayed, even not being needed any
more.
Now things should be better since I cleaned up all that code, even the one to
include the raster layers bbox in the accumulated general bounds, among the
ability to configure a subset of supported crs's to limit the list of 3900+
crs's we can serve in the capabilities.
It'd be nice if you could try that out before we release this Friday, new bugs
may always come in 
Regards,
Gabriel
On Wednesday 26 March 2008 11:19:14 pm Smith, Alan G. wrote:
Justin:
Based on Ryan's response, I submitted a bug:
http://jira.codehaus.org/browse/GEOS-1832Thank you,
Alan-----Original Message-----
From: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Sent: Wed 3/26/2008 5:47 PM
To: Smith, Alan G.
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] How is the common SRS generated in the WMS
GetCapabilities request?Hi Alan,
From what I can tell it is generated from the "first" feature type
encountered... which is not really defined. So I would perhaps look for
a layer which does not have an SRS set on it.Could you include your capabilities document. It might help.
-Justin
Smith, Alan G. wrote:
> I would like to know how the the common SRS generated in the WMF
> GetCapabilities request. I am receiving the following in my response
> from WMS GetCapabilities request:
> <!--common SRS:-->
> <SRS>EPSG:</SRS>
> I would like to figure out what I have done to cause this since it
> causes problems for ESRI's ArcMap.
>
> Thank you,
> Alan
>
>
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpl
>ace
>
> !DSPAM:4007,47ea99e1243181804284693!
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
> !DSPAM:4007,47ea99e1243181804284693!
Gabriel Roldán ha scritto:
It'd be nice if you could try that out before we release this Friday, new bugs may always come in
For those that do not know, the 1.6.x series is built every night out of the current code developers are fixing/improving and placed here:
http://gridlock.openplans.org/geoserver/1.6.x/
Unfortunately it seems the build went bye bye Friday, so there is nothing to try out... have a look in the following days to
see if a nightly starts appearing again and report back your testing
results
Cheers
Andrea
Gabriel:
Now I am receiving “EPSG:WGS84(DD)” instead of “EPSG:”. This causing the same problem as before. It seems that ArcMap is going to have a problem with an “EPSG:” entry that does not include a number. The “WGS84(DD)” text just seems to cause a different problem than the “” text.
Here is the ArcMap request with EPSG:WGS84(DD):
127.0.0.1 - - [31/03/2008:16:26:07 +0000] “GET /geoserver/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&SRS=EPSG:0&BBOX=-20037507.0671618,-14687879.1685618,20037507.0671618,14687879.1685619&WIDTH=735&HEIGHT=538&LAYERS=topp:wvout200803180600&STYLES=&EXCEPTIONS=application/vnd.ogc.se_xml&FORMAT=image/png&BGCOLOR=0xFFFFFF&TRANSPARENT=TRUE HTTP/1.1” 200 439
Here is the ArcMap request without EPSG:WGS84(DD):
127.0.0.1 - - [31/03/2008:16:28:27 +0000] “GET /geoserver/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&SRS=EPSG:4326&BBOX=-180,-90,180,90&WIDTH=809&HEIGHT=404&LAYERS=topp:wvout200803180600&STYLES=&EXCEPTIONS=application/vnd.ogc.se_xml&FORMAT=image/png&BGCOLOR=0xFFFFFF&TRANSPARENT=TRUE HTTP/1.1” 200 248898
Alan
-----Original Message-----
From: Gabriel Roldán [mailto:groldan@anonymised.com…1…]
Sent: Mon 3/31/2008 5:15 AM
To: geoserver-users@lists.sourceforge.net
Cc: Smith, Alan G.; Justin Deoliveira
Subject: Re: [Geoserver-users] How is the common SRS generated in the WMS GetCapabilities request?
Hi Alan,
thanks for the bug report, the issue should be solved now.
I’ve commented on the issue but may be some more explanation is worth:
On the early days, when we didn’t support reprojection nor rasters on the WMS,
we tried to figure out if there were a common SRS used by all the available
feature types in order to state it in the capabilities.
The very bug was not taking into account there might be no feature types at
all.
Then reprojection support came in and the list of all supported SRS’s was
added, but the “guess common crs” code stayed, even not being needed any
more.
Now things should be better since I cleaned up all that code, even the one to
include the raster layers bbox in the accumulated general bounds, among the
ability to configure a subset of supported crs’s to limit the list of 3900+
crs’s we can serve in the capabilities.
It’d be nice if you could try that out before we release this Friday, new bugs
may always come in
Regards,
Gabriel
On Wednesday 26 March 2008 11:19:14 pm Smith, Alan G. wrote:
Justin:
Based on Ryan’s response, I submitted a bug:
http://jira.codehaus.org/browse/GEOS-1832Thank you,
Alan-----Original Message-----
From: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Sent: Wed 3/26/2008 5:47 PM
To: Smith, Alan G.
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] How is the common SRS generated in the WMS
GetCapabilities request?Hi Alan,
From what I can tell it is generated from the “first” feature type
encountered… which is not really defined. So I would perhaps look for
a layer which does not have an SRS set on it.Could you include your capabilities document. It might help.
-Justin
Smith, Alan G. wrote:
I would like to know how the the common SRS generated in the WMF
GetCapabilities request. I am receiving the following in my response
from WMS GetCapabilities request:EPSG:
I would like to figure out what I have done to cause this since it
causes problems for ESRI’s ArcMap.Thank you,
Alan
Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpl
ace!DSPAM:4007,47ea99e1243181804284693!
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users!DSPAM:4007,47ea99e1243181804284693!
Gabriel:
I think I grabbed the wrong version–I didn’t see Andrea’s message on where the latest release is before looking trying to test your fix. I was testing with:
1.7.0-alpha1
I will try the latest 1.6.x when it becomes available.
Alan
-----Original Message-----
From: Gabriel Roldán [mailto:groldan@anonymised.com…1…]
Sent: Mon 3/31/2008 5:15 AM
To: geoserver-users@lists.sourceforge.net
Cc: Smith, Alan G.; Justin Deoliveira
Subject: Re: [Geoserver-users] How is the common SRS generated in the WMS GetCapabilities request?
Hi Alan,
thanks for the bug report, the issue should be solved now.
I’ve commented on the issue but may be some more explanation is worth:
On the early days, when we didn’t support reprojection nor rasters on the WMS,
we tried to figure out if there were a common SRS used by all the available
feature types in order to state it in the capabilities.
The very bug was not taking into account there might be no feature types at
all.
Then reprojection support came in and the list of all supported SRS’s was
added, but the “guess common crs” code stayed, even not being needed any
more.
Now things should be better since I cleaned up all that code, even the one to
include the raster layers bbox in the accumulated general bounds, among the
ability to configure a subset of supported crs’s to limit the list of 3900+
crs’s we can serve in the capabilities.
It’d be nice if you could try that out before we release this Friday, new bugs
may always come in
Regards,
Gabriel
On Wednesday 26 March 2008 11:19:14 pm Smith, Alan G. wrote:
Justin:
Based on Ryan’s response, I submitted a bug:
http://jira.codehaus.org/browse/GEOS-1832Thank you,
Alan-----Original Message-----
From: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Sent: Wed 3/26/2008 5:47 PM
To: Smith, Alan G.
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] How is the common SRS generated in the WMS
GetCapabilities request?Hi Alan,
From what I can tell it is generated from the “first” feature type
encountered… which is not really defined. So I would perhaps look for
a layer which does not have an SRS set on it.Could you include your capabilities document. It might help.
-Justin
Smith, Alan G. wrote:
I would like to know how the the common SRS generated in the WMF
GetCapabilities request. I am receiving the following in my response
from WMS GetCapabilities request:EPSG:
I would like to figure out what I have done to cause this since it
causes problems for ESRI’s ArcMap.Thank you,
Alan
Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpl
ace!DSPAM:4007,47ea99e1243181804284693!
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users!DSPAM:4007,47ea99e1243181804284693!
Hi Alan,
yeah, unfortunately you'll have to wait until a 1.6.x nightly is available.
The last one at <http://gridlock.openplans.org/geoserver/1.6.x/> is from last
Thursday and the fix were commited on Friday.
Hope this is solved asap.
Does anyone knows why a nightly could not be done? jdeolive?
Besides that, I wonder if "EPSG:WGS84(DD)" is a valid epsg code or rather why
we get "WGS84(DD)" out of CRS.getSupportedCodes("EPSG")?
Cheers,
Gabriel
On Monday 31 March 2008 06:31:59 pm Smith, Alan G. wrote:
Gabriel:
I think I grabbed the wrong version--I didn't see Andrea's message on where
the latest release is before looking trying to test your fix. I was
testing with: 1.7.0-alpha1
I will try the latest 1.6.x when it becomes available.Alan
-----Original Message-----
From: Gabriel Roldán [mailto:groldan@anonymised.com]
Sent: Mon 3/31/2008 5:15 AM
To: geoserver-users@lists.sourceforge.net
Cc: Smith, Alan G.; Justin Deoliveira
Subject: Re: [Geoserver-users] How is the common SRS generated in the WMS
GetCapabilities request?Hi Alan,
thanks for the bug report, the issue should be solved now.
I've commented on the issue but may be some more explanation is worth:
On the early days, when we didn't support reprojection nor rasters on the
WMS, we tried to figure out if there were a common SRS used by all the
available feature types in order to state it in the capabilities.
The very bug was not taking into account there might be no feature types at
all.
Then reprojection support came in and the list of all supported SRS's was
added, but the "guess common crs" code stayed, even not being needed any
more.
Now things should be better since I cleaned up all that code, even the one
to include the raster layers bbox in the accumulated general bounds, among
the ability to configure a subset of supported crs's to limit the list of
3900+ crs's we can serve in the capabilities.It'd be nice if you could try that out before we release this Friday, new
bugs may always come inRegards,
Gabriel
On Wednesday 26 March 2008 11:19:14 pm Smith, Alan G. wrote:
> Justin:
>
> Based on Ryan's response, I submitted a bug:
> http://jira.codehaus.org/browse/GEOS-1832
>
> Thank you,
> Alan
>
> -----Original Message-----
> From: Justin Deoliveira [mailto:jdeolive@anonymised.com]
> Sent: Wed 3/26/2008 5:47 PM
> To: Smith, Alan G.
> Cc: geoserver-users@lists.sourceforge.net
> Subject: Re: [Geoserver-users] How is the common SRS generated in the WMS
> GetCapabilities request?
>
> Hi Alan,
>
> From what I can tell it is generated from the "first" feature type
> encountered... which is not really defined. So I would perhaps look for
> a layer which does not have an SRS set on it.
>
> Could you include your capabilities document. It might help.
>
> -Justin
>
> Smith, Alan G. wrote:
> > I would like to know how the the common SRS generated in the WMF
> > GetCapabilities request. I am receiving the following in my response
> > from WMS GetCapabilities request:
> > <!--common SRS:-->
> > <SRS>EPSG:</SRS>
> > I would like to figure out what I have done to cause this since it
> > causes problems for ESRI's ArcMap.
> >
> > Thank you,
> > Alan
> >
> >
> >
> >
> > -----------------------------------------------------------------------
> >-
> >
> > -----------------------------------------------------------------------
> >-- Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/market
> >pl ace
> >
> >
> >
> >
> > -----------------------------------------------------------------------
> >-
> >
> > _______________________________________________
> > Geoserver-users mailing list
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
> >
> > !DSPAM:4007,47ea99e1243181804284693!!DSPAM:4045,47f112ab231812085621377!