[Mapserver-users] Projection AUTO, GDAL and ECW files

Brent Fraser bfraser at geoanalytic.com
Mon May 12 15:49:43 EDT 2003


This is a multi-part message in MIME format.

------=_NextPart_000_00CA_01C3188D.57D4E010
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Frank (and others),

  I'm doing some investigation into making the TILEINDEX feature a =
little more flexible with respect to coordinate systems.  I like the =
PROJECTION AUTO feature added to MapServer 3.7 for datastores, but not =
all of them store coordinate system information with the data (e.g. =
shapefiles, jpg), and some of them have their own "proprietary" method =
of specifying it (e.g. ECW) not handled by GDAL.  This means that =
integrating new datasets requires Mapserver implementors to carefully =
define the coordinate system in each map file.

  What do you think about having GDAL read an additional file that =
specifies the coordinate system definition for a specific data file?  =
The file could/should have the same filename prefix as the datafile with =
an extension of prj, csd or something that hasn't been used for similar =
things.  The format could be PROJ strings (or EPSG numbers, or OGIS WKT =
format).

  Good idea? Bad idea? Already been done? No interest?

Thanks!
Brent Fraser
GeoAnalytic Inc.
Tel:(403) 213-2700
bfraser at geoanalytic.com
www.geoanalytic.com

------=_NextPart_000_00CA_01C3188D.57D4E010
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Frank (and others),</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; I'm doing some investigation =
into making the=20
TILEINDEX feature a little more flexible with respect to coordinate=20
systems.&nbsp; I like the PROJECTION AUTO feature added to MapServer 3.7 =
for=20
datastores, but not all of them store coordinate system information with =
the=20
data (e.g. shapefiles, jpg), and some of them have their own =
"proprietary"=20
method of&nbsp;specifying it (e.g. ECW) not handled by GDAL.&nbsp; This =
means=20
that integrating new datasets requires Mapserver implementors to =
carefully=20
define the coordinate system in each map file.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; What do you think about having =
GDAL read an=20
additional file that specifies the coordinate system definition for a =
specific=20
data file?&nbsp; The file could/should have the same filename prefix as =
the=20
datafile with an extension of prj, csd or </FONT><FONT face=3DArial=20
size=3D2>something that hasn't been used for similar things.&nbsp; The =
format=20
could be PROJ strings (or EPSG numbers, or OGIS WKT =
format).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; Good idea? Bad =
idea?&nbsp;Already been done?=20
No interest?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Brent Fraser</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>GeoAnalytic Inc.<BR>Tel:(403) =
213-2700<BR><A=20
href=3D"mailto:bfraser at geoanalytic.com">bfraser at geoanalytic.com</A><BR><A=
=20
href=3D"http://www.geoanalytic.com">www.geoanalytic.com</A></FONT></DIV><=
/BODY></HTML>

------=_NextPart_000_00CA_01C3188D.57D4E010--




More information about the mapserver-users mailing list