Closed jbranigan closed 7 years ago
@jbranigan thanks; the collapsing of points into the lines seems to work nicely in terms of simplifying the data structure.
I'm wondering if it's possible to select a list of cues ordered by distance and direction using this data structure?
Regarding the topology sql I saw your were converting the multi-linestrings to linestrings. I'm not sure we can assume that the route data contains simple geometries which I believe is a requirement for the "regular" linestring geometry?
More needs to be done to select a list of cues ordered by distance and direction. Topology fixes would be best, but there may be ID tricks we can fall back on. Not sure what's best yet.
Thanks @jbranigan, I think it's good to have documentation of what has been attempted with SQL / PostGIS using the raw ECG data from Wiki Mapping.
I tried fixing the topology in PostGIS, but ran into some trouble there.
Then, I tried collapsing the point cue data onto the lines, in an attempt to build the structure that Dan mentioned on the phone earlier this week. I made a simple map that can be inspected - there are definitely still issues, but many of them stem from errors already present in the point cue dataset (mixed up north/south cues).
Map: https://jbranigan.carto.com/builder/203e79d6-374f-11e7-906f-0ecd1babdde5/embed