ztl_daytime
| completeness | green | All specified fields contain values for the 3 records provided. The dataset is stated to contain 3 records in total, implying it is complete for its defined scope, with no missing entries or attributes within the provided structure. |
| accuracy | green | The data appears to be syntactically correct and well-formed. Values in the 'tipologia' field are short, consistent codes, and 'atto_iniz' references follow a consistent 'YYYY/L/NNNNN' format, suggesting adherence to internal data standards with no obvious inaccuracies. |
| consistency | green | The dataset exhibits strong internal consistency, with uniform data types and formats across all records. The 'atto_iniz' field consistently lists administrative acts using a recognizable pattern, and the 'id' field maintains unique values, ensuring structural integrity. |
| timeliness | red | The latest administrative act referenced in the 'atto_iniz' field dates back to 2019. Considering today's date (2026-10-06), this implies the data has not been updated for approximately 7 years, raising significant concerns about its current relevance and accuracy for dynamic ZTL regulations. |
| uniqueness | green | Each record is uniquely identified by the 'id' field, with no duplicate identifiers observed among the provided data. This ensures that individual ZTL entries can be distinctly referenced within the dataset. |
| lineage | red | There is no information provided regarding the data's origin, generation methods, update frequency, or the specific department responsible for its creation and maintenance. While 'atto_iniz' provides internal references, a clear and comprehensive lineage is missing, hindering understanding of the data's provenance. |
| governance | red | Critical information regarding data governance, such as the designated data owner, established quality control processes, update policies, or contact information for data stewardship, is entirely absent. This lack of transparency makes it difficult to assess accountability and trust in the dataset's management. |
ztl_nighttime
| completeness | green | The dataset, which consists of 5 records, is fully represented in the provided sample. All specified fields (id, tipologia, atto_iniz) are populated for every record, with no missing or null values observed in the sample data. |
| accuracy | green | The Coordinate Reference System (CRS) is EPSG:3003, an appropriate national projection for Italy, and is not a quality concern as per the assessment context. The 'id' field appears to be a unique numeric identifier, and the 'tipologia' field contains single character codes. The 'atto_iniz' field consistently follows a 'YYYY/M/XXXXX' format, often including multiple comma-separated values. No implausible values or obvious inaccuracies are detected in the provided sample. |
| consistency | green | The data exhibits internal consistency in its structure and formatting. The 'id' field is numerical, 'tipologia' uses single characters, and 'atto_iniz' consistently uses a specific string format for administrative acts, including the use of commas to delineate multiple associated acts within a single field. No structural inconsistencies or conflicting data types were found. |
| timeliness | yellow | The 'atto_iniz' field, which likely indicates the initial administrative act, contains years ranging from 2014 to 2019. Given today's date of 2026-10-06, these dates are several years old. For a dynamic resource like ZTL regulations, the absence of more recent update information or explicit validity periods raises concerns about the current relevance and validity of the data, suggesting it may be outdated or require verification against current regulations. |
| uniqueness | green | The 'id' field provides a unique identifier for each of the 5 records in the dataset. All values in the 'id' column (201, 202, 200, 203, 204) are distinct, ensuring that each record can be uniquely identified within the dataset. |
| lineage | red | No information is provided regarding the origin of the data, the methods used for its collection, or any subsequent transformation processes. This lack of lineage information makes it impossible to assess the data's provenance, reliability, and the trustworthiness of its source. |
| governance | red | There is no information available concerning data ownership, defined update frequencies, established quality control procedures, or documented data access and usage policies. This absence of governance details indicates a critical gap in understanding how the data is managed, maintained, and assured for quality over time. |
ztl_green_shield
| completeness | yellow | The dataset generally appears complete with all expected fields populated. However, the 'data_fine' field consistently uses '00000000' to indicate an indefinite end date, which, while conveying meaning, is not a standard date format and could be better represented by a NULL value or a specific, documented placeholder. |
| accuracy | red | A critical accuracy issue is identified with the 'data_ini' field. All sample records show a start date of 2025-07-01. Given today's date is 2026-10-06, these start dates are in the past. If the resource 'ztl_green_shield' is intended to represent current operational zones, the data is outdated and potentially inaccurate regarding the current status or effective dates of these ZTL gates. This suggests the dataset may be a historical plan rather than a reflection of current reality. |
| consistency | green | The dataset exhibits good internal consistency. Field formats for identifiers, dates (including the non-standard '00000000' for end dates), and coordinate values are uniformly applied across the sample records. Categorical fields like 'tipo_varco' and 'tipol_cost' also show consistent formatting and value types. |
| timeliness | red | The dataset suffers from severe timeliness issues. All 'data_ini' values are set to 2025-07-01. As of today, 2026-10-06, this means the data describes events that began over a year ago. If this resource is meant to provide current information about ZTL green shields, it is significantly outdated and does not reflect the present operational status or any potential changes that may have occurred since the initial planned activation. |
| uniqueness | green | The 'id' and 'num_varco' fields appear to serve as effective unique identifiers for each ZTL gate, with no duplicate entries observed in the provided sample records. This suggests good uniqueness within the dataset, allowing for individual record identification. |
| lineage | yellow | The 'atto_ini' field, referencing administrative acts (e.g., 'Deliberazione n. DG/2023/00607'), provides good traceability for the legal basis of the ZTL gates. However, explicit lineage information for the dataset itself, such as its publication date, last update, data collection methodology, or responsible department, is missing. This limits understanding of the dataset's lifecycle and current relevance. |
| governance | red | The significant issues observed in timeliness and accuracy, particularly the outdated 'data_ini' values and the potential disconnect between the dataset and current operational reality, strongly suggest a lack of robust data governance. Information regarding data ownership, update frequency, quality control procedures, or a clear definition of the dataset's purpose (current status vs. historical plan) is absent, indicating a need for improved stewardship. |
test-custom-resource
| completeness | red | GOLIA data source is currently unavailable: GET /v1/{city}/{resourceType} failed after 2 attempts |
| accuracy | red | GOLIA data source is currently unavailable: GET /v1/{city}/{resourceType} failed after 2 attempts |
| consistency | red | GOLIA data source is currently unavailable: GET /v1/{city}/{resourceType} failed after 2 attempts |
| timeliness | red | GOLIA data source is currently unavailable: GET /v1/{city}/{resourceType} failed after 2 attempts |
| uniqueness | red | GOLIA data source is currently unavailable: GET /v1/{city}/{resourceType} failed after 2 attempts |
| lineage | red | GOLIA data source is currently unavailable: GET /v1/{city}/{resourceType} failed after 2 attempts |
| governance | red | GOLIA data source is currently unavailable: GET /v1/{city}/{resourceType} failed after 2 attempts |