osm component problem

Hi everone, I have a problem with all osm components. I opened my file a few days later (everything worked then) and after changing the radius at the osm shape component it turned orange and never came back. I opened the example file and i had the same issue, I tried the boolean toggle change from true to false and back but it didn't work. Any ideas what went wrong?

Attachments:

tuc_terrain.gh, 81 KB

Replies to This Discussion

Permalink Reply by djordje on August 3, 2017 at 1:06am

Hi Iro,

Can you post a screenshot or copy paste the warning message that you get from the readMe! output of the "OSM shapes" component?
Thank you in advance.

Permalink Reply by iro skouloudi on August 3, 2017 at 1:28am

1. The component generated invalid shapes data.

To fix this issue, simply rerun the component (set the "_runIt" input to "False", and then again to "True").

the strange thing is that the shape output contains curves, it is not empty even if the component seems not to work properly. Also when I try to change a value in osm objects like buildings, park etc it doesn't work. the shapes output shows all the categories together.

Permalink Reply by djordje on August 3, 2017 at 1:45am

Hi Iro,
What do you mean by: "when I try to change a value in osm objects like buildings"?

In the upper definition you attached there is no "OSM objects" droplist.

I tried your tuc_terrain.gh file on my home PC and it worked without any issues.

Do you have Administrator privileges on your PC?

Is it possible that you do this:
1) Set all _runIt inputs in your tuc_terrain.gh file to False.
2) Save an close the tuc_terrain.gh file.
3) Delete your "c:/gismo" folder
4) Open again your tuc_terrain.gh file in Grasshopper.
5) Run the "OSM shapes" component by setting its _runIt input to True.
6) If you again get the "Invalid shapes" warning, then set the _runIt input of the "OSM shapes" component to False.
7) Wait at least a couple of seconds (let' say 6 or 7 seconds)!
8) Set the _runIt input of the "OSM shapes" component to True again.

What happens then?

Permalink Reply by iro skouloudi on August 3, 2017 at 2:00am

I'll try all these and I will let you know. One more question, when you say "Delete your "c:/gismo" folder" you mean delete it from C:? And if so, gismo will be able to work?

Permalink Reply by djordje on August 3, 2017 at 2:22am

Yes, delete the "gismo" file from "c:/" partition. You won't have any problems when you do this. This will delete the openstreetmap and terrain files that gismo already downloaded for different locations. It may not fix your problem but it is worth trying.

Sometimes the issue is that people click too fast when they set the "OSM shapes" component's _runIt input from True to False, and then again to True. That's why I mentioned in my last reply to wait some 6 or 7 seconds.

Permalink Reply by iro skouloudi on August 3, 2017 at 2:34am

Unfortunately it didn't work. The problem started when I decided to change the radius in osm objects a few times. Before that all worked well. Maybe it is a problem of my pc. Thanx for trying to help!!

RSS