Problem for recognizing isolated OSM points

Hi there!

I don't know if somebody else had got the same problem, but let's try.

I was extracting some particular features of the OSM through the GenericOSM component.

Actually it uses to work pretty well just by setting the appropriate "key" and "value". However I've noticed that it does not detect isolated points.

For example, imagine you are "capturing" all the amenities labeled as "school". Ok, then, the component detects all the points which belong to a polygon (as boundaries, buildings or similar) and then the polygon can be drawn. However, if you have just a node tagged as "amenity" and "school" for some unknown reason it is ignored by the GenericOSM component.

Actually, I've tried just looking for "amenity" in general, leaving the "*" in the other imput as default, and it does the same, it just ignores the isolated "nodes", though they are detected by the OSMData component (because I can see them as small crosses! arg! Haha).

Any idea?

Thanks!

Replies to This Discussion

Permalink Reply by Timothy Logan on March 19, 2012 at 7:34am

This is something that was pointed out before. The plugin currently only searches the tags in the ways, not inside of the nodes. It's on my list of things to investigate.

Permalink Reply by JArgota on March 19, 2012 at 7:40am

OK. Thanks!!!! :)

Permalink Reply by FA_RE on June 25, 2012 at 11:33am

Hi,

great tool, but i woud like to know if there is a solution to get the "isolated nodes"?

TNX

Permalink Reply by Timothy Logan on June 25, 2012 at 12:27pm

I have an update that I've been testing that has quite a few changes, including the ability to get the isolated notes, but I haven't had time to document the changes. I'll try to throw together a new video or document soon and get it all released soon.

Permalink Reply by FA_RE on June 29, 2012 at 4:25am

TNX for the reply!!

Permalink Reply by JArgota on August 10, 2012 at 6:32am

Hi there again Tim,

I've been checking out this new release, but I can't get to make nodes work separately.

It is, I've seen the improvement in the input data for the OSM generic component, however, the K values filters in the right way all the points, but the V input just do nothing. And it only happens when collecting only point (it is, setting a 2 in the C input).

For example, I want to filter all the school nodes and ways. I link the OSM source file, and the, set "amenity" in K, and "school" in V. If I set 1 for C, I get all the way tagged as "school", so it is fine. However, if I try to get the nodes tagged as "school", and therefore I set 2 for C, i get all the amenities points...

Any idea what could be wrong?

Thanks!!!

Javier

Permalink Reply by Timothy Logan on August 10, 2012 at 7:27am

Yeah I just did a quick glance over the code and it looks like it's not evaluating the value of V in the part that searches through the points. Should be a relatively quick fix though. I'll try to get an update out soon.

Permalink Reply by JArgota on August 10, 2012 at 10:06am

Hi Tim!

Thanks a lot.

I am looking forward to check out your update for starting to get the most out of it! :D

Take care,

Javier

Permalink Reply by Timothy Logan on August 11, 2012 at 2:35pm

Thanks for pointing it out. There's an update that should fix the bug. I tested it on a few things and everything seemed to be working according to what I'd expect.

-Tim

RSS