Closed nesdolya closed 1 month ago
Changes for this issues have been made in the PR https://github.com/cat-cfs/twobilliontoolkit/pull/49
A correctly formatted project number will just be given the generic 0000 XXX - 000 project number if it is not found in the database (or datasource) so that is does not throw foreign key constraints
A spatial layer is added to the GDB with the incorrect project spatial id before the foreign key contraint is triggered. Please modify this so that these layers are assigned the 0000 XXX - 000 project number and appropriate project spatial id to be fixed by records reviser. In this case the warning is sufficient (no error entry needs to be added to the log file). Examples are: 2023 CFP - 430 and 2022 GNT - 717. Example dataset is located here: \vic-fas1\projects_a\2BT\01_Data\2BT_program_data\2023\RawData\00_Unprocessed_Spatial\GCDocs_Sept102024_Fixes