-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GFT tweaks for 24v3 draft 1 review #1196
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,3 +3,4 @@ SELECT | |
variable_id, | ||
lot_geom | ||
FROM {{ ref("int_spatial__cats_permits") }} | ||
WHERE lot_geom IS NOT NULL |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,3 +3,4 @@ SELECT | |
variable_id, | ||
lot_geom | ||
FROM {{ ref("int_spatial__state_facility") }} | ||
WHERE lot_geom IS NOT NULL |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,3 +3,4 @@ SELECT | |
variable_id, | ||
lot_geom | ||
FROM {{ ref("int_spatial__title_v_permit") }} | ||
WHERE lot_geom IS NOT NULL |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,3 +3,4 @@ SELECT | |
variable_id, | ||
lot_geom | ||
FROM {{ ref("int_spatial__historic_resources_adj") }} | ||
WHERE lot_geom IS NOT NULL |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,3 +3,4 @@ SELECT | |
variable_id, | ||
lot_geom | ||
FROM {{ ref("int_spatial__historic_resources") }} | ||
WHERE lot_geom IS NOT NULL |
11 changes: 9 additions & 2 deletions
11
products/green_fast_track/models/product/source/shadow/source__shadow_open_spaces_polys.sql
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,13 @@ | ||
SELECT | ||
variable_type, | ||
variable_id, | ||
raw_geom | ||
raw_geom AS geom | ||
FROM {{ ref("int_spatial__shadow_open_spaces") }} | ||
WHERE ST_GEOMETRYTYPE(raw_geom) = 'ST_MultiPolygon' | ||
WHERE ST_GEOMETRYTYPE(raw_geom) = 'ST_MultiPolygon' AND lot_geom IS NULL | ||
UNION ALL | ||
SELECT | ||
variable_type, | ||
variable_id, | ||
lot_geom AS geom | ||
FROM {{ ref("int_spatial__shadow_open_spaces") }} | ||
WHERE lot_geom IS NOT NULL |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thoughts on just passing along a
--product-label
CLI option?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something like that would make sense, though then we'd need to have this sort of logic in the
repeat
gha - still need to refer to both formattings in our code at the momentThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, I guess I'm angling for a way to avoid hardcoding these product overrides, which feels like it's going in the wrong direction. I'm fine if we just want to punt though until we have a strong feeling about where's best for this type of thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. Yeah I feel like a CLI option isn't really great either, in that it still adds some unneeded complexity. But it's 100% a lesser evil than what's in this PR
Maybe we should just have some sort of minimal
ProductPaths
object? And then dcpy can rely on pyproject.toml (or.dcpy
file, etc) that defines the path to product folder, DO folder name, db build name, etc. OR for each product, we have a standard spot to look, (i.e. the product folder) and store the additional metadata there. This seems like this could belong in a recipe actually. Though then you would need the recipe to run an upload step.Long way of saying I think we should punt the issue. I can make an issue for this