Opened 12 years ago

Closed 12 years ago

#2125 closed defect (fixed)

Unexpected quoting in GMT vector output.

Reported by: warmerdam Owned by: warmerdam
Priority: normal Milestone: 1.5.1
Component: OGR_SF Version: 1.5.0 betas/RCs
Severity: normal Keywords: gmt
Cc:

Description (last modified by warmerdam)

I've just installed GDAL v1.5 & am working through some GMT files generated by ogr2ogr (from VMAP0 shapefiles).

I've tweaked the docs to describe the output, which didn't take much. The only bug I've noticed is that ogr2ogr writes the contents of dbf double fields as a quoted text string, with leading whitespace, whereas I expected an unquoted numeric value with no whitespace, as for integer fields.

eg:

# @VGMT1.0 @GPOLYGON
# @R25/176.78868103/-47.1254081726/50
# @NFTCDESC|F_CODEDESC|ID|F_CODE|TILE_ID|FAC_ID|VEGDESC|FTC|VEG
# @Tstring|string|double|string|integer|double|string|integer|integer
# FEATURE_DATA
> >
# @DUnknown|Cropland|"          1"|EA010|1|"          8"|"Dry Crops"|0|1
# @P
138.554763793945312 49.982349395751953
138.544937133789062 49.982349395751953
138.53509521484375 49.982349395751953
138.525253295898438 49.982349395751953
138.525253295898438 49.9921875
...

Change History (2)

comment:1 Changed 12 years ago by warmerdam

Description: modified (diff)
Status: newassigned

Fixed in trunk (r13470) and 1.5 branch (r13471).

comment:2 Changed 12 years ago by warmerdam

Resolution: fixed
Status: assignedclosed

I have prepared a *very* preliminary gmt regression test script (r13472).

Note: See TracTickets for help on using tickets.