<br><font size=2 face="sans-serif">I probably do it the hard way. The
USDA flies summer color imagery in North Carolina every couple of years
for crop verification. They will put draft versions of the imagery
up in single image per county mosaics in MrSid format for download about
6-8 months before they make the final quarter quadragle geotiffs available.
The single county mosaics are in UTM projection. In NC, we
like utm zones so much, we have three of them. Since I prefer to
work with a seamless image layer in the same projection (North Carolina
State Plane) and quarter quad format, I:</font>
<br>
<br><font size=2 face="sans-serif">1) Use nearblack on the county MrSid
images and output to Imagine format.</font>
<br><font size=2 face="sans-serif">2) Reproject the county Imagine images
to NC State Plane projection</font>
<br><font size=2 face="sans-serif">3) use gdaltindex to create a shapefile
index (1) from an older statewide image layer with image overlap in North
Carolina State Plane projection.</font>
<br><font size=2 face="sans-serif">4) use gdaltindex to make a shapefile
index (2) of the reprojected county Imagine format image files.</font>
<br><font size=2 face="sans-serif">4) Run a python script which grabs the
corner coordinates of each polygon from shapefile index 1 and use
that to create a list of Imagine images that overlap with the polygon
by comparing it to index 2. This script then recursively "cookie
cuts" the section of each Imagine image that falls within the polygon
and creates a tiff file , using gdaltranslate. After all of the "cookie
cutting" has been done, the script merges all of the tiff files into
one tiff file using gdalwarp.</font>
<br>
<br><font size=2 face="sans-serif">For most of this, I cheat by using python
to pass os.system commands to use the utility binaries. </font>
<br>
<br><font size=2 face="sans-serif">I made up a powerpoint presentation
on this a couple of years ago at an internal national meeting, is there
a suitable wiki to upload it to ( after getting release permission
and conversion to Openoffice impress format)?</font>
<br>
<br><font size=2 face="sans-serif">Doug</font>
<br><font size=2 face="sans-serif"> </font>
<br>
<br>
<br><font size=2 face="sans-serif">Doug Newcomb
<br>
USFWS<br>
Raleigh, NC<br>
919-856-4520 ext. 14 doug_newcomb@fws.gov<br>
---------------------------------------------------------------------------------------------------------<br>
The opinions I express are my own and are not representative of the official
policy of the U.S.Fish and Wildlife Service or Dept. of the Interior.
Life is too short for undocumented, proprietary data formats.</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Hermann Peifer <peifer@gmx.eu></b>
</font>
<br><font size=1 face="sans-serif">Sent by: gdal-dev-bounces@lists.osgeo.org</font>
<p><font size=1 face="sans-serif">10/01/2010 09:21 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Jukka Rahkonen <jukka.rahkonen@mmmtike.fi></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">gdal-dev@lists.osgeo.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[gdal-dev] Re: gdal_rasterize -tr and
-te</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>On 01/10/2010 07:03, Jukka Rahkonen wrote:<br>
> Hermann Peifer<peifer<at> gmx.eu> writes:<br>
><br>
><br>
>> At work, we are taking this "standard grid" issue pretty
serious, but<br>
>> indeed, we might be the only ones worldwide with such a business
rule.<br>
><br>
> You are not alone, we are reprojecting our rasters to standard grid
because it<br>
> helps in making seamless mosaics from the reprojected images. We are
widening<br>
> the target extents a little bit to all directions with a python script
to suit<br>
> the grid.<br>
><br>
<br>
So we are already 2 ;-)<br>
<br>
Actually, I tentatively thought there would be more. This was why I <br>
wrote to the mailing list in the first place. I am aware that this <br>
(non-)issue can be solved in a shell one-liner or perhaps X lines of <br>
some other script code. I just thought that if there is a general <br>
interest, it could perhaps be built into the library.<br>
<br>
Hermann<br>
_______________________________________________<br>
gdal-dev mailing list<br>
gdal-dev@lists.osgeo.org<br>
</font></tt><a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev"><tt><font size=2>http://lists.osgeo.org/mailman/listinfo/gdal-dev<br>
</font></tt></a>
<br>