Record-level JSON/schema validation failed for required fields, data types, formats, enums, or numeric constraints used by the current ParkAPI/OCPI analyzer.
Schema & Identifier Integrity
Location & Geometry
Two records share the same identifier/coordinates or are close enough to be treated as a likely duplicate location; duplicate pages include related records for comparison.
Coordinates fall inside a configured Baden-Württemberg water polygon where a parking or charging feature is implausible.
A parking-spot record is more than the allowed distance from its referenced parent parking-site record.
Data Freshness & Timeliness
Static, modified, realtime, or OCPI last-updated metadata is older than the configured analyzer threshold for that field.
Realtime timestamps or values indicate the realtime feed is stale/frozen beyond REALTIME_SITE_REFRESH_SECONDS.
static_data_updated_at is much older than a recent modified_at, indicating a possible metadata bump without a real static-data refresh.
Capacity & Occupancy Integrity
Capacity is negative or exceeds the single configured maximum parking-entity capacity threshold of 10,000.
Metadata & Completeness
Provider/operator names normalize to very similar spellings, suggesting inconsistent naming of the same operator.
Name is missing, too short, purely numeric, repeated, or matches known placeholder tokens; allowed generic parking terms and short alphanumeric IDs are not flagged.