LION - SAF mismatches in 26a #2257
Description
There were two issues from before that Rodrigo wanted to punt to 26a. These need to be resolved, but also we need to research if there are other saf mismatches in qa__lion_dat_individual_diffs for 26a so we can send all issues to GR at once (and at that point, make an ADO ticket with a summary). In both of these cases, I believe our pipeline is correct.
Shoreline segment 0241972
- In dev, we assign 'N'. Prod has blank
- This segment has a protosegment
- In commonplace, there is a type 'N' record with segmentid 0241972
- However, in production, neither geometry-modeled segment or protosegment with segment id 0241972 has a (non-blank) special address flag. I'm pretty sure the shoreline segment should have it assigned
Centerline protosegment 0174704
- globalid '{96B37DB0-C48A-4AC5-A2AE-E8A411710BFE}'
- In dev, blank. Prod has 'B'
- Same boro as geometry-modeled segment. Altsegdata_type is 'R'
- In prod, both geometry-modeled segment and this protosegment have special address flag 'B'.
- Docs say in general, only one of geometry-modeled segment and protosegment should get the SAF record assigned, and in this case it seems it should be the geometry-modeled one. Certainly not both like the prod etl is spitting out