The Geoprocessing Community announces that the OSM2NetworkDataset V 1.1.1 can be used for ArcView. This Java application converts OpenStreetMap (OSM) data for use in network analyses in the ArcGIS extension Network Analyst. It is designed to generate transportation networks for any mode of transportation and any region. The generated networks are based on OSM attributes, such as restrictions, one-way roads, turn restrictions, point barriers, and maximum speed.
I have already tested extending the heap size. It doesn't solve the problem.
I'm going to investigate where this library comes from. Maybe it comes from others arcgis plugin.
I'll let you know as soon as possible.
creating a geodatabase from a 16mb osm-file (Heidelberg Old City) according to the log-file took me 02:18 min.
My 2nd osm-file was 184mb (metropolitan area) and I canceled the process after 1,5h because the process was significant slower than before. According to Oliver's question is the osm-filesize or the processor (or both?) the determining factor? (machine: Win7 64 bit; 4GB ram; 2,4 GHz, ArcGis 10.0 SP3)
I ran the program to convert the CA OSM file to a network dataset and after a couple hours I canceled it. I concluded that the program takes a LONG time to convert large OSM files.
I think what might be a better work around is to download smaller geographies of the roadway network you want to create. In my case geographies of 5,000 nodes or less (what the max size of an OSM file I can download from the OSM site). Run the network dataset for the smaller geographies. Then append the source data created by OSM2NDS (i.e., roads, turns, pois, junctions, etc). Lastly, rebuild the network dataset per the specifications of the network dataset created by the OSM2NDS program.