Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#7014 closed defect (fixed)

GeoJSON Schema Detection Issue

Reported by: plesk Owned by: warmerdam
Priority: low Milestone: 2.1.5
Component: OGR_SF Version: 2.2.0
Severity: normal Keywords: geojson, schema
Cc:

Description

GeoJSON schema detection is not functioning as expected for some fields. I have a dataset with a field “catchment” with values like “11: Terminal Lakes System” or “8: Upper Catchment”. These fields are incorrectly being recognised as dates, when they should be strings. The detection mechanism should be checking for multiple non-date chars and deciding on a field type accordingly.

Something along the lines of if the number of alpha-numeric chars > number of numeric chars then string, else date might be a start.

Attachments (1)

waterwaymgtunit.geojson (1.5 KB ) - added by plesk 7 years ago.
Sample Dataset

Download all attachments as: .zip

Change History (5)

by plesk, 7 years ago

Attachment: waterwaymgtunit.geojson added

Sample Dataset

comment:1 by Even Rouault, 7 years ago

Resolution: fixed
Status: newclosed

In 39910:

OGRParseDate(): avoid false-positive time detection (fixes #7014)

comment:2 by Even Rouault, 7 years ago

In 39911:

OGRParseDate(): avoid false-positive time detection (fixes #7014)

comment:3 by Even Rouault, 7 years ago

In 39912:

OGRParseDate(): avoid false-positive time detection (fixes #7014)

comment:4 by Even Rouault, 7 years ago

Milestone: 2.1.5
Note: See TracTickets for help on using tickets.