This all looks fine.
And you said that the destination tiff was smaller than the original?
Can you display the tiff files?
Maybe it's some disk problem (in the log you sent last time, it seems
there was an error reading the file...)?
On 05/25/2010 04:10 PM, Jenny Turner wrote:
Sorry Micha
My
Micha
You are absolutely right. I was running it in a shared folder, and for some
reason (not space beucase it's not full), i was getting that error. Now, I
tried in a Desktop folder and it worked.
Thanks
2010/5/26 Micha Silver mi...@arava.co.il
This all looks fine.
And you said that the
On 05/25/2010 11:17 AM, Jenny Turner wrote:
Yes Sure :)
Attached to this email you can find the log
I was thinking of just the results of gdalinfo. This way we can see if
the tiff is being recognized, and if its CRS is is available in the tiff
header.
Here's an example:
~gdalinfo
Sorry Micha
My original Landsat image:
Driver: GTiff/GeoTIFF
Files: L71203033_0332601_B10.TIF
L71203033_0332601_B10.aux
L71203033_0332601_B10.rrd
Size is 8161, 7141
Coordinate System is:
PROJCS[WGS 84 / UTM zone 29N,
GEOGCS[WGS 84,
DATUM[WGS_1984,
Hi
Following this topic I have tested this methodology by converting from UTM
29N to a specific local coordinate system (EPSG:3763) (available at PROJ4)
gdalwarp -t_srs EPSG:3763 band_landsat.TIF destination.tif
With that I got a segmentation error, one TIFFReadDirectory a lot of
On 05/24/2010 06:26 PM, Jenny Turner wrote:
Hi
Following this topic I have tested this methodology by converting from
UTM 29N to a specific local coordinate system (EPSG:3763) (available
at PROJ4)
gdalwarp -t_srs EPSG:3763 band_landsat.TIF destination.tif
With that I got a segmentation
Greetings
Firman, but imagine that I have rasters in UTM for differente zones (e.g.
huge countries like USA, etc). How can I produce an automatic importing tool
that uses gdalwarp to project an image to WGS84 and import to GRASS?
Thanks for your help
Best regards,
Jenny
On Mon, May 17, 2010 at
Dear Jenny,
Yes, I am agree that will be such a huge work :D.
Actually I am not familiar with shell script but maybe I can imagine the
workflow
and perhaps someone in this list can help.
I think the algorithm of such script is:
1. Put all the imageries in one folder
2. Use gdalinfo command to
Jenny Turner wrote:
Greetings
Firman, but imagine that I have rasters in UTM for differente zones
(e.g. huge countries like USA, etc). How can I produce an automatic
importing tool that uses gdalwarp to project an image to WGS84 and
import to GRASS?
Using gdalwarp you don't have to specify
Greetings
Thanks It really worked but now I have one particualr question:
I need to have an automatic proceeding but, in this case my input images
are not in the same coordinate system (e.g. different UTM Zones). Can I
apply this methdology without defining source_coordinate system?
Thanks
Jenny
Hi,
As far as I know you must define the source coordinate system.
I think it is pretty straightforward when you are using gdalwarp.
If there are so many images, maybe you can create a shell script to run the
process.
Cheers,
Firman Hadi
Center for Remote Sensing - ITB
Jl. Ganesha No. 10,
Jenny Turner wrote:
I need to import Landsat images (r.in.gdal) to my location but, my Landsat
images are in a specific Coordinate system (WGS84) that is different from
mine. Could anyone explain me (briefly ) the steps to import this images?
(There is also a within-grass solution)
It is
Greetings
I need to import Landsat images (r.in.gdal) to my location but, my Landsat
images are in a specific Coordinate system (WGS84) that is different from
mine. Could anyone explain me (briefly ) the steps to import this images?
Thanks
Jenny
___
On 10 May 2010, at 18:00, Jenny Turner wrote:
Greetings
I need to import Landsat images (r.in.gdal) to my location but, my Landsat
images are in a specific Coordinate system (WGS84) that is different from
mine. Could anyone explain me (briefly ) the steps to import this images?
Thanks
14 matches
Mail list logo
