|
Problem IC66470
|
Status: Closed |
DB2 SPATIAL EXTENDER SHAPEFILE IMPORT FAILURES |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Two problems have been identified with some shapefiles
1. When using the 'db2se import_shape' or the
db2gse.ST_import_shape_stored procedure, it fails with a message
that the coordinate system definition in the .prj file does not
match the spatial reference system specified for the import
process.
This may occur if the coordinate system definition in the .prj
file is correct but this is followed by additional information
not related to the geographic or projected coordinate system
definition.
This is an example
GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",S
PHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",
0.0],UNIT["Degree",0.0174532925199433]],VERTCS["Unknown
VCS from ArcInfo
Workstation",VDATUM["Unknown"],PARAMETER["Vertical_Shift",0.0],P
ARAMETER["Direction",1.0],UNIT["Meter",1.0]]
In particular, the VERTCS part is not recognized.
All text after the end of the GEOGCS definition should be
ignored.
2. Some shapefiles which have Z coordinates may be rejected with
a "coordinate out of bounds" error message.
This is due to the presence of M values in the shapefile which
have a value less than -1E38 which indicates a "no data" value
and will generally be outside the bounds of the M value in the
spatial reference system definition. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Spatial Extender users *
****************************************************************
* PROBLEM DESCRIPTION: *
* Two problems have been identified with some shapefiles *
* *
* 1. When using the 'db2se import_shape' or the *
* db2gse.ST_import_shape_stored procedure, it fails with a *
* message that the coordinate system definition in the .prj *
* file does not match the spatial reference system specified *
* for the import process. *
* This may occur if the coordinate system definition in the *
* .prj file is correct but this is followed by additional *
* information not related to the geographic or projected *
* coordinate system definition. *
* *
* This is an example *
* GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983"
* VCS from ArcInfo *
* Workstation",VDATUM["Unknown"],PARAMETER["Vertical_Shift",0.0]
* In particular, the VERTCS part is not recognized. *
* *
* All text after the end of the GEOGCS definition should be *
* ignored. *
* *
* 2. Some shapefiles which have Z coordinates may be rejected *
* with a "coordinate out of bounds" error message. *
* This is due to the presence of M values in the shapefile *
* which have a value less than -1E38 which indicates a "no *
* data" value and will generally be outside the bounds of the *
* M value in the spatial reference system definition. *
****************************************************************
* RECOMMENDATION: *
* Apply V9.7 fixpack 2 *
**************************************************************** |
| Local Fix: |
The fix to problem number 1 is to either rename/erase the .prj
file or remove the information following the GEOGCS or PROJCS
definition.
The only solution to problem #2 is to apply the fixpack which
corrects this. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
For problem #1, erase/rename the .prj file or remove the extra
information after the GEOGCS/PROJCS definition |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66825
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.02.2010
23.04.2010
23.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
