CRS - Problem when the data is displayed in different UTM zones at the same project.
Hello,
IesBrazil team is testing OpenVDS+ with CRS and one of the steps were to QC the data using Headwave from Bluware. The team noticed a problem and we did a documentation on the tests that I will present below:
Goal of the Tests: Check if OpenVDS+ is adding correctly the CRS into the VDS file,
Methodology: Convert SEGY to VDS using OpenVDS+/Headwave and QC the data using Headwave,
Data used: Volve and Brazilian data (Volve doesn't present any problem). From Brazil we used 4 files from Solimões Basin and 1 file from Amazonas Basin, provided by ANP. The data can find HERE, below you can download directly all the files used in this test (from Brazil, that is where we identified the problem):
- 0233_LESTE_URUCU.3D.MIG_FIN.1.sgy - Solimões Basin, SAD69/UTM 20S, EPSG:29190
- 0237_AEROPORTO.3D.MIG_FIN.1.sgy - Solimões Basin, SAD69/UTM 20S, EPSG:29190
- 0237_IGARAPE_MARTA.3D.MIG_FIN.2.sgy - Solimões Basin, SAD69/UTM 20S, EPSG:29190
- R0300_3D_CHIBATA_PSTM.3D.PSTM.1.sgy - Solimões Basin, SIRGAS 2000/UTM 20S, EPSG:31980
-
R0300_2D_AM_URUCARA.3D.PSTM.1.sgy - Amazonas Basin, SAD69/UTM 21S, EPSG:29191
Shapefile: Georeferenced polygons of exploratory blocks in geographic coordinates and datum SAD69, available HERE,
Problem: When the project has a different zone from the data (e.g: the project is located at SAD69/ UTM 20S and the data is located at SAD69/ UTM 21S), the file is wrongly spatially positioned (We used a VDS converted by Headwave and the original SEGY to compare),
OpenVDS+ Version: 3.3.0,
Comparative Scenario:
- SEGY with Original CRS
- SEGY with WGS84 CRS
- VDS from HW with Original CRS
- VDS from HW with WGS84 CRS
- VDS from OpenVDS+ with WGS84 CRS (only option available)
First Scenario - SEGY with Original CRS
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.
In this test the team uploaded all the segy files, listed in the "Data used" topic, under the Original CRS (also informed with the data list) and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.
Result: All the data are at the expected spatial position.
Second Scenario - SEGY with WGS84 CRS
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.
In this test the team uploaded all the segy files, listed in the "Data used" topic, under the CRS WGS84 and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.
Result: All the data are at the expected spatial position.
Third Scenario - VDS from HW with Original CRS
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.
In this test the team converted to vds, using Headwave, all the segy files, listed in the "Data used" topic, under the Original CRS (also informed with the data list) and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.
Result: All the data are at the expected spatial position.
Fourth Scenario - VDS from HW with WGS84 CRS
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.
In this test the team converted to vds, using Headwave, all the segy files, listed in the "Data used" topic, under the CRS WGS84 and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.
Result: All the data are at the expected spatial position.
Fifth Scenario - VDS from OpenVDS+ with WGS84 CRS (only option available)
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.
In this test the team converted to vds, using OpenVDS+, all the segy files, listed in the "Data used" topic, under the CRS WGS84 and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.
Result: The file R0300_3D_AM_URUCARA that is located under a different zone from the project (21S) is wrongly spatially positioned (Should be at the same position that the red polygon is).
We are available for any additional information needed.
Regards,
Juliana