topic Re: Problems with SSDM database in File Geodatabase API Questions

Problems with SSDM database

__11 — Thu, 22 Jan 2015 05:16:45 GMT

I'm having a problem adding rows to an SSDM database. To reproduce the problem:

Download the SSDM package (OGP_SSDM_V1_2014.zip) from http://www.iogp.org/Geomatics#2521682-seabed-survey-data-model

The Geodatabase is in OGP_SSDM_V1_2014\3_Data_Model_Template\3a_GIS\OGP_SSDM_Template_WGS84_V1_20131223_92.gdb - it has tables, but no rows in the tables.

It's a version 9 database, and File Geodatabase API v1.3 won't open it, so open it with Esri ArcCatalog (I used 10.0) and upgrade it to 10. Attached is OGP_SSDM_Template_WGS84_V1_20131223_92_updated_to_10.gdb.zip -the database after I updated it to 10.

Now use the attached SSDM_Test.cpp to open the database and add a row to one table. The API reports no errors.

Load the database into ArcCatalog and try to preview the added data (in Survey_Sounding_Grid) - Most of the time, ArcCatalog reports "Open Failed. Error opening feature class" (Sometimes it has worked, but mostly not. Sometimes ArcCatalog crashes when opening the table.)

Inserting an empty row instead (change #if 0 to #if 1 in the code) has the same effect.

The same code works without any problems when run on the previous version of the SSDM database (attached as OGP_SSDM_Template_WGS84_V1_20110326_92.gdb.zip).

Any ideas what the problem with OGP_SSDM_Template_WGS84_V1_20131223_92 is?

Re: Problems with SSDM database

LanceShipman — Thu, 19 Feb 2015 20:31:41 GMT

One copy of survey_sounding_grid has a grid size of 0, the other has a grid size of 1000. Since the feature class is empty, it should be zero.

On one copy of survey_sounding_grid the SYMBOL_CODE includes the Symbology_point_survey domain. The other has no domain assigned.

Re: Problems with SSDM database

__11 — Thu, 26 Feb 2015 09:19:38 GMT

Using ArcCatalog, in OGP_SSDM_Template_WGS84_V1_20131223_92_updated_to_10.gdb I changed Survey_Sounding_Grid to:

Properties, Indexes, Grid 1 = 0
Properties, Fields, SYMBOLOGY_CODE, Domain = (nothing)

so now they match OGP_SSDM_Template_WGS84_V1_20110326_92.gdb, but it does not fix the problem.

Any other ideas?

Can you (or anyone else) reproduce the problem?

Re: Problems with SSDM database

__11 — Tue, 24 Mar 2015 02:18:26 GMT

A quick test indicates the same problem applies with FileGDB_API v1.4

Re: Problems with SSDM database

__11 — Thu, 16 Apr 2015 07:03:26 GMT

Further investigation reveals that if one imports the XML provided as part of SSDM_V1_2014 (OGP_SSDM_V1_2014\3_Data_Model_Template\3a_GIS\ArcCatalog_ESRI_XML-OGP_SSDM_Template_WGS84_V1_20131223.xml) with ArcCatalog v10 the resultant database works OK with FileGDB_API.