diff options
| author | Arun Isaac | 2026-08-27 14:37:27 +0100 |
|---|---|---|
| committer | Arun Isaac | 2026-08-27 14:37:27 +0100 |
| commit | b3d924c02b8f0f7921f768f747b7f6297e379fa2 (patch) | |
| tree | 37cc7c7b6c2fd211a10a23718bbadbdb08757895 | |
| parent | 7a88ec86e728936920fc0ffdd4e0b0df4d7ab1f1 (diff) | |
| download | domagi-b3d924c02b8f0f7921f768f747b7f6297e379fa2.tar.gz domagi-b3d924c02b8f0f7921f768f747b7f6297e379fa2.tar.lz domagi-b3d924c02b8f0f7921f768f747b7f6297e379fa2.zip | |
Order path_segment by the output coordinates, not the input.
In domagi extract, order path_segment by the output start and end coordinates, not the input start and end coordinates. We achieve this by renaming the output coordinates "start" and "end" respectively.
| -rw-r--r-- | domagi/domagi.py | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/domagi/domagi.py b/domagi/domagi.py index eda2981..5174264 100644 --- a/domagi/domagi.py +++ b/domagi/domagi.py @@ -268,7 +268,11 @@ def extract(con, outfile, segment_name, path_range, steps, threads, progress): INSERT INTO subset_db.path_segment -- There are no gaps in the path segments. So, it's enough to subtract -- first_start from the path segment coordinates. - SELECT path_segment.path_id, segment_id, segment_orientation, start-first_start, "end"-first_start + SELECT path_segment.path_id, + segment_id, + segment_orientation, + start-first_start AS start, + "end"-first_start AS end FROM selected_segment INNER JOIN path_segment ON path_segment.segment_id=selected_segment.id INNER JOIN path_first_start ON path_first_start.path_id=path_segment.path_id |
