Multi-projection support

Description

Wish list item:

I'd like to see GeoServer be able to publish a WFS layer in multiple projections or SRSes without duplicating the data. I realize that under the WFS spec, only one SRS can be specified for a layer, but if GeoServer could project requests and responses on the fly, perhaps I could set up multiple featureTypes that use the same source data by specifying layers with different SRS element contents for each one in the info.xml file.

Environment

None

Activity

Show:
codehaus
April 10, 2015, 4:35 PM

CodeHaus Comment From: cholmes - Time: Wed, 19 Nov 2003 17:35:03 -0600
---------------------
<p>I'd also like to see something like this eventually. Just now geotools is grappling with getting SRS's through the whole data flow model. Right now geoserver just kind of hacks things on at the end, assuming that the user sets up everything correctly. We're adding reprojection to geotools datastores, and once it's in place DataStores should be able to handle it internally if they have the capabilities, and geotools should handle the reprojection if they don't. It'll probably take a few months to get those changes all the way rolled out to geoserver, but once they in we can experiment with how we want to deal with reprojections. Setting up layers that automatically reproject by default is one idea. </p>

<p>I feel like the spec also may leave a few holes for you to request features in different projections. For example if you ask for a filter with a geometry then that geometry will have an srs. As far as I can tell the spec doesn't seem to say what you should do if the srs of the bbox asked for is not the same as the featureType. Raise an exception? Project the box into the FeatureType's srs? Or project the features into the boxes srs? Maybe I'm missing something, but I think it might be good to ask the spec for clarification, and possibly a new wfs spec version might have better information about spatial reference systems, requesting the feature service to translate them. </p>

<p>The other idea is a Web Coordinate Transformation Service, which is currently an opengis discussion paper, that might be able to handle the transformation. It might be a bit heavy-weight, but it could be cool if geoserver offered it, and also just integrated it into the service chain, allowing some easy way to specify transformed data. I haven't looked too closely at the spec though, it might not be appropriate.</p>

codehaus
April 10, 2015, 4:35 PM

CodeHaus Comment From: cholmes - Time: Thu, 28 Oct 2004 12:08:12 -0500
---------------------
<p>Moved to 1.3, and upgraded to critical, I believe this is one of the essential improvements needed, should do it for WMS (as it's required by the spec), and for WFS (next spec should give us how to do it).</p>

codehaus
April 10, 2015, 4:35 PM

CodeHaus Comment From: cholmes - Time: Thu, 14 Feb 2008 14:01:25 -0600
---------------------
<p>This is now done, since we've got it in WMS and WFS 1.1</p>

Assignee

Unassigned

Reporter

codehaus

Triage

None

Fix versions

None

Affects versions

Components

Priority

High
Configure