ELK 2 issue - different results to ELK 1

Hello,

So i wanted to get information on ATM machines and bicycle rental in a certain place (osm map file attached). When using ELK 2 (dropdown menu for feature types and adding sub-types), both amenity:bicycle_rental and amenity:atm gave no results. It was the same with highway:bus_stop.

I knew it is not possible so i tried using ELK 1 instead - using same values/keys it gave expected results. Problematic area is highlighted with group - Screenshot below:

Has anyone got an idea why it doesn't work with ELK 2? I find it highly possible that i am doing something wrong, so any advice would be appreciated :).

I'd like to get some more information on these, especially bus stop names and bicycle rental capacity - i know this kind of info is often covered by OSM. Unfortunately i have no idea how to get that result with ELK 1.

I attach gh file and osm map file.

Thank you for your time and help!

Attachments:

elk2issue.gh, 16 KB
elk2issue.osm, 4.9 MB

Replies to This Discussion

Permalink Reply by Timothy Logan on October 23, 2016 at 11:32am

I'm running into two problems that I don't recall seeing before. First, when you have the "Show Individual Outputs" checked from the sub-feature selection window, the OSM Data component isn't outputting any data. And second, there's a lot of unexpected data that's not being properly filtered out. There should be at most 36 elements that it should find between ATM's, bus stops, and bicycle rentals, but for some reason it's letting through hundreds of things that it shouldn't. You can filter this down, but it's definitely a problem. I don't really have an answer for you at the moment, but I'll see what I can do to resolve it when I can find some time.

Attached is a way that you can try filtering for the things you want until I'm able to get it resolved.

-Tim

Attachments:

elk2issue_TL01.gh, 21 KB

Permalink Reply by Wujo on October 23, 2016 at 12:10pm

Hello Tim,

Thank you for your response and help with filtering the data. These problems you listed are exactly what i meant. What do you think might the problem be? Is it connected with OSM file, corrupt installation or is there a problem inside elk?

Thank you for your time and help

Permalink Reply by Timothy Logan on October 23, 2016 at 2:51pm

It's likely a problem in Elk. I looked through the OSM file a bit for the ATM's and the hits when I searched for the text 'atm' in the file and found 17 hits, though 2 represented the same object because one of it's tags was 'amenity:atm' and another was 'atm_ref:ML1824A' so it would match the 16 items that the filtered content was showing. It may be a few weeks before I get a chance to really get into it just based on my work schedule right now so you may have to live with the filtered approach for now.

RSS