river_crossing
| completeness | yellow | The dataset exhibits minor completeness issues. Several optional fields like `longName`, `info` (for tunnels), and `statusMessage` are frequently null across records. Additionally, the `info` field within services is consistently null. While the provided data appears to be a full snapshot for the specified query (4 records), the absence of these descriptive attributes reduces the richness of the data. |
| accuracy | yellow | A notable accuracy concern is observed in the 'DeWaterbus' record where the top-level `status` is 'ACTIVE', but its `connectorStatus`, all `shore` statuses, and all `service` statuses are 'INACTIVE'. This discrepancy suggests that the overall status might not accurately reflect the operational state of the river crossing. Furthermore, the `info` fields contain raw HTML tags, which, while not an error, implies the data is not fully parsed or cleaned for direct consumption. |
| consistency | red | The data suffers from a critical consistency issue regarding the operational status of the 'DeWaterbus' record. The top-level `status` being 'ACTIVE' directly contradicts the `INACTIVE` status reported for its `connectorStatus`, individual `shores`, and their `services`. This internal inconsistency makes it difficult to ascertain the true operational state of this river crossing. There is also minor inconsistency in the population of `longName`, `info`, and `statusMessage` fields across records. |
| timeliness | green | The data is highly timely, as indicated by the 'Last updated' and 'Fetched at' timestamps matching today's date (2026-10-06). This suggests that the data is very current and reflects the most recent information available from the source. |
| uniqueness | green | All primary identifiers (`id`) for river crossings, shores, services, and accessibilities are UUIDs and appear to be unique within the provided dataset. No duplicate records or identifiers were found, ensuring that each entity can be distinctly identified. |
| lineage | yellow | Basic lineage information is provided through the `Source` URL (`https://api.slimoverdeschelde.be/api`) and the `Last updated`/`Fetched at` timestamps. This allows for tracing the origin and freshness of the data. However, there is no further detail on the data generation process, transformation steps, or explicit data refresh schedules, which would enhance the understanding of the data's journey. |
| governance | red | No information regarding data governance is provided. This includes details about the data owner, responsible department, data quality policies, contact persons for data issues, or terms of use. The absence of such information makes it challenging to understand the stewardship of the data and whom to approach for clarifications or problem resolution. |
transit_stops
| 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 |
transit_lines
| 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 |
transit_route_stops
| 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 |
bus_stops_accessibility
| completeness | red | The dataset exhibits critical completeness issues. The 'location.address' field is consistently null for all records, which significantly diminishes the utility of location data. Furthermore, the 'updated_at' field is also consistently null across all entries, making it impossible to ascertain when individual bus stop information was last verified or modified. These omissions hinder effective use and understanding of the data's details and freshness. |
| accuracy | red | A severe accuracy issue is present due to extensive duplication of physical bus stops. Multiple records share identical 'name', 'latitude', and 'longitude' values but are assigned different unique 'id's. For example, records 1 through 12 all represent 'Antwerpen J. De Voslei' at the exact same coordinates. This redundancy means the dataset inaccurately represents the number of distinct bus stops and can lead to erroneous analyses. |
| consistency | red | The dataset suffers from significant logical inconsistency. The primary issue is the redundant representation of physical bus stops, where the same stop (identified by name and coordinates) appears multiple times with different internal IDs. While data types and schema are consistent, this fundamental logical inconsistency makes the dataset unreliable for applications requiring unique identification of urban infrastructure elements. |
| timeliness | yellow | The dataset's overall timeliness is good, as the 'Last updated' metadata indicates it was refreshed on today's date (2026-10-06). However, the 'updated_at' field for individual records is uniformly null. This absence of record-level update information prevents users from assessing the freshness or most recent verification of specific bus stop details, which is a significant limitation for a dynamic resource. |
| uniqueness | red | While each record possesses a unique 'id' within the dataset, the underlying real-world entities (bus stops) are not uniquely represented. The pervasive duplication of bus stops, where multiple records correspond to the exact same physical location and name, severely compromises the uniqueness of the data at an entity level. This makes it challenging to identify and count distinct bus stops accurately. |
| lineage | yellow | The resource provides a direct ArcGIS FeatureServer query URL, which is a positive aspect for tracing the immediate source. However, there is a lack of detailed information regarding the data's broader lineage, such as original collection methods, any transformations applied, or the specific department/agency responsible for its creation and maintenance beyond the generic ArcGIS service identifier. This limits understanding of the data's provenance. |
| governance | red | Information on data governance is critically lacking. There is no explicit mention of a data owner, contact persons for inquiries, documented update frequency policies, or established data quality standards. The presence of significant data quality issues, such as widespread duplication and missing essential fields, further suggests an absence of robust data governance or effective quality control measures for this resource. |
tram_stops_accessibility
| completeness | yellow | The dataset exhibits significant completeness issues. The `location.address` field is consistently null for all records, severely limiting the contextual information for each tram stop. Crucially, the `updated_at` field is also null for every entry, making it impossible to determine the individual freshness or last verification date of the accessibility information. Additionally, the provided data contains 79 records, while the metadata indicates a total of 100 records, suggesting that this is a partial sample of the full dataset. |
| accuracy | yellow | The geographical coordinates (`latitude`, `longitude`) appear to be accurate and within the expected range for tram stops in Antwerp. The `vehicle_type` is consistently 'tram', aligning with the resource's description. However, the complete absence of address information (all `location.address` fields are null) reduces the overall accuracy and specificity of the location data, as users cannot pinpoint stops by a street address. |
| consistency | yellow | The data schema is consistently applied across all records, with fields like `id`, `name`, `location` (including `latitude`, `longitude`), `vehicle_type`, and accessibility flags (`accessible_mobility_impaired`, `accessible_with_assistance`, `accessible_visually_impaired`) maintaining their expected data types. However, a notable inconsistency lies in the representation of tram stops: numerous records share identical `name`, `location` coordinates, and accessibility attributes but are assigned different `id`s. This suggests that the `id` field might not uniquely identify a distinct physical tram stop, or that the data lacks a clear mechanism to differentiate between distinct platforms or directions for the same named stop. |
| timeliness | red | While the metadata indicates that the resource itself was last updated and fetched on today's date (2026-10-06), the `updated_at` field within every individual data record is null. This critical deficiency means there is no way to determine the freshness or last verification date of the accessibility information for any specific tram stop, making the timeliness of the actual data content entirely unknown and therefore unreliable for users needing up-to-date information. |
| uniqueness | red | The dataset suffers from severe uniqueness issues. There are numerous instances where multiple records possess identical values across all descriptive attributes, including `name`, `location` (latitude and longitude), `vehicle_type`, and all accessibility flags, yet each of these functionally identical records is assigned a distinct `id`. For example, 'Antwerpen A. Van Cauwelaert' appears multiple times with identical coordinates and accessibility information but different IDs. This high degree of functional duplication indicates that the `id` field does not serve as a unique identifier for a distinct physical tram stop and severely impacts the data's integrity and usability. |
| lineage | yellow | The resource provides a clear source URL (ArcGIS FeatureServer) which is a good starting point for tracing data lineage. However, further detailed information about the data's origin, such as the specific methods of data collection, the original data producer (beyond the platform), or any subsequent transformations or processing steps, is not available. The absence of individual record-level `updated_at` timestamps also hinders the ability to track the specific lineage and evolution of each data point. |
| governance | yellow | Information regarding the data governance framework for this resource is not explicitly provided. While the `Last updated` timestamp for the resource itself indicates a recent refresh, details on data ownership, established update frequencies, or specific quality control procedures are missing. The widespread issues of null values for `location.address` and `updated_at` fields, along with the extensive functional duplication, suggest potential gaps in data governance policies regarding data completeness, uniqueness, and metadata standards. |