[Mapserver-users] Integrating MapServ with Another Existing map server.

[Ed McNierney]

Omry -

The Open GIS Consortium's WMS interface is very easy to use.  I would
recommend modifying your client software so it can read raster data from
a WMS server; that way you can read your "RMS" data and you'll also be
able to read from other raster systems in the future.

As far as raster performance goes, it sounds like your system only
produces maps at the client in one projection.  Whatever that projection
is, you should simply reproject all your raster data in advance and do
it once - then you don't even have to think about reprojection
performance, because you won't be doing it.

I do not think "lat/lon" is a very good projection in general, but it is
particularly unattractive when using raster data.  The spatial
distortion is pretty bad except at the equator (you can't even put an
accurate scale bar on it, unless the units are degrees) and that tends
to produce visible distortions in imagery.

	- Ed

Ed McNierney
President and Chief Mapmaker
TopoZone.com
ed at topozone.com


-----Original Message-----
From: Omry Yadan [mailto:omry at telmap.com] 
Sent: Wednesday, October 15, 2003 5:00 AM
To: mapserver-users at lists.gis.umn.edu
Subject: [Mapserver-users] Integrating MapServ with Another Existing map
server.

Here is the scenario of my problem:
First two definitions: 
1. TMS - Telmap map server, a proprietary map server developed by the
company I work for.

2. RMS - Raster map server, the map server CGI you all know, (I know it
can 
do vectors too, but I only care about the raster for now).

TMS sends vector data in a proprietary format and in a proprietary
projection to a java map client that renders it.
I need to integrate raster data from RMS into this system - more
specifically, I want to combine data from TMS with raster data from RMS,
and
to render the vector data over the raster data in the client.

My current problem is the coordinate system and units in which to
request
the raster map.
My client understands LatLong, and the proprietary projection (and can
convert from one to the other), and RMS understands LatLong and many
other
projections my client currently does not.
So one clear solution will be to use LatLong as the common coordinate
system. (Have the client request maps using LatLong bounding box - does
it
even make sense?).
Another option I see is to teach my client to convert to the projection
used
in the specific project I am working on, but it's a solution I don't
like,
because it means more development whenever I get raster data which is in
a
different coordinate system.

I would appreciate any suggestions / Insight about this issues.

Thanks.
_______________________________________________
Mapserver-users mailing list
Mapserver-users at lists.gis.umn.edu
http://lists.gis.umn.edu/mailman/listinfo/mapserver-users