<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
so could you stop set messenge to me .<BR>
thank again, Tahnk you for coopration and all information <BR> <BR>> From: gdal-dev-request@lists.osgeo.org<BR>> Subject: gdal-dev Digest, Vol 63, Issue 23<BR>> To: gdal-dev@lists.osgeo.org<BR>> Date: Mon, 10 Aug 2009 12:00:21 -0400<BR>> <BR>> Send gdal-dev mailing list submissions to<BR>> gdal-dev@lists.osgeo.org<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> http://lists.osgeo.org/mailman/listinfo/gdal-dev<BR>> or, via email, send a message with subject or body 'help' to<BR>> gdal-dev-request@lists.osgeo.org<BR>> <BR>> You can reach the person managing the list at<BR>> gdal-dev-owner@lists.osgeo.org<BR>> <BR>> When replying, please edit your Subject line so it is more specific<BR>> than "Re: Contents of gdal-dev digest..."<BR>> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. reprojection HDF / GCP extraction (Becker, Thomas)<BR>> 2. Re: reprojection HDF / GCP extraction ( Lucena, Ivan )<BR>> 3. RE: reprojection HDF / GCP extraction (Becker, Thomas)<BR>> 4. RE: reprojection HDF / GCP extraction ( Lucena, Ivan )<BR>> 5. Re: Motion: Adopt GDAL 1.6.2RC2 as final release<BR>> (Daniel Morissette)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Mon, 10 Aug 2009 14:00:50 +0200<BR>> From: "Becker, Thomas" <thob@dmu.dk><BR>> Subject: [gdal-dev] reprojection HDF / GCP extraction<BR>> To: "gdal-dev@lists.osgeo.org" <gdal-dev@lists.osgeo.org><BR>> Message-ID:<BR>> <D4AB8C2051A3D1449495F8E45815E6000B2ADCF42E@dmupost.dmu.dk><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> Hi all,<BR>> <BR>> I have a couple NOAA-15 images as HDF-EOS files which I would like to reproject to WGS84. The data carry a subgroup called 'Geolocation Fields' holding latitude and longitude for each pixel in separated arrays. Reading the files with gdalinfo leads to the output at the end of this posting.<BR>> <BR>> Out of the HDF-EOS format I would like to create a correct georeferenced image (GTIF). One which will not look like a swath scanned image, but a skewed and correctly referenced one.<BR>> <BR>> Using gdalwarp leads to the message: There is no affine transformation and no GCPs.<BR>> <BR>> Since the coordinates for the centre of each pixel are stored in the before mentioned arrays, is there a way to extract GCPs out of the data.<BR>> <BR>> Thanks for your help.<BR>> <BR>> Best regards,<BR>> Thomas<BR>> <BR>> gdalinfo output:<BR>> <BR>> Driver: HDF4/Hierarchical Data Format Release 4<BR>> Files: amsua15_2000.034_08964_0104_0258_GC.eos<BR>> Size is 512, 512<BR>> Coordinate System is `'<BR>> Metadata:<BR>> HDFEOSVersion=HDFEOS_V2.4<BR>> Subdatasets:<BR>> SUBDATASET_1_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:23800.37 MHz<BR>> SUBDATASET_1_DESC=[851x30] 23800.37 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_2_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:31400.42 MHz<BR>> SUBDATASET_2_DESC=[851x30] 31400.42 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_3_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:50299.91 MHz<BR>> SUBDATASET_3_DESC=[851x30] 50299.91 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_4_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:52799.39 MHz<BR>> SUBDATASET_4_DESC=[851x30] 52799.39 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_5_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:53595.41 +- 115 MHz<BR>> SUBDATASET_5_DESC=[851x30] 53595.41 +- 115 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_6_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:54399.53 MHz<BR>> SUBDATASET_6_DESC=[851x30] 54399.53 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_7_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:54940.64 MHz<BR>> SUBDATASET_7_DESC=[851x30] 54940.64 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_8_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:55498.70 MHz<BR>> SUBDATASET_8_DESC=[851x30] 55498.70 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_9_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 MHz<BR>> SUBDATASET_9_DESC=[851x30] 57290.33 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_10_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 217 MHz<BR>> SUBDATASET_10_DESC=[851x30] 57290.33 +- 217 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_11_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 322.2 +- 48 MHz<BR>> SUBDATASET_11_DESC=[851x30] 57290.33 +- 322.2 +- 48 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_12_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 322.2 +- 22 MHz<BR>> SUBDATASET_12_DESC=[851x30] 57290.33 +- 322.2 +- 22 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_13_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 322.2 +- 10 MHz<BR>> SUBDATASET_13_DESC=[851x30] 57290.33 +- 322.2 +- 10 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_14_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 322.2 +- 4.5 MHz<BR>> SUBDATASET_14_DESC=[851x30] 57290.33 +- 322.2 +- 4.5 MHz Orbit 8964 (32-bit floating-point)<BR>> SUBDATASET_15_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:88997.00 MHz<BR>> SUBDATASET_15_DESC=[851x30] 88997.00 MHz Orbit 8964 (32-bit floating-point)<BR>> Corner Coordinates:<BR>> Upper Left ( 0.0, 0.0)<BR>> Lower Left ( 0.0, 512.0)<BR>> Upper Right ( 512.0, 0.0)<BR>> Lower Right ( 512.0, 512.0)<BR>> Center ( 256.0, 256.0)<BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 2<BR>> Date: Mon, 10 Aug 2009 07:14:39 -0500<BR>> From: " Lucena, Ivan " <ivan.lucena@pmldnet.com><BR>> Subject: Re: [gdal-dev] reprojection HDF / GCP extraction<BR>> To: "Becker, Thomas" <thob@dmu.dk>, "gdal-dev@lists.osgeo.org"<BR>> <gdal-dev@lists.osgeo.org><BR>> Message-ID: <20090810121439.27899.qmail@s466.sureserver.com><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> Becker,<BR>> <BR>> Please take a look at RFC#4: http://trac.osgeo.org/gdal/wiki/rfc4_geolocate<BR>> <BR>> Regards,<BR>> <BR>> Ivan<BR>> <BR>> <BR>> > -------Original Message-------<BR>> > From: Becker, Thomas <thob@dmu.dk><BR>> > Subject: [gdal-dev] reprojection HDF / GCP extraction<BR>> > Sent: Aug 10 '09 07:00<BR>> > <BR>> > Hi all,<BR>> > <BR>> > I have a couple NOAA-15 images as HDF-EOS files which I would like to reproject to WGS84. The data carry a <BR>> subgroup called 'Geolocation Fields' holding latitude and longitude for each pixel in separated arrays. Reading the files <BR>> with gdalinfo leads to the output at the end of this posting.<BR>> > <BR>> > Out of the HDF-EOS format I would like to create a correct georeferenced image (GTIF). One which will not look <BR>> like a swath scanned image, but a skewed and correctly referenced one.<BR>> > <BR>> > Using gdalwarp leads to the message: There is no affine transformation and no GCPs.<BR>> > <BR>> > Since the coordinates for the centre of each pixel are stored in the before mentioned arrays, is there a way to <BR>> extract GCPs out of the data.<BR>> > <BR>> > Thanks for your help.<BR>> > <BR>> > Best regards,<BR>> > Thomas<BR>> > <BR>> > gdalinfo output:<BR>> > <BR>> > Driver: HDF4/Hierarchical Data Format Release 4<BR>> > Files: amsua15_2000.034_08964_0104_0258_GC.eos<BR>> > Size is 512, 512<BR>> > Coordinate System is `'<BR>> > Metadata:<BR>> > HDFEOSVersion=HDFEOS_V2.4<BR>> > Subdatasets:<BR>> > SUBDATASET_1_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:23800.37 MHz<BR>> > SUBDATASET_1_DESC=[851x30] 23800.37 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_2_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:31400.42 MHz<BR>> > SUBDATASET_2_DESC=[851x30] 31400.42 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_3_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:50299.91 MHz<BR>> > SUBDATASET_3_DESC=[851x30] 50299.91 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_4_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:52799.39 MHz<BR>> > SUBDATASET_4_DESC=[851x30] 52799.39 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_5_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:53595.41 +- 115 MHz<BR>> > SUBDATASET_5_DESC=[851x30] 53595.41 +- 115 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_6_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:54399.53 MHz<BR>> > SUBDATASET_6_DESC=[851x30] 54399.53 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_7_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:54940.64 MHz<BR>> > SUBDATASET_7_DESC=[851x30] 54940.64 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_8_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:55498.70 MHz<BR>> > SUBDATASET_8_DESC=[851x30] 55498.70 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_9_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:57290.33 MHz<BR>> > SUBDATASET_9_DESC=[851x30] 57290.33 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_10_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:57290.33 +- 217 MHz<BR>> > SUBDATASET_10_DESC=[851x30] 57290.33 +- 217 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_11_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:57290.33 +- 322.2 +- 48 MHz<BR>> > SUBDATASET_11_DESC=[851x30] 57290.33 +- 322.2 +- 48 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_12_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:57290.33 +- 322.2 +- 22 MHz<BR>> > SUBDATASET_12_DESC=[851x30] 57290.33 +- 322.2 +- 22 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_13_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:57290.33 +- 322.2 +- 10 MHz<BR>> > SUBDATASET_13_DESC=[851x30] 57290.33 +- 322.2 +- 10 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_14_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:57290.33 +- 322.2 +- 4.5 MHz<BR>> > SUBDATASET_14_DESC=[851x30] 57290.33 +- 322.2 +- 4.5 MHz Orbit 8964 (32-bit floating-point)<BR>> > SUBDATASET_15_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit <BR>> 8964:88997.00 MHz<BR>> > SUBDATASET_15_DESC=[851x30] 88997.00 MHz Orbit 8964 (32-bit floating-point)<BR>> > Corner Coordinates:<BR>> > Upper Left ( 0.0, 0.0)<BR>> > Lower Left ( 0.0, 512.0)<BR>> > Upper Right ( 512.0, 0.0)<BR>> > Lower Right ( 512.0, 512.0)<BR>> > Center ( 256.0, 256.0)<BR>> > _______________________________________________<BR>> > gdal-dev mailing list<BR>> > gdal-dev@lists.osgeo.org<BR>> > http://lists.osgeo.org/mailman/listinfo/gdal-dev<BR>> > <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 3<BR>> Date: Mon, 10 Aug 2009 15:05:29 +0200<BR>> From: "Becker, Thomas" <thob@dmu.dk><BR>> Subject: RE: [gdal-dev] reprojection HDF / GCP extraction<BR>> To: "Lucena, Ivan" <ivan.lucena@pmldnet.com><BR>> Cc: "gdal-dev@lists.osgeo.org" <gdal-dev@lists.osgeo.org><BR>> Message-ID:<BR>> <D4AB8C2051A3D1449495F8E45815E6000B2ADCF470@dmupost.dmu.dk><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> Hello Ivan,<BR>> <BR>> thanks for the hint. Now is this how GDAL already works? Because this track is meant for comments. At least in my data which are from 2000 I can not see any metadata of that kind. After reading the trac I am puzzled. Also in the output of gdalinfo only the subdatset of 'Data Fields' is mentioned and not the subdataset of 'Geolocation Fields'. I can not realy see which band represent latitude and longitude.<BR>> <BR>> If I just don't understand the trac maybe you can tell me how a command to GDAL, based on the gdalinfo output would look like to get the job done.<BR>> <BR>> Regards,<BR>> <BR>> Thomas<BR>> <BR>> -----Original Message-----<BR>> From: Lucena, Ivan [mailto:ivan.lucena@pmldnet.com] <BR>> Sent: Monday, August 10, 2009 2:15 PM<BR>> To: Becker, Thomas; gdal-dev@lists.osgeo.org<BR>> Subject: Re: [gdal-dev] reprojection HDF / GCP extraction<BR>> <BR>> Becker,<BR>> <BR>> Please take a look at RFC#4: http://trac.osgeo.org/gdal/wiki/rfc4_geolocate<BR>> <BR>> Regards,<BR>> <BR>> Ivan<BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 4<BR>> Date: Mon, 10 Aug 2009 08:37:17 -0500<BR>> From: " Lucena, Ivan " <ivan.lucena@pmldnet.com><BR>> Subject: RE: [gdal-dev] reprojection HDF / GCP extraction<BR>> To: "Becker, Thomas" <thob@dmu.dk><BR>> Cc: "gdal-dev@lists.osgeo.org" <gdal-dev@lists.osgeo.org><BR>> Message-ID: <20090810133719.21851.qmail@s466.sureserver.com><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> Becker,<BR>> <BR>> I afraid I don't have much to add to what is in the RFC#4. You can search on the discussion list archives for more <BR>> information or wait for the sun to weak up the experts.<BR>> <BR>> Regards,<BR>> <BR>> Ivan<BR>> <BR>> <BR>> > -------Original Message-------<BR>> > From: Becker, Thomas <thob@dmu.dk><BR>> > Subject: RE: [gdal-dev] reprojection HDF / GCP extraction<BR>> > Sent: Aug 10 '09 08:05<BR>> > <BR>> > Hello Ivan,<BR>> > <BR>> > thanks for the hint. Now is this how GDAL already works? Because this track is meant for comments. At least in <BR>> my data which are from 2000 I can not see any metadata of that kind. After reading the trac I am puzzled. Also in <BR>> the output of gdalinfo only the subdatset of 'Data Fields' is mentioned and not the subdataset of 'Geolocation <BR>> Fields'. I can not realy see which band represent latitude and longitude.<BR>> > <BR>> > If I just don't understand the trac maybe you can tell me how a command to GDAL, based on the gdalinfo <BR>> output would look like to get the job done.<BR>> > <BR>> > Regards,<BR>> > <BR>> > Thomas<BR>> > <BR>> > -----Original Message-----<BR>> > From: Lucena, Ivan [mailto:ivan.lucena@pmldnet.com]<BR>> > Sent: Monday, August 10, 2009 2:15 PM<BR>> > To: Becker, Thomas; gdal-dev@lists.osgeo.org<BR>> > Subject: Re: [gdal-dev] reprojection HDF / GCP extraction<BR>> > <BR>> > Becker,<BR>> > <BR>> > Please take a look at RFC#4: http://trac.osgeo.org/gdal/wiki/rfc4_geolocate<BR>> > <BR>> > Regards,<BR>> > <BR>> > Ivan<BR>> > <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 5<BR>> Date: Mon, 10 Aug 2009 11:12:45 -0400<BR>> From: Daniel Morissette <dmorissette@mapgears.com><BR>> Subject: Re: [gdal-dev] Motion: Adopt GDAL 1.6.2RC2 as final release<BR>> To: gdal-dev <gdal-dev@lists.osgeo.org><BR>> Message-ID: <4A8038ED.6080709@mapgears.com><BR>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<BR>> <BR>> Frank Warmerdam wrote:<BR>> > Motion: Adopt GDAL 1.6.2RC2 as official GDAL/OGR 1.6.2 release.<BR>> > <BR>> <BR>> +1 (Sorry for the delayed vote, I was away last week. I just tested it <BR>> and it seems fine.)<BR>> <BR>> <BR>> Daniel<BR>> -- <BR>> Daniel Morissette<BR>> http://www.mapgears.com/<BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> _______________________________________________<BR>> gdal-dev mailing list<BR>> gdal-dev@lists.osgeo.org<BR>> http://lists.osgeo.org/mailman/listinfo/gdal-dev<BR>> <BR>> End of gdal-dev Digest, Vol 63, Issue 23<BR>> ****************************************<BR><br /><hr /> يمكنك تنظيم صورك وتحريرها باستخدام Windows Live. <a href='http://www.microsoft.com/middleeast/arabic/windows/windowslive/products/photo-gallery-edit.aspx' target='_new'>قم بمشاركة صورك.</a></body>
</html>