FGDB export failing with merged MgcpCroppedPoiRoadBuilding & PortAuPrinceOsmPoiRoadBuilding

[mikejeffe]

Conflate PortAuPrinceOsmPoiRoadBuilding and MgcpCroppedPoiRoadBuilding raw osm data (osm layer1, mgcp layer2). You should get 1 review. Export the merged output to either TDS6.1 or MGCP as a FGDB file and it will fail with the output below.

2016-01-15 14:30:19,680 ERROR JobExecutionManager:225 - Job with ID: ex_2e3e9b2f 3c0a4b9f8be5f9e798943616 failed: Failed to execute.Error running osm2ogr: Error creating feature - OGR Error Code: (6) Feature causing error: ([100]{(ADR, No Information), (AOO, -999999), (ARA, -9999 99), (ATB, -999999), (AWP, -999999), (BEN, noInformation), (BNF, -999999), (BSU, ), (CAA, -999999), (CCN, No Information), (CDR, No Information), (COS, ), (CRM, ), (ETY, ), (FCSUBTYPE, 100083), (FFN, 999), (FFN2, -999999), (FFN3, -999999), (F_CODE, AL013), (GUG, ), (HEI, ), (HGT, -999999), (HST, -999999), (HST2, -99999 9), (HST3, -999999), (LMC, -999999), (LZN, -999999), (MFB, -999999), (MUB, -9999 99), (OTH, (FFN:tyres) (ZI004_RCG:osm)), (PCF, -999999), (PYC, ), (PYM, ), (RLE , -999999), (SAX_RS1, No Information), (SAX_RS2, No Information), (SAX_RS3, noIn formation), (SAX_RS4, noInformation), (SAX_RS5, No Information), (SAX_RS6, noInf ormation), (SAX_RS8, No Information), (SAX_RS9, No Information), (SAX_RX1, noInf ormation), (SAX_RX2, noInformation), (SAX_RX5, noInformation), (SAX_RX6, noInfor mation), (SAX_RX7, noInformation), (SAX_RX8, noInformation), (SAX_RX9, No Inform ation), (SAX_RY0, No Information), (SAX_RY1, noInformation), (SAX_RY2, noInforma tion), (SPT, ), (SRL, ), (SSR, -999999), (SSR2, -999999), (SSR3, -999999), (TEL, ), (TOS, ), (TTC, ), (TTC2, ), (TTC3, ), (UFI, ba1e0e94-01ce-482e-9f1b-f7ec50c4 5cce), (VCM, -999999), (VCM2, -999999), (VCM3, -999999), (VOI, noInformation), ( WID, -999999), (ZI001_SDP, No Information), (ZI001_SDV, 2014-08-30T18:10:18.000Z ), (ZI001_SPS, -999999), (ZI001_SRT, noInformation), (ZI001_VSC, noInformation), (ZI001_VSD, noInformation), (ZI001_VSN, No Information), (ZI004_RCG, other), (Z I005_FNA, 4 x 4), (ZI005_NFN, No Information), (ZI006_MEM, No Information), (ZI0 14_PBY, -999999), (ZI014_PBY2, -999999), (ZI014_PBY3, -999999), (ZI014_PPO, -999 999), (ZI014_PPO2, -999999), (ZI014_PPO3, -999999), (ZI014_PRW, -999999), (ZI014 _PRW2, -999999), (ZI014_PRW3, -999999), (ZI018_WIT, -999999), (ZI020_GE4, noInfo rmation), (ZI026_CTUC, 5), (ZI026_CTUL, -999999), (ZI026CTUU, -999999), (ZI037 REL, -999999), (ZI037_RFA, -999999), (ZSAX_RS0, noInformation), (ZSAX_RX0, noInf ormation), (ZSAX_RX3, noInformation), (ZSAX_RX4, noInformation), (ZVH, -999999)} ) make: *\ [step1] Error 255

2016-01-15 14:30:19,685 ERROR JobResource:494 - Failed to execute.Error running osm2ogr: Error creating feature - OGR Error Code: (6) Feature causing error: ([100]{(ADR, No Information), (AOO, -999999), (ARA, -9999 99), (ATB, -999999), (AWP, -999999), (BEN, noInformation), (BNF, -999999), (BSU, ), (CAA, -999999), (CCN, No Information), (CDR, No Information), (COS, ), (CRM, ), (ETY, ), (FCSUBTYPE, 100083), (FFN, 999), (FFN2, -999999), (FFN3, -999999), (F_CODE, AL013), (GUG, ), (HEI, ), (HGT, -999999), (HST, -999999), (HST2, -99999 9), (HST3, -999999), (LMC, -999999), (LZN, -999999), (MFB, -999999), (MUB, -9999 99), (OTH, (FFN:tyres) (ZI004_RCG:osm)), (PCF, -999999), (PYC, ), (PYM, ), (RLE , -999999), (SAX_RS1, No Information), (SAX_RS2, No Information), (SAX_RS3, noIn formation), (SAX_RS4, noInformation), (SAX_RS5, No Information), (SAX_RS6, noInf ormation), (SAX_RS8, No Information), (SAX_RS9, No Information), (SAX_RX1, noInf ormation), (SAX_RX2, noInformation), (SAX_RX5, noInformation), (SAX_RX6, noInfor mation), (SAX_RX7, noInformation), (SAX_RX8, noInformation), (SAX_RX9, No Inform ation), (SAX_RY0, No Information), (SAX_RY1, noInformation), (SAX_RY2, noInforma tion), (SPT, ), (SRL, ), (SSR, -999999), (SSR2, -999999), (SSR3, -999999), (TEL, ), (TOS, ), (TTC, ), (TTC2, ), (TTC3, ), (UFI, ba1e0e94-01ce-482e-9f1b-f7ec50c4 5cce), (VCM, -999999), (VCM2, -999999), (VCM3, -999999), (VOI, noInformation), ( WID, -999999), (ZI001_SDP, No Information), (ZI001_SDV, 2014-08-30T18:10:18.000Z ), (ZI001_SPS, -999999), (ZI001_SRT, noInformation), (ZI001_VSC, noInformation), (ZI001_VSD, noInformation), (ZI001_VSN, No Information), (ZI004_RCG, other), (Z I005_FNA, 4 x 4), (ZI005_NFN, No Information), (ZI006_MEM, No Information), (ZI0 14_PBY, -999999), (ZI014_PBY2, -999999), (ZI014_PBY3, -999999), (ZI014_PPO, -999 999), (ZI014_PPO2, -999999), (ZI014_PPO3, -999999), (ZI014_PRW, -999999), (ZI014 _PRW2, -999999), (ZI014_PRW3, -999999), (ZI018_WIT, -999999), (ZI020_GE4, noInfo rmation), (ZI026_CTUC, 5), (ZI026_CTUL, -999999), (ZI026CTUU, -999999), (ZI037 REL, -999999), (ZI037_RFA, -999999), (ZSAX_RS0, noInformation), (ZSAX_RX0, noInf ormation), (ZSAX_RX3, noInformation), (ZSAX_RX4, noInformation), (ZVH, -999999)} ) make: *\ [step1] Error 255

[mikejeffe]

Interestingly enough, the input dataset PortAuPrinceOsmPoiRoadBuilding also fails when you export it to TDS61 so I suspect the error is introduced with that dataset.

[mattjdnv]

I have found the problem and it is with the Source Date Time attribute.

The OSM file has the date & time as an Javascript produced "ISO" standard string. E.g. "2012-12-30T21:40:47.000Z"

Unfortunately, the TDSv61 spec uses the same spec but defines it a bit differently:

"Formatted in accordance with ISO 8601:2000, 5.4.1, Combinations of date and time of day - Complete representation - Extended format, a calendar date and time representation, as a single data element comprising up to twenty characters, where [YYYY] represents a calendar year, [MM] the ordinal number of a calendar month within the calendar year, [DD] the ordinal number of a day within the calendar month, [hh] the ordinal number of an hour within the calendar day, [mm] the ordinal number of a minute within the hour, [ss] the ordinal number of a second within the minute, and an optional 'Z' when the time is according to Coordinated Universal Time (UTC), as 'YYYY-MM-DDThh:mm:ssZ' (for example: '1985-04-12T11:45:20Z' for 11 hours, 45 minutes and 20 seconds UTC on 12 April 1985). Representations with reduced precision may be used in accordance with 5.4.2 (for example: '1985-04-12' for 12 April 1985). Representations consistently using basic format (eliminating the hyphen '-' and the colon ':') may be used in accordance with 5.4.1 (for example: '19850412T114520Z')."

This means that the Javascript version is longer than the 20 characters that the TDS (and MGCP) spec expects due to having milliseconds.

2012-12-30T21:40:47.000Z <- OSM: 1985-04-12T11:45:20Z <- TDS:

I will modify the TDS & MGCP translators to chop off the milliseconds from the "source:datetime" tag on export.

[mikejeffe]

Tested FGDB export with TDS61 and MGCP. Looks good!