Opened 7 years ago

Last modified 5 years ago

#3284 new defect

Imported kml file fails to generate JSON compliant output to v.what

Reported by: geografik Owned by: grass-dev@…
Priority: normal Milestone: 7.4.5
Component: Database Version: 7.2.0
Keywords: v.what, kml, 'valid JSON format' Cc:
CPU: OSX/Intel Platform: MacOSX


I have imported a kml file that contains contours of a feature of interest. Functionally an x,y,z data set. It displays correctly in GRASS. When queried to determine the value of z, the attached error is given that indicates a lack of conformance with JSON formatting. The values of z are given for the feature in the error message but additional processing such as does not work. GRASS is able to label the contours correctly. Using the attribute table manager is not much help - it produces an error that indicates 'Inconsistent number of columns in table'.

I see that there is a bug report (3133) that reflects the same problem but has been fixed in 7.0.5 - I'm getting the 'same' error in 7.3.svn. (on OS X 10.10.5)

The error message is too long to fit on the monitor - and is not scrollable, so the full content is not visible.

Anna Petrášová diagnosed the problem as multiline strings in the 'description' column and suggested deleting it. That resolved the problem but is not a complete solution where that column is needed.

Attachments (1)

Screen Shot 2017-02-12 at 9.11.07 AM.png (133.6 KB ) - added by geografik 7 years ago.
screenshot of error output

Download all attachments as: .zip

Change History (9)

by geografik, 7 years ago

screenshot of error output

comment:1 by neteler, 7 years ago

The same happens with the Sentinel-2 tile index KML: the quotes seem not to be properly escaped.


comment:2 by martinl, 7 years ago


comment:3 by neteler, 7 years ago


Ticket retargeted after milestone closed

comment:4 by martinl, 6 years ago

Milestone: 7.2.3

Ticket retargeted after milestone closed

comment:5 by martinl, 6 years ago

Milestone: 7.2.4

comment:6 by neteler, 5 years ago


Did you try lately?

comment:7 by neteler, 5 years ago


comment:8 by mmetz, 5 years ago

Should be fixed in trunk r74048 and relbr r74448.

Note: See TracTickets for help on using tickets.