generative modeling for Rhino
CAN WE IMPORT MY PLACES MARKED IN GOOGLE TO GRASSHOPPER SOMEHOW USING GHOWL??
What format do 'myplaces' come in? Are these KML? What are you expecting to import...Markers, geometry?
File extension is kmz (attached), and i wish to import Markers
EDIT : I just saw the save options, and it can be saved in kml format too
In gHowl we have to written anything to explicitly read KML files, though the XML parser component gives you the data. With some appropriate selection of paths, you can get the data from there.
I just wrote a quick and dirty script to get the specific Placemark elements from the KML file. The script looks for Points, LineStrings (paths), and Polygons and outputs the element value. I am attaching the grasshopper file, a Rhino file with a picture as an underlay. You might need to reference the underlay picture. I will add an improved version to the next gHowl. Currently just the geometry is returned, not the name or anything else...
let me know if you need to make some sense of it.
In gHowl we have to written anything to explicitly read KML files
In gHowl we have NOT written anything to explicitly read KML files
Thanks Luis, for a quick response and your effort...
I am using Rhino 4 SR9, so the rhino file isn't opening... I think there is only image for reference in there so the grasshopper file should run on its own, right? But, i am getting this error
And this doesn't change whether the path for the file is provided or not... is it due to the absence of rhino file?
No, I think it is due to the Rhino version. The rhino file should not matter, as you say, as it is only really an underlay...I am running on Rhino 5 and the .Net framework it is targeting is different so the code in the c# component will not behave in the same manner in Rhino 4 sr9. Do you have the option to run this in Rhino 5?
No, i don't have rhino 5
Is there a way to import name or description too? Since i intend to import a large number of place-marks, so naming them individually would take quite a while...
I have not had a chance to port this to Rhino 4 code. I hesitate to do so because Rhino 5 will be out any week now (hopefully!). I tend to just work in Rhino 5 now and rarely look back to Rhino 4. If I get the chance I will attempt it in Rhino 4...