Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Konstanz scraper collects bogus data #232

Closed
defgsus opened this issue Jan 2, 2022 · 2 comments
Closed

Konstanz scraper collects bogus data #232

defgsus opened this issue Jan 2, 2022 · 2 comments

Comments

@defgsus
Copy link
Collaborator

defgsus commented Jan 2, 2022

Currently, looking at https://api.parkendd.de/Konstanz it show things like this for every lot:

{
  "address": null,
  "coords": null,
  "forecast": false,
  "free": 0,
  "id": "konstanz168",
  "lot_type": null,
  "name": "168",
  "state": "nodata",
  "total": 0
}

I haven't looked into the details as i actually just rewrote the scraper for ParkAPI2. Their website is working fine.

I guess they changed the number of columns in the tables and what once was the lot name is now the number of free spaces. You will probably notice when exporting the archive for 2021 ;)

@defgsus
Copy link
Collaborator Author

defgsus commented Jan 2, 2022

Checking my own little scraper, the change in the table has been some months ago.

@defgsus defgsus linked a pull request Jan 2, 2022 that will close this issue
@jklmnn
Copy link
Member

jklmnn commented Jan 3, 2022

I see, thanks for noticing. The reason for that is likely that we had to make the scraper more error resistant (sometimes single lots would have missing information). However we only check if the scraper fail. So as it was error resistant it didn't fail anymore on missing data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants