[GRASS-user] error with imported kml file

Stuart Edwards sedwards2 at cinci.rr.com
Mon Feb 13 05:13:20 PST 2017


> On Feb 12, 2017, at 8:13 PM, Anna Petrášová <kratochanna at gmail.com> wrote:
> 
> On Sun, Feb 12, 2017 at 5:42 PM, Stuart Edwards <sedwards2 at cinci.rr.com> wrote:
>> Anna
>> 
>> Thanks for the quick response.
>> 
>> Here's the output from v.what -j for the query in the screenshot:
>> 
>> (Sun Feb 12 17:14:20 2017)
>> v.what -j map=DBT___Waste___3D at corH coordinates=-79:45:47.0628,
>> 39:05:14.8848
>> {"Coordinates": {"East": "79W", "North": "39N"},
>> "Maps":
>> [{"Map": "DBT___Waste___3D",
>> "Mapset": "corH"}
>> ]}
>> (Sun Feb 12 17:14:21 2017) Command finished (0 sec)
>> 
>> Output from v.db.select (same query):
>> 
>> (Sun Feb 12 17:19:57 2017)
>> v.db.select --overwrite map=DBT___Waste___3D at corH
>> file=/Users/sesMacBook/Baker/CorridorH/WasteDisposal/vdbselect1
>> (Sun Feb 12 17:19:57 2017) Command finished (0 sec)
>> 
>> 
> 
> Looking at the attachment, the problem is definitely in multiline
> strings in your 'description' column. I suggest to create a ticket for
> this. For now, you might want to consider deleting that column if it
> is not needed, to be able to use the vector.
> 
> Anna

Deleting the description column eliminated the error and the file performs as expected 

thanks!

Stu
> 
>> 
>> Another kml contour file (from a different source) displayed in the same
>> mapset produces better results from a query:
>> 
>> east, north: -79.7618228288, 39.0853199854
>> DESIGN_MAJOR_CONTOURS at corH:
>> Type: Line
>> Id: 5007
>> Length: 106.682658
>> Line_height: 691.997
>> Layer: 1
>> Category: 1
>> Driver: sqlite
>> Database: /Users/sesMacBook/grassdata/KML/corH/sqlite/sqlite.db
>> Table: DESIGN_MAJOR_CONTOURS
>> Key_column: cat
>> Attributes:
>>   cat: 1
>>   Name: Style2
>>   altitudeMode: absolute
>>   tessellate: -1
>>   extrude: -1
>>   visibility: -1
>> 
>> However, the v.what -j command produces a similar result to the one above:
>> 
>> (Sun Feb 12 17:29:12 2017)
>> v.what -j map=DESIGN_MAJOR_CONTOURS at corH coordinates=-79.7618228288,
>> 39.0853199854
>> {"Coordinates": {"East": "79:45:42.562184W", "North": "39:05:07.151947N"},
>> "Maps":
>> [{"Map": "DESIGN_MAJOR_CONTOURS",
>> "Mapset": "corH"}
>> ]}
>> (Sun Feb 12 17:29:12 2017) Command finished (0 sec)
>> 
>> and the v.db.select output is much shorter:
>> 
>> (Sun Feb 12 17:35:44 2017)
>> v.db.select --overwrite map=DESIGN_MAJOR_CONTOURS at corH
>> file=/Users/sesMacBook/Baker/CorridorH/WasteDisposal/vdbselect2
>> (Sun Feb 12 17:35:44 2017) Command finished (0 sec)
>> 
>> produces:
>> 
>> cat|Name|description|timestamp|begin|end|altitudeMode|tessellate|extrude|visibility|drawOrder|icon
>> 1|Style2|||||absolute|-1|-1|-1||
>> 
>> I can send you the two kml files if that would be helpful.
>> 
>> thx
>> 
>> Stu
>> 
>> On Feb 12, 2017, at 3:44 PM, Anna Petrášová <kratochanna at gmail.com> wrote:
>> 
>> Hi,
>> 
>> On Sun, Feb 12, 2017 at 10:36 AM, Stuart Edwards <sedwards2 at cinci.rr.com>
>> wrote:
>>> 
>>> Hi -
>>> 
>>> 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
>>> v.to.rast 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.
>>> 
>>> Any assistance or advice much appreciated.
>>> 
>> please post (or attach) the text outputs of v.what with -j flag and
>> v.db.select, which are the backend commands behind the GUI dialogs. That
>> helps us to analyze it.
>> 
>> Anna
>> 
>>> Stu
>>> 
>>> <Screen Shot 2017-02-12 at 10.29.33 AM.png>
>>> 
>>> _______________________________________________
>>> grass-user mailing list
>>> grass-user at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-user
>> 
>> 
>> 
>> 



More information about the grass-user mailing list