-
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
conflate_model
and gpkg_from_ras
should take model_name
parameter rather than inferring it
#186
Comments
Let's adjsut the payload above to include a {
"source_model_directory": "Z:\\collections\\ble_12040103_EastForkSanJacinto\\ROCKY_BRANCH",
"model_name": "ROCKY_BRANCH",
"source_network": {
"file_name": "Z:\\reference_data\\nwm_flowlines_with_bbox.parquet",
"version": "2.1",
"type": "nwm_hydrofabric"
}
}
Inference will be updated to use: f"{source_model_directory} \ {model_name}.prj" |
When calling ras_to_gpkg we don't yet know what the model_name is. We find the model name by first grabbing all .prj files then assessing if prj file is the RAS project file. For conflate model, the model_name has been added as a required arg. Note that it is the path to the source model geopackage that we infer with the souce_model_directory and model_name; i.e., not the .prj file. |
@mdeshotel I didn't understand the last sentence, can you describe it with an example of API/Schema changes before and after? |
Seth's comment above was saying we infer the f"{source_model_directory} \ {model_name}.prj" My comment was just pointing out that we don't infer the f"{source_model_directory} \ {model_name}.gpkg" |
When submitting jobs for these processes, there is no way to provide a
model_name
. It is inferred from the parent folder name. This is wrong becausemodel_name
could be different. For example ifmodel_stac_id
is 'ROCKY_BRANCH' and themodel_name
is 'ROCKY BRANCH' then the following will fail as the GPKG name will be 'ROCKY BRANCH.gpkg'.The text was updated successfully, but these errors were encountered: