I’ve given some .geojson files to be analyzed in grasshopper, thus I am trying out almost all available plugins in the forum and on food4rhino.
So far the plug-ins are working with most of the types - points, lines, multiple polygons - however, I cannot retrieve the data when all of the geometries are in one single geojson.
I’ve noticed that the multi-geometry-type file is way larger than the single-geometry-type file, and has much more information when I open it in code editors.
Nonetheless, I am wondering if it’s possible to parse this multi-geometry-type geojson file with some plugin or if this file has some issue in the first place.
The file is zipped since discourse is not allowing geojson upload.
So glad that this data is readable, but it looks little bit different than what I was expecting though.
I haven’t tried it with Heron since it looked obsolete on the food4rhino, cause it was last updated 2 years ago and not showing if its supporting Rhino 7 atm.
I’ve deleted the files that are installed via food4rhino and fresh installed via PackageManger. Now its working without no issue.
I’ve got some other sample data provided, - multiple building outlines that is different from the first post, and it is still not readable via all the plugins
Could you tell me what is would be the best practice working with geojson data, especially what standard of GIS should I receive if I want to manipulate it in grasshopper environment?
I’m glad you found Heron on the Package Manager. Now that Heron v0.4.0 has been released, I plan to update food4rhino with an example file when it’s ready so there will be less confusion.
When using Heron, typically the first thing to do is set the Earth Anchor Point close to that of the data with the SetEAP component. Fewer errors will arise when this is done.
This will make sure all the data is coming in close to Rhino’s origin. Both geojson files you posted work when this is done. Note, I’ve unchecked “Clip with boundary” from the menu so that no boundary curve is needed.
I’m not sure I understand your last question, but overall I think geojson is a great GIS filetype. If you get the data in a projected coordinate system (ie EPSG:5179) you will probably have more success with the various plugins.
No, the boundary is not compulsory, but if you have a large shapefile or other data source, the boundary can clip the source and improve import time. You can provide any kind of closed curve as input.
