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

Scrape parking lot details from openstreetmap #118

Open
Haves1001 opened this issue May 15, 2016 · 7 comments
Open

Scrape parking lot details from openstreetmap #118

Haves1001 opened this issue May 15, 2016 · 7 comments

Comments

@Haves1001
Copy link

Haves1001 commented May 15, 2016

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
Copy link
Member

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
Copy link

Mic92 commented May 16, 2016

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
Copy link
Member

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
Copy link
Author

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
Copy link
Member

jklmnn commented May 16, 2016

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

@Mic92
Copy link

Mic92 commented May 17, 2016

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
Copy link
Member

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.

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

No branches or pull requests

4 participants