Changes between Initial Version and Version 1 of Ticket #5691, comment 1


Ignore:
Timestamp:
03/27/24 17:23:16 (9 months ago)
Author:
robe

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #5691, comment 1

    initial v1  
    7373Since I am using the existing tiger edge ids, I also need to reset the sequence id of the topology, which it appears I am not doing, so future possible adds don't conflict with that's been added.
    7474
    75 Although it looks like I'm literally taking what tiger is giving me cause in the tiger.edges structure I am mapping to postgis topology edge_data structure as follows
     75I'm literally taking what tiger is giving me cause in the tiger.edges structure I am mapping to postgis topology edge_data structure as follows, but I think the next_left_edge, next_right_edge I had to derive cause tiger data doesn't have those so I'm probably doing that wrong
    7676
    7777
    … …  
    7979 , t.tnidf As start_node, t.tnidt As end_node, t.tfidl As left_face
    8080                        , t.tfidr As right_face, tl.tlid AS next_left_edge,  tr.tlid As next_right_edge
     81
     82FROM te AS t LEFT JOIN te As tl
     83                                                                ON (t.tnidf = tl.tnidt AND t.tfidl = tl.tfidl)
     84                        LEFT JOIN te As tr ON (t.tnidt = tr.tnidf AND t.tfidr = tr.tfidr)
    8185}}}
    8286
    8387
    84 I am doing some extra math though with negating things and closing stuff up if it doesn't match, so the issue might be there.