[Proj] ntf_r93.gsb file corrupted

[Cuinet Jérôme]

MD5 test is to tests the file integrity. But if here the problem is due to 
file integrity, further problem of regression may be due to another cause.

Development tests may include MD5 integrity test, but finally global test 
could be made. The aim is to detect a problem, next to diagnostic it, is it 
?


----- Original Message ----- 
From: "Eric Miller" <EMiller at dfg.ca.gov>
To: "PROJ.4 and general Projections Discussions" <proj at lists.maptools.org>
Sent: Friday, September 25, 2009 12:17 AM
Subject: Re: [Proj] ntf_r93.gsb file corrupted


>>> On 9/24/2009 at 11:49 AM, Frank Warmerdam <warmerdam at pobox.com>
wrote:
> Cuinet Jérôme wrote:
>> A question :
>>
>> Are not there some coordinate transformation tests which verifiy the

>> calculations ?
>>
>> I don't know how often mistakes appears, but this type of tests
don't seems
>> to be diificult to construct.
>
> Jérôme,
>
> There are regression tests, but they do not include ntf_r93.gsb even
now.
> I would add the problem corrupted the file in a relatively subtle way
that
> would only be detected for a grid shift in some places.

Wouldn't it be better to use md5 checksums or digital signatures to
verify that a data file's contents haven't been altered?  The md5 sum
approach doesn't provide much security, but it can be a quick
verification check that something hasn't gone horribly wrong with the
file.

md5sum ntf_r93.gsb > ntf_r93.gsb.md5sum

md5sum -c ntf_r93.gsb.md5sum

Or some variation...

-- 

Eric G. Miller
Staff Programmer
CA Dept. of Fish & Game

_______________________________________________
Proj mailing list
Proj at lists.maptools.org
http://lists.maptools.org/mailman/listinfo/proj