[Geoserver-devel] about SRS parameter

GeoServer GeoServer Developer
1

Hi all,

I just created
http://jira.codehaus.org/browse/GEOS-493

the question is if you're ok in making SRS parameter mandatory (that's what
the spec says).

Cheers,

Gabriel.

2

I guess my only concern is that making the SRS parameter manditory breaks client code that doesn't presently supply the paramter. Making things optional is much easier then making things mandatory.

On the other hand the spec saying it should be manditory is big hammer to throw around.

What does everyone else think.

-Justin

Gabriel Roldán wrote:

Hi all,

I just created http://jira.codehaus.org/browse/GEOS-493

the question is if you're ok in making SRS parameter mandatory (that's what the spec says).

Cheers,

Gabriel.

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

3

If we do make this manditory, do we want it for 1.3.0?

We can always make it pseudo optional. If the SRS is supplie din the request, we use it. If it is not supplied, we add in 4326 as a default. This will stop client code from breaking. This could result in unexpected results however.

I think we need to look at how long it would take to change, and how many other things it will break, in order to determine when we should implement it.

Brent Owens
TOPP

Justin Deoliveira wrote:

I guess my only concern is that making the SRS parameter manditory breaks client code that doesn't presently supply the paramter. Making things optional is much easier then making things mandatory.

On the other hand the spec saying it should be manditory is big hammer to throw around.

What does everyone else think.

-Justin

Gabriel Roldán wrote:

Hi all,

I just created http://jira.codehaus.org/browse/GEOS-493

the question is if you're ok in making SRS parameter mandatory (that's what the spec says).

Cheers,

Gabriel.

4

Justin,

The interaction should be:

1. client issues GetCapabilities; upon receival of the
   Capabilities document, it obtains the SRSs supported by the server.
2. client interacts with the server or gives up.
3. SRS=NONE is allowed in Capabilities document.

Note that SRS is part of the GetMap request not the response.

v/r,
Efren

-----Original Message-----
From: geoserver-devel-admin@lists.sourceforge.net
[mailto:geoserver-devel-admin@lists.sourceforge.net]On Behalf Of Justin
Deoliveira
Sent: Tuesday, November 29, 2005 9:36 AM
To: Gabriel Roldán
Cc: David Blasby; Brent Owens; geoserver-devel@lists.sourceforge.net
Subject: [Geoserver-devel] Re: about SRS parameter

I guess my only concern is that making the SRS parameter manditory
breaks client code that doesn't presently supply the paramter. Making
things optional is much easier then making things mandatory.

On the other hand the spec saying it should be manditory is big hammer
to throw around.

What does everyone else think.

-Justin

Gabriel Roldán wrote:

Hi all,

I just created
http://jira.codehaus.org/browse/GEOS-493

the question is if you're ok in making SRS parameter mandatory (that's what
the spec says).

Cheers,

Gabriel.

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

-------------------------------------------------------
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

5

Agreed, we can schedule it for after 1.3.0.

Anyway, note the current behavior is to let it null, not to use 4326, so I'm
letting it as is, which finally means querying in whatever the feature source
is in.
Problem is when more than one FS is being queries at the same time, though.

comments?

On Tuesday 29 November 2005 18:48, Brent Owens wrote:

If we do make this manditory, do we want it for 1.3.0?

We can always make it pseudo optional. If the SRS is supplie din the
request, we use it. If it is not supplied, we add in 4326 as a default.
This will stop client code from breaking. This could result in
unexpected results however.

I think we need to look at how long it would take to change, and how
many other things it will break, in order to determine when we should
implement it.

Brent Owens
TOPP

Justin Deoliveira wrote:
> I guess my only concern is that making the SRS parameter manditory
> breaks client code that doesn't presently supply the paramter. Making
> things optional is much easier then making things mandatory.
>
> On the other hand the spec saying it should be manditory is big hammer
> to throw around.
>
> What does everyone else think.
>
> -Justin
>
> Gabriel Roldán wrote:
>> Hi all,
>>
>> I just created http://jira.codehaus.org/browse/GEOS-493
>>
>> the question is if you're ok in making SRS parameter mandatory
>> (that's what the spec says).
>>
>> Cheers,
>>
>> Gabriel.

-------------------------------------------------------
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