How we check prices
Every month we read each council's own car park pages and record every price, rule and pay code with the page it came from and the date.
Checks on every car park
- Where a council publishes pay-by-phone codes, we compare them across two of its own pages and open RingGo's public page for each code to make sure it is the right car park. If the council's pages disagree, we use the code that both RingGo and one of the council's pages agree on. If no code checks out, or the council publishes none, we do not show a pay button.
- Where a council publishes prices in more than one place (for example a car park's own page and a notice of new charges), we check they agree. If they do not, the car park is held back.
- Where the council says nothing about something, such as a height limit, we say "Not stated" rather than guess.
- We check prices make sense: a longer stay should not cost less than a shorter one, and we do not show tickets longer than the maximum stay. Anything that looks like a mistake is left out.
- Car parks with prices that change by day or time are read by a person, and that reading is checked again if the council changes its page.
- Small price changes are updated automatically. Big changes are held back until someone has looked.
A town only appears once every one of its car parks has passed these checks. If a later check fails, we keep showing the last checked version. Each page shows the date it was last checked.
Map positions
Where the council's own map or OpenStreetMap has the car park, the pin is exact. Otherwise the pin is at the centre of the car park's postcode, and the directions buttons search for the car park by name. If a council's postcode is missing or wrong but its map pin is confirmed by OpenStreetMap, we show the nearest real postcode.
Signs at the car park always have the final say.