[ gpsdrive ] gpsdrive and NOAA charts

Mon May 12 19:08:17 AKDT 2008

On Monday 12 May 2008 07:08:07 am Chris H wrote:
> On Monday 12 May 2008 00:41:19 Hamish wrote:
> > which version did you try with?
>
> chris123 at kubuntu8:~$ gdalinfo --version
> GDAL 1.4.4.0, released 2007/11/23

tried again on same system to eliminate the memory shortage issues (pls dont 
laugh but I run a business on 256M RAM and P1.3 processor and it works fine 
except for image rendering..)

System is triple boot so this time tested with opensuse 10.3

chris123 at s103:~> gdalinfo --version
GDAL 1.5.0, released 2007/12/18

> The syntax I used was :
> chris123 at kubuntu8:~$ gdalwarp -t_srs "EPSG:4326" -order 2 -rn 12200_1.KAP
> noaa_1.tif

same syntax

and a smashing success..!!!

gdal converted the same test file to tif without issues.
running gdalslice.sh on the file and it completed successfully however did 
give me the following errors towards the end repeatedly:
Processing chunk [8640 0] ...
Input file size is 9619, 12838
-srcwin 8640 0 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 768] ...
Input file size is 9619, 12838
-srcwin 8640 768 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 1536] ...
Input file size is 9619, 12838
-srcwin 8640 1536 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 2304] ...
Input file size is 9619, 12838
-srcwin 8640 2304 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 3072] ...
Input file size is 9619, 12838
-srcwin 8640 3072 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 3840] ...
Input file size is 9619, 12838
-srcwin 8640 3840 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 4608] ...
Input file size is 9619, 12838
-srcwin 8640 4608 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 5376] ...
Input file size is 9619, 12838
-srcwin 8640 5376 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 6144] ...
Input file size is 9619, 12838
-srcwin 8640 6144 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 6912] ...
Input file size is 9619, 12838
-srcwin 8640 6912 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 7680] ...
Input file size is 9619, 12838
-srcwin 8640 7680 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 8448] ...
Input file size is 9619, 12838
-srcwin 8640 8448 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 9216] ...
Input file size is 9619, 12838
-srcwin 8640 9216 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 9984] ...
Input file size is 9619, 12838
-srcwin 8640 9984 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 10752] ...
Input file size is 9619, 12838
-srcwin 8640 10752 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

Processing chunk [8640 11520] ...
Input file size is 9619, 12838
-srcwin 8640 11520 1280 1024 falls outside raster size of 9619x12838
or is otherwise illegal.
Quietly moving on ...

However reviewing map_koord_draft.txt it finally looks good;

example:
top_noaa_12200_0_0.png 39.121497222 -75.919413889 127114
top_noaa_12200_0_768.png 38.809730556 -75.919413889 127114
top_noaa_12200_0_1536.png 38.497963889 -75.919413889 127114
top_noaa_12200_0_2304.png 38.186197222 -75.919413889 127114
top_noaa_12200_0_3072.png 37.874430556 -75.919413889 127114
top_noaa_12200_0_3840.png 37.562663889 -75.919413889 127114
top_noaa_12200_0_4608.png 37.250897222 -75.919413889 127114
top_noaa_12200_0_5376.png 36.939130556 -75.919413889 127114
top_noaa_12200_0_6144.png 36.627363889 -75.919413889 127114
top_noaa_12200_0_6912.png 36.315594444 -75.919413889 127114
top_noaa_12200_0_7680.png 36.003827778 -75.919413889 127114
top_noaa_12200_0_8448.png 35.692061111 -75.919413889 127114
top_noaa_12200_0_9216.png 35.380294444 -75.919413889 127114
top_noaa_12200_0_9984.png 35.068527778 -75.919413889 127114
top_noaa_12200_0_10752.png 34.756761111 -75.919413889 127114
top_noaa_12200_0_11520.png 34.444994444 -75.919413889 127114
top_noaa_12200_960_0.png 39.121497222 -75.529705556 127114

Last step is to test these files in gpsdrive. Will do that tomorrow. 

So all I can conclude from this exercise is that there must be a difference 
between the kubuntu and opensuse package other then the version number but I 
really dont trust package numbers from different vendors. The latest suse 
package is identified as gdal-1.5.1-5.1.i586.rpm  23-Mar-2008 09:17  284K on 
http://download.opensuse.org/repositories/Application:/Geo/openSUSE_10.3/i586/
which is even newer then the current 1.5.0-9.3 installed locally. Yet the gdal 
site seems to favor a 1.4 release level. Who knows. ..:) 

Regardless, this version seems to work flawlessly. Over the comming days since 
Im migrating most of my workstations to Kubuntu I will do a fresh 8.0.4 
install and see if the situation changes. That will be telling. 

Many thanks for your patience as this is really important to me and a very 
interesting and potentially important alternative usage of gpsdrive. 

A change request if I may Hamish.

The gdal slice script seems to work just fine, however would it be possible to 
augment this script to allow it run in batch mode without the need of 
identifying the input and output files as these are basically standardized 
for noaa charts. 

For example a nice feature would be for the script to walk through a directory 
of noaa_xxx.tif files and create the necessary tiles in discrete folders with 
the base name of noaa_xxx and with a base output file of noaa_xxx as is 
currently defined by the script anyway. 

In this manner a directory containing several hundred noaa_xxx.tif files, 
could be processed in batch mode. Once done it would not be that difficult to 
load the data into say a UMN mapserver and make them available to everyone. 

Just a thought. Sorry I don't code nor script unfortunately. Currently 
learning the rudimentary steps of mapserver. Someday I'll tackle grass but 
thats a different beast altogether. 

Thanks again Hamish and others.  
-- 
/ch