Open kiliankoe opened 5 years ago
a friend asked me about the entrance height of a parking lot (he drives a camping van).
Maybe you can add this too.
If available I would put stuff like that in the additional information field, which should definitely be displayed in the apps once I get around to updating those 👍
I'll just copy my comment from #215 here to continue the conversation as suggested.
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:
@AugustQu I'm not sure having an explicit field for headroom/entrance height makes sense, since it only applies to some lot types, but it's definitely something we could add to additionalInformation
if available 👍
edit: I see I've written that above as well, sorry about the duplicate comment 😄
wherever you want to store this information.
A friend drives a 'Wohnmobil'. For entering a parking lot with this vehicle he needs this information.
Can I add a few more requests for an updated schema?
2020-06-09T19:15:19+02:00
) for times, instead of a timezone-less version that implies UTC.
Since Dresden has started this, fits nicely into the project. I suppose adding a link for buying tickets for supported services to a city's data would make the most sense.
Apps would probably just open the system browser either in-app or directly, having a button to buy tickets somewhere. I'll open separate issues for that.