Difference between revisions of "Main Page/Research/MSB/vertex-level tracking"
From phurvitz
Phil Hurvitz (talk | contribs) |
Phil Hurvitz (talk | contribs) |
||
Line 11: | Line 11: | ||
## Write out PostGIS code for importing XYZ line data | ## Write out PostGIS code for importing XYZ line data | ||
##: Relies on the LINESTRING geometry with 3 dimensions | ##: Relies on the LINESTRING geometry with 3 dimensions | ||
+ | ## Create VIEWs for stationary vs moving lines | ||
## Dump from PostGIS using pgsql2shp | ## Dump from PostGIS using pgsql2shp | ||
##: Maintains XYZM coordinates on vertices | ##: Maintains XYZM coordinates on vertices |
Revision as of 18:07, 24 March 2009
Vertex-level tracking of edits from MSB data
- GIS typically does not store vertex-level attributes.
- The XYZ coordinates in 2.5D line data sets may be used for uniquely identifying vertices
- Download data from UBI (Jonathan's server space)
- Perform pre-processing
- Includes concatenation of bouts
- Uniquely identify records
- dat$id <- seq(1, nrow(dat)) (R)
- Generate lines (using sub-bout parser)
- Write out PostGIS code for importing XYZ line data
- Relies on the LINESTRING geometry with 3 dimensions
- Create VIEWs for stationary vs moving lines
- Dump from PostGIS using pgsql2shp
- Maintains XYZM coordinates on vertices
- Write out PostGIS code for importing XYZ line data
- Edit in ArcMap (Use 3rd-party vertex mass editor [ET Tools from ian-ko.com])
- Deleting individual vertices drops them and does not re-order, i.e., maintains the Z coordinate on each XY vertex. (My tests of ArcView 3 showed failure in this regard).
- Import shapefile as PostGIS table
- Maintains XYZ coordinates
- Dump from PostGIS; this example shows how to dump each record as an EWKT format (XYZ text)
- copy (select asewkt(line_waspn) from s56_coords) to '/tmp/coords.txt';
- Read into R