Due to limited functionality of GDAL with respect to OSM file types, I've decided to add OsmSharp and Protobuf-net dependencies in order to create the ImportOSM component. This component will read local OSM files and generate geometry organized into three branches, one each for Nodes, Ways and Relations. Additionally, it will attempt to interpret elements with "building" and "building:parts" keys to create 3d building geometry (currently breps).
To make it easier to find relevant OSM data, I've also included a RESTOSM component that grabs data from available OSM endpoints (ie the Overpass API). Once an OSM file is generated with RESTOSM, this can be plugged into ImportOSM.
Due to limited functionality of GDAL with respect to OSM file types, I've decided to add OsmSharp and Protobuf-net dependencies in order to create the
ImportOSMcomponent. This component will read local OSM files and generate geometry organized into three branches, one each for Nodes, Ways and Relations. Additionally, it will attempt to interpret elements with "building" and "building:parts" keys to create 3d building geometry (currently breps).To make it easier to find relevant OSM data, I've also included a
RESTOSMcomponent that grabs data from available OSM endpoints (ie the Overpass API). Once an OSM file is generated withRESTOSM, this can be plugged intoImportOSM.