#4247 closed defect (fixed)
The BSB driver does not handle correctly the European 1950 datum
Reported by: | jcrepetto | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | GDAL_Raster | Version: | svn-trunk |
Severity: | normal | Keywords: | bsb ED50 |
Cc: |
Description
I have some BSB/KAP files containing these metadata :
BSB_KNP=SC=15000,GD=European 1950 ,PR=MERCATOR,PP=0.000000,PI=UNKNOWN,SP=UNKNOWN,SK=0,UN=METERS,SD=LOWEST LOW WATER,DX=1.50,DY=1.50
But gdalinfo reports that the coordinate system is WGS84.
The attached patch fixes the problem.
Attachments (1)
Change History (6)
comment:1 by , 12 years ago
by , 12 years ago
Attachment: | bsb_ED50.patch.gz added |
---|
Patch to support the ED50 datum in the BSB driver
follow-up: 3 comment:2 by , 12 years ago
I have updated the patch, now georefencing is correct.
Plaese commit the patch.
comment:4 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The patch looked good. I have just renamed the pszDatum variable to pszGEOGCS to be really explicit on its content. The autotest suite is a bit light on datum&projection support in BSB. I've tested quicly with 2 NOAA datasets mentionned in http://trac.osgeo.org/gdal/ticket/3409#comment:11 that it doesn't cause apparent regressions in the WGS84 case.
r23113 /trunk/gdal/frmts/bsb/bsbdataset.cpp: BSB: Parse the GD keyword in BSB_KNP to recognize European 1950 datum (#4247, patch by jcrepetto)
r23114 /branches/1.8/gdal/frmts/bsb/bsbdataset.cpp: BSB: Parse the GD keyword in BSB_KNP to recognize European 1950 datum (#4247, patch by jcrepetto)
I have found another problem : The BSB driver considers that the GCP coordinates are always in WGS84 :
I'll try to update the patch to fix this problem.