-
Notifications
You must be signed in to change notification settings - Fork 6
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
Feat project creation #71
Conversation
Always good db practice to at |
|
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.
Looks good 👍
Minor comment: to save listing this huge list of variables to inject, could the ones from project_metadata
be inserted simply using **project_metadata
?
They will be used as keyword args, so this will work where the variable names match.
It would also make the code more resilient to change / breakage if variables change in future.
values={ | ||
"id": _id, | ||
"author_id": author_id, | ||
"name": project_metadata.name, |
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.
Is would work here for example and all vars that match like this
Description
This PR introduces several enhancements and fixes to the project schema:
New Features:
deadline
column to the projects table to track submission deadlines.no_fly_zones
input to supportPolygon
,MultiPolygon
, and other geometry types, ensuring flexible and accurate representation of restricted areas.Additional Schema Fields: Introduced the following new fields to the project schema:
Utility Functions:
multipolygon_to_polygon
utility function to handle and convert multipolygon geometries withinno_fly_zones
.