None
Content
1. Rule 222: Checks that the values in the Date_approved column in the PlanSpatial layer match the values in the Date_approved column in the ZFPropusa layer.
2. Rule 223: Checks whether the values in the Data_exp column of the PlanSpatial layer match the values in the Data_exp column of the ZFPropusa layer.
3. Rule 224: Checks if the values in the Date_approve column of the SpatialPlan layer match the values in the Date_approve column of the SupplementaryRegulationZone layer.
4. Rule 225: Checks whether the values in the Data_exp column of the PlanSpatial layer match the values in the Data_exp column of the SupplementaryRegulationZone layer.
5. Rule 226: Checks that the time period in the Data_approved and Data_exp columns in the ExistingZFZ layer does not overlap with the time period in the Data_approved and Data_exp columns in the SpacedZFZ layer.
6. Rule 227: Checks whether the time period in the Data_approve and Data_exp columns of the ZFPropusa layer is later than the time period in the Data_approve and Data_exp columns of the ZFExist layer.
7. Added 5 validation rules that check if the information is spelled correctly with diacritics that use comma not sedline.
8. The messages written in the validation report have been updated.
9. Fixed the problems that caused the application to crash during the validation process.
10. For the ExistingIntraVisibleLimit and DefaultIntraVisibleLimit layers, the validation rule has been revised so that the "Revision" field is always of type Date (String format is not supported).
11. For rule no. 102 the format in which the information is displayed in the validation report when errors occur has been revised.
12. The validation button for PATJ documentation has been activated
The validation rules for PATJ check:
- existence and validity of the zip archive;
- zip archive structure;
- existence of pdf and gpkg documents;
- the content of the Geopackage file (layers, related fields and geometry elements).
13. Fixed the issue related to the duplication of validation rules in the report in some scenarios.
14. Fixed an issue related to time fields that allowed to enter information in Date & time format (only Date or String format is supported).
15. Implemented the diacritics check in the layer LocalUrbanismLocalRegulation (field Type_ZF_ZRS).
16. Corrected the rule that checks the allowed values in the TechnicalEdilitaryNetworks layer, for PUZ.
17. Rule 107: has been updated and validates on the Clad_Hmax column the entered information of both string and integer type.
18. Rule 174 (PUZ): has been updated to apply a 10m buffer zone and to check if PlanSpatial complies with the administrative boundary of the UAT.
19. Rules 203-208: updated the formula that checks the area of geometries against the information included in the attribute table.
2. Rule 223: Checks whether the values in the Data_exp column of the PlanSpatial layer match the values in the Data_exp column of the ZFPropusa layer.
3. Rule 224: Checks if the values in the Date_approve column of the SpatialPlan layer match the values in the Date_approve column of the SupplementaryRegulationZone layer.
4. Rule 225: Checks whether the values in the Data_exp column of the PlanSpatial layer match the values in the Data_exp column of the SupplementaryRegulationZone layer.
5. Rule 226: Checks that the time period in the Data_approved and Data_exp columns in the ExistingZFZ layer does not overlap with the time period in the Data_approved and Data_exp columns in the SpacedZFZ layer.
6. Rule 227: Checks whether the time period in the Data_approve and Data_exp columns of the ZFPropusa layer is later than the time period in the Data_approve and Data_exp columns of the ZFExist layer.
7. Added 5 validation rules that check if the information is spelled correctly with diacritics that use comma not sedline.
8. The messages written in the validation report have been updated.
9. Fixed the problems that caused the application to crash during the validation process.
10. For the ExistingIntraVisibleLimit and DefaultIntraVisibleLimit layers, the validation rule has been revised so that the "Revision" field is always of type Date (String format is not supported).
11. For rule no. 102 the format in which the information is displayed in the validation report when errors occur has been revised.
12. The validation button for PATJ documentation has been activated
The validation rules for PATJ check:
- existence and validity of the zip archive;
- zip archive structure;
- existence of pdf and gpkg documents;
- the content of the Geopackage file (layers, related fields and geometry elements).
13. Fixed the issue related to the duplication of validation rules in the report in some scenarios.
14. Fixed an issue related to time fields that allowed to enter information in Date & time format (only Date or String format is supported).
15. Implemented the diacritics check in the layer LocalUrbanismLocalRegulation (field Type_ZF_ZRS).
16. Corrected the rule that checks the allowed values in the TechnicalEdilitaryNetworks layer, for PUZ.
17. Rule 107: has been updated and validates on the Clad_Hmax column the entered information of both string and integer type.
18. Rule 174 (PUZ): has been updated to apply a 10m buffer zone and to check if PlanSpatial complies with the administrative boundary of the UAT.
19. Rules 203-208: updated the formula that checks the area of geometries against the information included in the attribute table.