+6I wonder if anyone knows a knows what would be a good format to write out solid geometry. I have worked with filegeodatabase but that is multipatch. I need spatial indexing to be able to use a spatial intersect with a feature reader. So a big dataset with solids where we often only need a few of.
The multipatch feature class (FGDB) kind of works but then I need a solidbuilder and that takes a lot of time.
Thank you!
Best answer by virtualcitymatt
FFS does seem like a good option. But I would also like to mention that a solid builder isn’t always required. You can also use a GeometryCoercer to coerce a CompositeSurface into a Brep and it’s much faster.
Another option would be storing the Solid Geometry and an attribute (e.g., GeoemtryExtractor)? Then in your workflow replace the Solid with a 2D representation (Polygon) which can be used as a spatial query.
Other options for Solids include CityJSON and CityGML, however, you can’t work with a spatial index there. But there is the 3DCityDB which is the database version of CityGML (PostGIS).
If you’re only ever going to read it back into FME (guess based on the mention of the FeatureReader), you could look into using FMEs own native format, FFS:
https://docs.safe.com/fme/html/FME-Form-Documentation/FME-ReadersWriters/ffs/ffs.htm
+6
+47
FFS does seem like a good option. But I would also like to mention that a solid builder isn’t always required. You can also use a GeometryCoercer to coerce a CompositeSurface into a Brep and it’s much faster.
Another option would be storing the Solid Geometry and an attribute (e.g., GeoemtryExtractor)? Then in your workflow replace the Solid with a 2D representation (Polygon) which can be used as a spatial query.
Other options for Solids include CityJSON and CityGML, however, you can’t work with a spatial index there. But there is the 3DCityDB which is the database version of CityGML (PostGIS).
