search

offenesdresden / ParkAPI

🅿️ open API serving parking lot data for multiple cities
https://parkendd.de/map.html
MIT License
85 stars 46 forks source link

Scrape parking lot details from openstreetmap #118

Open Haves1001 opened 8 years ago

Haves1001 commented 8 years ago

I saw that there was originally planned to support a scraping of detail information by url. Did you ever consider to link information generated by the openstreetmap project with the live data scraped from various sources?

Like you can see here there are a lot of information regarding the location and details of the parking spots: Overpass parking lots in Dresden

kiliankoe commented 8 years ago

Sounds like a great idea actually! There's several sources from where we should be aggravating additional data, be it better positioning data (as in the outline of the parking lot), pricing information, opening times or whatever.

In doing so we should probably think about the data format we're sending to the apps. Most data would be unnecessary to send on every request.

I'd love to get some input from @jklmnn, @sibbl and @Mic92 on this 😊

Mic92 commented 8 years ago

As our goal is to scrape live data, it would probably make sense, if we only provide the openstreetmap id in the api for our few lots and let the clients to make a nearby search to overpass to create a mashup.

kiliankoe commented 8 years ago

We did want to make data from Dresden's parking lot detail pages available though, just never got around to it... That information is quite useful to have.

Haves1001 commented 8 years ago

From my experience most parking lot owner do not provide the detail information or at least it is really hard to scrape them. But I agree, maybe it would be the best way to provide the osm id with the repsonse. But I'm not so sure if you want to handle the whole information handling on client side as the osm key:value mapping would have to be translated/converted to a human readable format. This would maybe save some effort to do it one time on backend side. Additionally you are more flexible to change settings like the overpass host when you want to/have to change the provider.

jklmnn commented 8 years ago

I would prefer if we keep the API compatible and extend it with extra data from OSM.

Mic92 commented 8 years ago

Overpass returns probably more park lots for same area as we currently have. To include these results it would be required to narrow the search in the API. This is possible, but has to be taken into account.

kiliankoe commented 8 years ago

If we include OSM (or other) data, I suggest only doing so for the lots we actually support, e.g. those lots that actually have current data and are published on the sites we scrape.