When I added reprojection to geoserver, people were still used to the
old behavior which was to never reproject. Making the SRS parameter
manditory would break most of the current users.
So, if you dont specify a CRS in your GetMap then it will does the same
as SRS=NONE. This means that there's no reprojection done. This also
means that you better have made the request bbox in the same projection
as your data or you'll probably get a blank map.
If you have a layer where you do not specify a SRS (in the FeatureType
editor) then geotools assumes that its projection is the same as the
request projection. Obviously geotools cannot arbitrarily transform
from an unknown SRS to a known SRS.
Both these assumptions save most people from shooting themselves in the
foot, but its not without its consequences.
I dont really care if we make it manditory or not, but we will almost
certainly get people complaining about it if we change it. We could
add a WMS config option for it though (and have it default - at least
for a while - to 'no SRS in request means SRS=NONE').
People who dont put the SRS in the request are likely:
a) wanting the SRS=NONE behavior (request projection=data projection)
b) actually wanted WSG84 lat-long (4326) with the axis hopefully
correctly aligned.
c) made a boo-boo in the request
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
Folks,
I think this is the wrong behaviour for a server. Either the client knows
what it wants or the server throws a ServiceException.
Adding smarts to the server to try to figure out what the client wants is
just going to complicate the server code un-necessarily.
SRS is a REQUEST parameter and the WMS 1.1.1 Implementation Specification
clearly states that is Required.
v/r,
Efren
-----Original Message-----
From: geoserver-devel-admin@lists.sourceforge.net
[mailto:geoserver-devel-admin@lists.sourceforge.net]On Behalf Of
dblasby@anonymised.com
Sent: Wednesday, November 30, 2005 6:26 AM
Cc: geoserver-devel@lists.sourceforge.net
Subject: [Geoserver-devel] Re: about SRS parameter
When I added reprojection to geoserver, people were still used to the
old behavior which was to never reproject. Making the SRS parameter
manditory would break most of the current users.
So, if you dont specify a CRS in your GetMap then it will does the same
as SRS=NONE. This means that there's no reprojection done. This also
means that you better have made the request bbox in the same projection
as your data or you'll probably get a blank map.
If you have a layer where you do not specify a SRS (in the FeatureType
editor) then geotools assumes that its projection is the same as the
request projection. Obviously geotools cannot arbitrarily transform
from an unknown SRS to a known SRS.
Both these assumptions save most people from shooting themselves in the
foot, but its not without its consequences.
I dont really care if we make it manditory or not, but we will almost
certainly get people complaining about it if we change it. We could
add a WMS config option for it though (and have it default - at least
for a while - to 'no SRS in request means SRS=NONE').
People who dont put the SRS in the request are likely:
a) wanting the SRS=NONE behavior (request projection=data projection)
b) actually wanted WSG84 lat-long (4326) with the axis hopefully
correctly aligned.
c) made a boo-boo in the request
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel