mfdz / thingsboard-to-parkapi Goto Github PK

The page https://www.herrenberg.de/de/Stadtleben/Erlebnis-Herrenberg/Service/Parkplaetze contains the (static) list of parking spaces in Herrenberg.

We want to add it to our list of dynamically updated parking spots in Herrenberg. That's why want to extract the data from the above web site and convert it to JSON.

Acceptance criteria

• Extract the data from the page either manually or by writing a script (preferable). BeatifulSoup is a nice python library to do this kind of thing.
• Convert the data to a JSON that looks like this: https://github.com/offenesdresden/ParkAPI/blob/master/park_api/cities/Basel.geojson?short_path=3982ad9
• You can extract the lat,lng from the details page: it is encoded in the Google Maps link (Anfahrt/Routing)
• Commit the resulting JSON file to this repo.
• If you write a script also commit it.

Values should be ‚no/yes/opening_hours like string‘
That is to comply withOSM tagging and not to introduce a new scheme.

For parkings where charge is know, this may be provided as well (see OSM wiki)

We currently use camelCase like e.g. openingHours internally while ParkAPI should use OSM like snake case (opening_hours). Please harmonize these.

Depending on opening hours, state should be open or closed. See schema.

The ParkAPI city.json schema currently does neither support opening_hours nor fees. We should ask them to add these to the schema. Additionally, I'd like to add a new attribute to provide additional notices to customers, like e.g. upcoming events/opening hour changes etc.

The lot_types Park-Carpool/Park-Ride don't fit in the (German) naming schema for the other lot types.
In my opinion, upstream should agree on (English) enum values.

As every change would require adopting clients, this would be a breaking change and be handled with care. For now we leave as is implemented, but should discuss this issue with the ParkAPI project.