-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of SR McMullan
Sent: Monday, 7 October 2002 4:05 PM
To: [EMAIL PROTECTED]
Subject: RE: Registration of imagesHi Huapeng,I recently had the same problem with EROS A1 imagery in TFW format. Here is what I think has happened, and my work-around.The GeoTiff format only specifies six parameters in a planar rectangular matrix, which relates the Raster Space (image) to Model Space (Earth-based system). The six parameters in the GeoTiff specification are stored in the TFW file accompanying your image and are defined as follows:ResolutionUnit (296)
XResolution (282)
YResolution (283)
Orientation (274)
XPosition (286)
YPosition (287)ER Mapper 6.3 imports the TFW file directly, but does not use the TFW information in the ERS header. Note that because there is no projection information in the TFW file, ER Mapper also uses "RAW" datum and projection.Probably the simplest thing to do is import the TIF and accompanying TFW files into ERM and save as ERS datasets. Then edit the projection, cell size and registration coordinates in the ERS file, and reload the images.Now I really didn't trust this method, because you are assuming the TIFF files were planar/rectangular/vertical orientation to start with. What I did to check the registration is to use control points for the original EROS (SPOT/Ikonos in this case) and re-warp the scene. You may then have to move one of the images around a bit to make sure they register together.For lots of really good info on the GeoTiff specifications, hit the GeoTiff Web site at http://www.remotesensing.org/geotiff/spec/geotiff2.5.html#2.5Cheers, and happy imaging!SRM.Steven R. McMullan, P.Geo.
Principal GeophysicistPoseidon Geophysics (Pty) Limited
Plot 3423 Matima Crescent Extention 12
Private Bag X018
Gaborone, BotswanaTel +267 351 612
Cell +267 71 300 820
Fax +267 300 787
E-mail [EMAIL PROTECTED]
Personal E-mail [EMAIL PROTECTED]-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Trevor Chen
Sent: 05 October 2002 03:50 PM
To: [EMAIL PROTECTED]
Subject: Registration of images>From: [EMAIL PROTECTED] (List Server) >Reply-To: [EMAIL PROTECTED] >Subject: ERMAPPER-L Daily Digest >Date: Thu, 3 Oct 2002 03:28:27 +0800 > >---------------------------------------------------------------------- > >Date: Tue, 1 Oct 2002 16:52:52 -0400 (EDT) >Subject: Comparing Gridded Datasets >From: "Greg Reinecke" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >Hello List, > >I have been working with a client that has numerous gridded elevation >datasets produced over time. We wish to compare changes between two >datasets that cover the same extents on the ground and have the same pixel >dimensions. I tried using the provided formula for calculating the >difference between two datasets but just can't seem to get the desired >results (difference between the two datasets). I suspect I am doing >something wrong in the algorithm. Any insight would be much appreciated. > >********************************************** >Gregory T. Reinecke >President & CEO >Geographic Technology & Resource Systems, Inc. >P.O.Box 651023 >Potomac Falls, VA 20165 >www.gtrsystems.com > >---------------------------------------------------------------------- > >From: "John Cady" <[EMAIL PROTECTED]> >Subject: Re: Comparing Gridded Datasets >Date: Tue, 1 Oct 2002 21:04:18 -0600 >Reply-To: [EMAIL PROTECTED] >Greg, > >Have you combined the datasets into a single multiple-layer dataset:? You >need to do that to do so in order to apply a simple difference formula in ER >Mapper. The method works well. > >John Cady >______________________________________ >----- Original Message ----- >From: "Greg Reinecke" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Tuesday, October 01, 2002 2:52 PM >Subject: Comparing Gridded Datasets > > > > Hello List, > > > > I have been working with a client that has numerous gridded elevation > > datasets produced over time. We wish to compare changes between two > > datasets that cover the same extents on the ground and have the same pixel > > dimensions. I tried using the provided formula for calculating the > > difference between two datasets but just can't seem to get the desired > > results (difference between the two datasets). I suspect I am doing > > something wrong in the algorithm. Any insight would be much appreciated. > > > > ********************************************** > > Gregory T. Reinecke > > President & CEO > > Geographic Technology & Resource Systems, Inc. > > P.O.Box 651023 > > Potomac Falls, VA 20165 > > www.gtrsystems.com > > > > ----------------------------------------------------------- > > > > To make changes to your subscription, please visit our website, >http://www.ermapper.com/technicl/ermapperl/index.htm > > > > > > > >---------------------------------------------------------------------- > >From: "John Cady" <[EMAIL PROTECTED]> >Subject: Re: Comparing Gridded Datasets >Date: Tue, 1 Oct 2002 21:04:27 -0600 >Reply-To: [EMAIL PROTECTED] > >----- Original Message ----- >From: "Greg Reinecke" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Tuesday, October 01, 2002 2:52 PM >Subject: Comparing Gridded Datasets > > > > Hello List, > > > > I have been working with a client that has numerous gridded elevation > > datasets produced over time. We wish to compare changes between two > > datasets that cover the same extents on the ground and have the same pixel > > dimensions. I tried using the provided formula for calculating the > > difference between two datasets but just can't seem to get the desired > > results (difference between the two datasets). I suspect I am doing > > something wrong in the algorithm. Any insight would be much appreciated. > > > > ********************************************** > > Gregory T. Reinecke > > President & CEO > > Geographic Technology & Resource Systems, Inc. > > P.O.Box 651023 > > Potomac Falls, VA 20165 > > www.gtrsystems.com > > > > ----------------------------------------------------------- > > > > To make changes to your subscription, please visit our website, >http://www.ermapper.com/technicl/ermapperl/index.htm > > > > > > > >---------------------------------------------------------------------- > >From: "Leo Romeijn" <[EMAIL PROTECTED]> >Subject: Gridding memory allocation problem >Date: Wed, 2 Oct 2002 10:09:54 -0500 >Reply-To: [EMAIL PROTECTED] >This is a multi-part message in MIME format. > >------=_NextPart_000_0012_01C269FB.DAF1C260 >Content-Type: text/plain; > charset="us-ascii" >Content-Transfer-Encoding: 7bit > >List, > > I am trying to grid an XYZ text file (482mb), using the Minimum >Curvature option with the defaults, but I keep getting an error message >(listed below), and the status bar stops at about 85%. The terrain is >min: 6m to max: 2400m, there is a big mountain in the scene, coming from >the coastline. Has anyone else run into this problem with the Minimum >Curvature option? I have been successful on smaller areas, but I am >unsure why I am running out of memory or what the problem could be. > >Error Box: >Gridding Terminated Abnormally > >Status box: >Reading Data. >Read 17729803 points, (min:6.000 max:2442.000) >Could not allocate 851030544 bytes of memory >Connection closed. > >Platform: Win2K >Ram: 2GB >Virtual Mem: >C:\ None >D:\1024mb >H:\1024mb >ER Mapper 6.3 > > > >Leo M. Romeijn >Satellite Imaging Corporation >12777 Jones Rd., Suite 370 >Houston, TX 77070, USA >832.237.2900 ext.202, 832.237.2910 (Fax) >[EMAIL PROTECTED] >www.satimagingcorp.com > > > >------=_NextPart_000_0012_01C269FB.DAF1C260 >Content-Type: text/html; > charset="us-ascii" >Content-Transfer-Encoding: quoted-printable > > > > > >charset=3Dus-ascii"> > >6.0.4630.0"> > > > > > >Hi All,
I brought one SPOT and one IKONOS images both in GeoTiff format and having same projection (UTM 39) and datum (WGS84) into ERMAPPER but they could not register each other very well. The IKONOS image was apparently in wrong place. I displayed them together in ArcMap and they registered very well. They were in right place. I appreciate it if anyone could figure out what happens. Something wrong with ERMapper?
Cheers,
Huapeng Chen
GIS Specialist, Aramco, Saudi Arabia
>FACE=3D"Arial">List,
> >>LANG=3D"en-us"> >FACE=3D"Arial">I am trying to grid an XYZ text file (482mb), = >usin>FACE=3D"Arial">g = >the>FACE=3D"Arial"> >FACE=3D"Arial">Minimum Curvature option>LANG=3D"en-us"> = >with the defaults>LANG=3D"en-us">, but I keep getting = >an = >error message = >(listed below), = >and the sta>FACE=3D"Arial">t>FACE=3D"Arial">us bar stops at about 85%.>LANG=3D"en-us"> = >The terrain is min: 6m to max: 2400m, there is a = >big mountain in the scene, coming>LANG=3D"en-us"> from>LANG=3D"en-us"> the coastline.>LANG=3D"en-us"> Has anyone else run into this = >problem with the >FACE=3D"Arial">Minimum Curvature option>LANG=3D"en-us">? I have been>LANG=3D"en-us"> successful>LANG=3D"en-us"> = >on smaller areas, but I am unsure why I am running = >out of memory or = >what the problem could be.
> >>FACE=3D"Arial">Error>FACE=3D"Arial"> Box:
> >Gridding = >Terminate>FACE=3D"Arial">d = >Abnormally
> >Status = >box:
> >>FACE=3D"Arial">Rea>FACE=3D"Arial">d>FACE=3D"Arial">ing Data>FACE=3D"Arial">...
> >Read 17729803 = >points, (min:6.000 max:2442.000)>LANG=3D"en-us">
> >Could not = >allocate 851030544 bytes of memory
> >Connection = >closed>FACE=3D"Arial">...
> >>FACE=3D"Arial">Platform>FACE=3D"Arial">: Win2K
> >Ram: = >2GB
> >>FACE=3D"Arial">Virtual>FACE=3D"Arial"> Mem:
> >C:\ = >None
> >>FACE=3D"Arial">D:\1024>FACE=3D"Arial">mb
> >>FACE=3D"Arial">H:\1024mb
> >ER = >Map>FACE=3D"Arial">p>FACE=3D"Arial">er 6.3
>
>
> >>LANG=3D"en-us">Leo M. = >Romeijn
> >>Black">Satellite Imaging Corporation
> >>FACE=3D"Arial">12777 Jones Rd., Suite 370
> >>FACE=3D"Arial">Houston, TX 77070, USA
> >>FACE=3D"Arial">832.237.2900 ext.202, 832.237.2910 = >(Fax)
> >>FACE=3D"Arial">[EMAIL PROTECTED]
> >>FACE=3D"Arial">www.satimagingcorp.com
> >> > > >------=_NextPart_000_0012_01C269FB.DAF1C260-- > >---------------------------------------------------------- >To stop receiving the daily digest, send email to [EMAIL PROTECTED] with the command > set mode standard ermapper-l >in the body.
Join the world's largest e-mail service with MSN Hotmail. Click Here
----------------------------------------------------------- To make changes to your subscription, please visit our website, http://www.ermapper.com/technicl/ermapperl/index.htm
Just a
quick 2 cents on this -
Geotiff files should be able to be treated as
independent complete files with
sufficient projection info (datum/projection/parameters
if needed).
TFW
files (as noted below) have no datum/projection info, and are designed primarily
for
use
with ESRI products (TFW is an ESRI format as far as I know).
The
fact that Geotiff is self contained, and tfw is not (and contains a subset of
the Geotiff info)
implies that Geotiff + tfw is theoretically a redundant
combination.
Tiff
(not Geotiff) + tfw is a more practical combination.
Reality is that tfw (and world files in general) are in
wide use, and their handling within ER Mapper
can be
improved. We are currently working on this and should have something available
in the next
1-2
months.
Cheers
Mike
- Registration of images Trevor Chen
- RE: Registration of images SR McMullan
- RE: Registration of images Mike Dunne
- RE: Registration of images Mpaka . O . Erekosima
- RE: Registration of images Gerard_Zaluski
