[mapserver-users] One table with multiple GeometryColumns

[Thomas Bonfort]

AFAIK, creating 3 distinct layers is currently the only solution
available, which has the inconvenience that the client must explicitely
request the correct layer in order to avoid the overhead of reprojection.
You can use INCLUDEs inside those layers in order to avoid duplicating
the rest of the LAYER configuration (i.e. for everything except NAME,
DATA, PROJECTION).
The mechanism used for
http://mapserver.org/fr/development/rfc/ms-rfc-86.html SCALETOKENs could
probably be extended to include other runtime-replaceable tokens
(notably projection id), but there would still be issues in that case as
to how mapserver itself should be instructed whether to reproject the
data or not.

--
thomas

On 27/01/2014 11:28, Jiří Kadlec wrote:
> Dear mapserver forum,
> 
> In my PostGIS database I have a table 'lakes' with 3 geometry columns:
> the_geom4326, the_geom3857, the_geom3067
> My goal is to make my 'lakes' layer available in the 3 different
> projections: (EPSG:4326, EPSG:3857, EPSG:3067)
> 
> Is this possible in MapServer?
> 
> (then only way I managed so far is to serve the table as 3 different
> layers, first layer in EPSG:4326, second layer in EPSG:3857, third layer in
> EPSG:3067)
> 
> 
> Thanks a lot for help,
> 
> 
> 
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>