[gdal-dev] RE: gdal-dev Digest, Vol 63, Issue 23
Abdullah Al jadidi
aljadidi65 at hotmail.com
Thu Aug 13 00:32:17 EDT 2009
so could you stop set messenge to me .
thank again, Tahnk you for coopration and all information
> From: gdal-dev-request at lists.osgeo.org
> Subject: gdal-dev Digest, Vol 63, Issue 23
> To: gdal-dev at lists.osgeo.org
> Date: Mon, 10 Aug 2009 12:00:21 -0400
>
> Send gdal-dev mailing list submissions to
> gdal-dev at lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
> or, via email, send a message with subject or body 'help' to
> gdal-dev-request at lists.osgeo.org
>
> You can reach the person managing the list at
> gdal-dev-owner at lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gdal-dev digest..."
>
>
> Today's Topics:
>
> 1. reprojection HDF / GCP extraction (Becker, Thomas)
> 2. Re: reprojection HDF / GCP extraction ( Lucena, Ivan )
> 3. RE: reprojection HDF / GCP extraction (Becker, Thomas)
> 4. RE: reprojection HDF / GCP extraction ( Lucena, Ivan )
> 5. Re: Motion: Adopt GDAL 1.6.2RC2 as final release
> (Daniel Morissette)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 10 Aug 2009 14:00:50 +0200
> From: "Becker, Thomas" <thob at dmu.dk>
> Subject: [gdal-dev] reprojection HDF / GCP extraction
> To: "gdal-dev at lists.osgeo.org" <gdal-dev at lists.osgeo.org>
> Message-ID:
> <D4AB8C2051A3D1449495F8E45815E6000B2ADCF42E at dmupost.dmu.dk>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi all,
>
> 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.
>
> 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.
>
> Using gdalwarp leads to the message: There is no affine transformation and no GCPs.
>
> 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.
>
> Thanks for your help.
>
> Best regards,
> Thomas
>
> gdalinfo output:
>
> Driver: HDF4/Hierarchical Data Format Release 4
> Files: amsua15_2000.034_08964_0104_0258_GC.eos
> Size is 512, 512
> Coordinate System is `'
> Metadata:
> HDFEOSVersion=HDFEOS_V2.4
> Subdatasets:
> SUBDATASET_1_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:23800.37 MHz
> SUBDATASET_1_DESC=[851x30] 23800.37 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_2_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:31400.42 MHz
> SUBDATASET_2_DESC=[851x30] 31400.42 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_3_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:50299.91 MHz
> SUBDATASET_3_DESC=[851x30] 50299.91 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_4_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:52799.39 MHz
> SUBDATASET_4_DESC=[851x30] 52799.39 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_5_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:53595.41 +- 115 MHz
> SUBDATASET_5_DESC=[851x30] 53595.41 +- 115 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_6_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:54399.53 MHz
> SUBDATASET_6_DESC=[851x30] 54399.53 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_7_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:54940.64 MHz
> SUBDATASET_7_DESC=[851x30] 54940.64 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_8_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:55498.70 MHz
> SUBDATASET_8_DESC=[851x30] 55498.70 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_9_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 MHz
> SUBDATASET_9_DESC=[851x30] 57290.33 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_10_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 217 MHz
> SUBDATASET_10_DESC=[851x30] 57290.33 +- 217 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_11_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 322.2 +- 48 MHz
> SUBDATASET_11_DESC=[851x30] 57290.33 +- 322.2 +- 48 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_12_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 322.2 +- 22 MHz
> SUBDATASET_12_DESC=[851x30] 57290.33 +- 322.2 +- 22 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_13_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 322.2 +- 10 MHz
> SUBDATASET_13_DESC=[851x30] 57290.33 +- 322.2 +- 10 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_14_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:57290.33 +- 322.2 +- 4.5 MHz
> SUBDATASET_14_DESC=[851x30] 57290.33 +- 322.2 +- 4.5 MHz Orbit 8964 (32-bit floating-point)
> SUBDATASET_15_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit 8964:88997.00 MHz
> SUBDATASET_15_DESC=[851x30] 88997.00 MHz Orbit 8964 (32-bit floating-point)
> Corner Coordinates:
> Upper Left ( 0.0, 0.0)
> Lower Left ( 0.0, 512.0)
> Upper Right ( 512.0, 0.0)
> Lower Right ( 512.0, 512.0)
> Center ( 256.0, 256.0)
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 10 Aug 2009 07:14:39 -0500
> From: " Lucena, Ivan " <ivan.lucena at pmldnet.com>
> Subject: Re: [gdal-dev] reprojection HDF / GCP extraction
> To: "Becker, Thomas" <thob at dmu.dk>, "gdal-dev at lists.osgeo.org"
> <gdal-dev at lists.osgeo.org>
> Message-ID: <20090810121439.27899.qmail at s466.sureserver.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Becker,
>
> Please take a look at RFC#4: http://trac.osgeo.org/gdal/wiki/rfc4_geolocate
>
> Regards,
>
> Ivan
>
>
> > -------Original Message-------
> > From: Becker, Thomas <thob at dmu.dk>
> > Subject: [gdal-dev] reprojection HDF / GCP extraction
> > Sent: Aug 10 '09 07:00
> >
> > Hi all,
> >
> > 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.
> >
> > 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.
> >
> > Using gdalwarp leads to the message: There is no affine transformation and no GCPs.
> >
> > 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.
> >
> > Thanks for your help.
> >
> > Best regards,
> > Thomas
> >
> > gdalinfo output:
> >
> > Driver: HDF4/Hierarchical Data Format Release 4
> > Files: amsua15_2000.034_08964_0104_0258_GC.eos
> > Size is 512, 512
> > Coordinate System is `'
> > Metadata:
> > HDFEOSVersion=HDFEOS_V2.4
> > Subdatasets:
> > SUBDATASET_1_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:23800.37 MHz
> > SUBDATASET_1_DESC=[851x30] 23800.37 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_2_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:31400.42 MHz
> > SUBDATASET_2_DESC=[851x30] 31400.42 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_3_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:50299.91 MHz
> > SUBDATASET_3_DESC=[851x30] 50299.91 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_4_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:52799.39 MHz
> > SUBDATASET_4_DESC=[851x30] 52799.39 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_5_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:53595.41 +- 115 MHz
> > SUBDATASET_5_DESC=[851x30] 53595.41 +- 115 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_6_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:54399.53 MHz
> > SUBDATASET_6_DESC=[851x30] 54399.53 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_7_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:54940.64 MHz
> > SUBDATASET_7_DESC=[851x30] 54940.64 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_8_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:55498.70 MHz
> > SUBDATASET_8_DESC=[851x30] 55498.70 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_9_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:57290.33 MHz
> > SUBDATASET_9_DESC=[851x30] 57290.33 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_10_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:57290.33 +- 217 MHz
> > SUBDATASET_10_DESC=[851x30] 57290.33 +- 217 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_11_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:57290.33 +- 322.2 +- 48 MHz
> > SUBDATASET_11_DESC=[851x30] 57290.33 +- 322.2 +- 48 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_12_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:57290.33 +- 322.2 +- 22 MHz
> > SUBDATASET_12_DESC=[851x30] 57290.33 +- 322.2 +- 22 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_13_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:57290.33 +- 322.2 +- 10 MHz
> > SUBDATASET_13_DESC=[851x30] 57290.33 +- 322.2 +- 10 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_14_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:57290.33 +- 322.2 +- 4.5 MHz
> > SUBDATASET_14_DESC=[851x30] 57290.33 +- 322.2 +- 4.5 MHz Orbit 8964 (32-bit floating-point)
> > SUBDATASET_15_NAME=HDF4_EOS:EOS_SWATH:"amsua15_2000.034_08964_0104_0258_GC.eos":Orbit
> 8964:88997.00 MHz
> > SUBDATASET_15_DESC=[851x30] 88997.00 MHz Orbit 8964 (32-bit floating-point)
> > Corner Coordinates:
> > Upper Left ( 0.0, 0.0)
> > Lower Left ( 0.0, 512.0)
> > Upper Right ( 512.0, 0.0)
> > Lower Right ( 512.0, 512.0)
> > Center ( 256.0, 256.0)
> > _______________________________________________
> > gdal-dev mailing list
> > gdal-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/gdal-dev
> >
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 10 Aug 2009 15:05:29 +0200
> From: "Becker, Thomas" <thob at dmu.dk>
> Subject: RE: [gdal-dev] reprojection HDF / GCP extraction
> To: "Lucena, Ivan" <ivan.lucena at pmldnet.com>
> Cc: "gdal-dev at lists.osgeo.org" <gdal-dev at lists.osgeo.org>
> Message-ID:
> <D4AB8C2051A3D1449495F8E45815E6000B2ADCF470 at dmupost.dmu.dk>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello Ivan,
>
> 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.
>
> 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.
>
> Regards,
>
> Thomas
>
> -----Original Message-----
> From: Lucena, Ivan [mailto:ivan.lucena at pmldnet.com]
> Sent: Monday, August 10, 2009 2:15 PM
> To: Becker, Thomas; gdal-dev at lists.osgeo.org
> Subject: Re: [gdal-dev] reprojection HDF / GCP extraction
>
> Becker,
>
> Please take a look at RFC#4: http://trac.osgeo.org/gdal/wiki/rfc4_geolocate
>
> Regards,
>
> Ivan
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 10 Aug 2009 08:37:17 -0500
> From: " Lucena, Ivan " <ivan.lucena at pmldnet.com>
> Subject: RE: [gdal-dev] reprojection HDF / GCP extraction
> To: "Becker, Thomas" <thob at dmu.dk>
> Cc: "gdal-dev at lists.osgeo.org" <gdal-dev at lists.osgeo.org>
> Message-ID: <20090810133719.21851.qmail at s466.sureserver.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Becker,
>
> 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
> information or wait for the sun to weak up the experts.
>
> Regards,
>
> Ivan
>
>
> > -------Original Message-------
> > From: Becker, Thomas <thob at dmu.dk>
> > Subject: RE: [gdal-dev] reprojection HDF / GCP extraction
> > Sent: Aug 10 '09 08:05
> >
> > Hello Ivan,
> >
> > 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.
> >
> > 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.
> >
> > Regards,
> >
> > Thomas
> >
> > -----Original Message-----
> > From: Lucena, Ivan [mailto:ivan.lucena at pmldnet.com]
> > Sent: Monday, August 10, 2009 2:15 PM
> > To: Becker, Thomas; gdal-dev at lists.osgeo.org
> > Subject: Re: [gdal-dev] reprojection HDF / GCP extraction
> >
> > Becker,
> >
> > Please take a look at RFC#4: http://trac.osgeo.org/gdal/wiki/rfc4_geolocate
> >
> > Regards,
> >
> > Ivan
> >
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 10 Aug 2009 11:12:45 -0400
> From: Daniel Morissette <dmorissette at mapgears.com>
> Subject: Re: [gdal-dev] Motion: Adopt GDAL 1.6.2RC2 as final release
> To: gdal-dev <gdal-dev at lists.osgeo.org>
> Message-ID: <4A8038ED.6080709 at mapgears.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Frank Warmerdam wrote:
> > Motion: Adopt GDAL 1.6.2RC2 as official GDAL/OGR 1.6.2 release.
> >
>
> +1 (Sorry for the delayed vote, I was away last week. I just tested it
> and it seems fine.)
>
>
> Daniel
> --
> Daniel Morissette
> http://www.mapgears.com/
>
>
> ------------------------------
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>
> End of gdal-dev Digest, Vol 63, Issue 23
> ****************************************
_________________________________________________________________
.Windows Live يمكنك تنظيم صورك وتحريرها ومشاركتها باستخدام
http://www.microsoft.com/middleeast/arabic/windows/windowslive/products/photo-gallery-edit.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/gdal-dev/attachments/20090813/54556464/attachment-0001.html
More information about the gdal-dev
mailing list