Opened 7 years ago

Last modified 5 years ago

#3286 new enhancement

Add Line_height as a valid attribute in v.to.db — at Initial Version

Reported by: geografik Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: Database Version: 7.2.0
Keywords: Line_height, v.in.db, kml Cc:
CPU: All Platform: All

Description

Imported kml files that include elevation data are structured generally as shown below in GRASS (this is an example of a contour line):

east, north: -79.7630759471, 39.0874586371 DBT@corH:

Type: Line Id: 885 Length: 275.746 Line_height: 698.602997 Layer: 1 Category: 885 Driver: sqlite Database: /Users/sesMacBook/grassdata/KML/corH/sqlite/sqlite.db Table: DBT Key_column: cat Attributes:

cat: 885 cat_: 885 tessellate: -1 extrude: -1 visibility: -1

Elevation data is maintained in the Line_height field which is not a recognized attribute, and therefor precludes any further use of these data in GRASS - beyond simple display and labling. 3D analysis, for example, is not possible. The suggested improvement to v.to.db would add Line_height to the list of attributes considered in this module so that the elevation data could become part of the recognized feature attributes and be useful in other modules.

Change History (0)

Note: See TracTickets for help on using tickets.