Issues related to evse_id_heterogeneity.
Schema & Identifier Integrity
Record-level JSON/schema validation failed for required fields, data types, formats, enums, or numeric constraints used by the current ParkAPI/OCPI analyzer.
Two OCPI EVSE records share the same evse_id/uid/id; detail rows include both records so operators can compare the duplicates.
Issues related to evse_id_anomaly.
Location & Geometry
Coordinates fall inside a configured Baden-Württemberg water polygon where a parking or charging feature is implausible.
Latitude and/or longitude is absent on a location-bearing record, so the feature cannot be mapped or spatially validated.
Data Freshness & Timeliness
Static, modified, realtime, or OCPI last-updated metadata is older than the configured analyzer threshold for that field.
Equipment & Connector Integrity
EVSE status is missing/unknown or explicitly unavailable/out of order; this is operational availability, not a schema error.
An EVSE status has remained unchanged beyond the configured stale-status threshold.
Connector data is missing a maximum power value, has non-positive or above-threshold power in watts, or uses a standard outside the OCPI/DATEX taxonomy.