Opened 2 months ago

Closed 2 months ago

Last modified 2 months 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 2 months ago.
Sample Dataset

Download all attachments as: .zip

Change History (5)

Changed 2 months ago by plesk

Attachment: waterwaymgtunit.geojson added

Sample Dataset

comment:1 Changed 2 months ago by Even Rouault

Resolution: fixed
Status: newclosed

In 39910:

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

comment:2 Changed 2 months ago by Even Rouault

In 39911:

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

comment:3 Changed 2 months ago by Even Rouault

In 39912:

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

comment:4 Changed 2 months ago by Even Rouault

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