[Herrenberg] Data

[hbruch]

Herrenberg now publishes open parking data, already in ParkAPI format: https://api.stadtnavi.de/parkapi.json (URL might still change in future).

Note: the response contains some additional tags (opening_hours, fees) which we'd like to add to the schema in an upcoming PR.

I think that even if external data providers comply with the ParkAPI schema, for security/compatibility reasons responses should not only be passed through.

Is there already a reusable scraper for remote ParkAPI sources?

[kiliankoe]

This is very cool! I also very much like the additional data, which is something I've been meaning to add to the spec for a long time, a PR for that sounds great!

I think that even if external data providers comply with the ParkAPI schema, for security/compatibility reasons responses should not only be passed through.

The ParkAPI project also tries to aggregate historical data, so at least caching it makes sense in any way. The initial motivation behind the project also included alleviating potential stress from data sources by not passing requests from clients directly through. Popularity has never risen to anywhere close to that being an issue however. Just as an aside to security and compatibility, which are valid enough by themselves as reasons 👍

Is there already a reusable scraper for remote ParkAPI sources?

Nope, not yet.

[kiliankoe]

A few months ago I took a stab at rewriting the data aggregation with some lessons learned in mind. Regarding the additional lot data, I arrived at this list:

• dataAge: Date?
• name: String
• coordinates: Coordinates
• city: String
• region: String?
• address: String?
• available: Available (discrete values or range, as the Deutsche Bahn for example only has ranges in their dataset)
• capacity: Int?
• state: State
• type: LotType?
• detailURL: URL?
• imageURL: URL?
• pricing: Pricing? (contains optional text and URL for more info)
• openingHours: OpeningHours? (contains optional text and URL for more info)
• additionalInformation: [String: Any]?

See here: https://github.com/OpenParkingApp/OpenParkingBase/blob/b80585775abbabbac088c2540d766449c934a3ec/Sources/OpenParkingBase/Lot.swift#L4-L18

[hbruch]

Before I comment here: Should we discuss additional data in #175 or in a new issue?

[kiliankoe]

Makes sense to move that conversation there 👍

[AugustQu]

Hi,

can you please include the headroom of a parking lot in the data.

Is headroom the correct word for it? I mean the max. allowed height of a car entering the parking lot.

Thanks.

[kiliankoe]

I noticed that only two lots in the dataset have actual availability information, is this to be expected (for now)?

[kiliankoe]

It's not being used in any way right now for this project, but I added a module for the (possibly) upcoming version of this project to play around with the data: https://github.com/OpenParkingApp/Herrenberg

[hbruch]

@kiliankoe for now, there are only two parking areas with live data, indeed.

They use floor sensors sending their occupancy state via LoRaWAN which is then aggregated. For a couple of other parkings occupancy data will be published as soon as it's available.

[kiliankoe]

Ah that's awesome! And adding more data sounds great as well 👍