<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>RE: [UMN_MAPSERVER-USERS] Mapserver response</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<BR>
<BR>
<P><FONT SIZE=2>-----Original Message-----<BR>
From: Frank Warmerdam [<A HREF="mailto:fwarmerdam@gmail.com">mailto:fwarmerdam@gmail.com</A>]<BR>
Sent: Fri 5/13/2005 3:07 PM<BR>
To: Norman Barker<BR>
Cc: MAPSERVER-USERS@lists.umn.edu<BR>
Subject: Re: [UMN_MAPSERVER-USERS] Mapserver response<BR>
<BR>
On 5/13/05, Norman Barker <nbarker@rsinc.com> wrote:<BR>
> Thanks Frank,<BR>
><BR>
> I was trying to find a way to force a file through MapServer WCS because of bug 1183, it works with some<BR>
> files (with square resolution), but not others hence the question.<BR>
><BR>
> Would there be a way to specify a 'RAW' extension to MapServer WCS to retrieve the base file unaltered? I am thinking in particular of retrieving data with custom geotiff tags, or say a Jpeg2000 file with custom XML inside it?<BR>
<BR>
Norman,<BR>
<BR>
I don't forsee supporting a raw mode which literally returns the original<BR>
file since it is quite out-of-band for mapserver. However, I have been<BR>
thinking that for WCS mode it would be nice if we could have some way<BR>
of returning various kinds of metadata associated with the source file<BR>
when serving via WCS. This would likely only make sense for<BR>
layers that are not tileindexed. Perhaps a PROCESSING directive<BR>
on the layer that would indicate what sorts of metadata to carry over<BR>
to the result file. <BR>
<BR>
Of course, it would at best likely be constrained by the metadata<BR>
model of GDAL. <BR>
<BR>
I have no concrete plans to add such a feature but I think it is worth<BR>
further discussion about the sorts of things we would want to carry over.<BR>
<BR>
> Any thing we can do to help with the WCS resolution/reprojection bug please let us know.<BR>
<BR>
I dug into and closed the bug yesterday. Perhaps it was using an<BR>
old email address for you, so you didn't get the notification? The<BR>
overall result was that you were missing a PROJECTION block<BR>
on your raster layer, so anything going through the warp/resampler<BR>
was just not acting.<BR>
<BR>
Hi Frank,<BR>
<BR>
A Processing directive would be a really cool idea! I can see that we could preserve metadata in JPEG2000<BR>
that way, and also allow custom tags. Could it be opened up to include hooks to image processing as well?<BR>
Then you would have remote subsetting and processing in one (or perhaps I am getting carried away!! :-))<BR>
<BR>
Many thanks for closing the bug, I have moved jobs to RSI hence the change in email. I am using the FWTools version of MapServer but I will take the nightly source and build it asap.<BR>
<BR>
Many thanks,<BR>
<BR>
Norman Barker<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>