Bug - Verification (for same-format conversions) for format shapefile

Aspose.GIS Product Family
1

Hi Alexander,

For conversion from one format to itself, I make a verification (only for same-format conversions)
using checksums.
If checksums of input file and output file are differing is ok if not is not ok.

Please see:

Input files:
ShapeFiles.7z (326 Bytes)

shapefile4.7z (165.6 KB)

Code:

ConversionVerificationHelper.cs.zip (2.7 KB)

Thanks,

2

@danies8

You are reporting a potential issue with the verification process for same-format conversions using checksums, specifically for the Shapefile format . You’ve shared input files and a code helper file (ConversionVerificationHelper.cs.zip) related to this process . However, there is no direct evidence in the provided context confirming whether the bug exists, as you have not shared the actual checksum values or detailed error messages .

A similar issue was reported earlier for .stl files regarding blind watermarking verification, which was later resolved by the Aspose team [2, 3, 4].

To help determine if there is an issue with the Shapefile verification logic, please share the checksum values of the input and output files for the conversion, or any error messages encountered during the process.

3

Alexander , please check.

4

Hi, @danies8

I don’t understand what you wanna to do and what result you expected.
checksums the same because files the same.
if “(sourceDriver == destinationDriver)” why you need to do something ? Just do nothing.

5

When source format and target format are the same, you told me you read the main file abd nandatiries near him and copy the content to newww files.
The input and the output files are diffrenttt , so they have different checksums.

In the sample i gave you they have same checksums.

That means that out file is not a new file.
In other samples of converting from shapefile to shapefile, the checsums where different.

This check , only when source abd target have same format .
We make this validation ti make the conversion more stronger, to our CDR sytem-check virus from your output.
When the source and target are diffrent we do not need it since new files are creating in the output.

So, you undersand my point.
If yes can you check my samples, l gave you helper class , to check the checksums.

Thanks in advance,

6

Yes, we just make copy of file to output path, but for copy as for as i understand checksums should be the same. I will recheck you examples, maybe in case where checksums were different was something wrong

7

What does it mean not new if we create new file?

8

Files should be the same. The just have different time of creation