I was trying to write a plugin for Rhino + Grasshopper (CAD environment). I was trying to run simulations, and wanted to get my graph in UTM coordinates (meters unit). Is there a way I can import OSM and transform the coordinates to UTM (I have that logic implemented), need a way to plug it into the import framework (probably through a ITwoPassPreprocessor).
Also within the same application, I have some geometry in the CAD environment, which Grasshopper allows me to algorithmically model. So I wanted to use a street network that someone has potentially modeled in the CAD environment, and wants to build a network out of it. In the plugin I am developing, I am introducing an interface for this, but dont know whats the best way to create a routerdb from custom geometric data (in UTM coordinates). Right now I was thinking of serializing it to an osm format and loading that, but is there a better way to do it. I tried using the overloaded constructors for RoutingNetwork but got confused the Attribute and metadata layout.
I was trying to write a plugin for Rhino + Grasshopper (CAD environment). I was trying to run simulations, and wanted to get my graph in UTM coordinates (meters unit). Is there a way I can import OSM and transform the coordinates to UTM (I have that logic implemented), need a way to plug it into the import framework (probably through a ITwoPassPreprocessor).
Also within the same application, I have some geometry in the CAD environment, which Grasshopper allows me to algorithmically model. So I wanted to use a street network that someone has potentially modeled in the CAD environment, and wants to build a network out of it. In the plugin I am developing, I am introducing an interface for this, but dont know whats the best way to create a routerdb from custom geometric data (in UTM coordinates). Right now I was thinking of serializing it to an osm format and loading that, but is there a better way to do it. I tried using the overloaded constructors for RoutingNetwork but got confused the Attribute and metadata layout.