mboeringa

> Wow, 1 month is a LONG time. If you have the means, the Data Interoperability extension may produce faster results - http://store.esri.com/esri/showdetl.cfm?SID=2&Product_ID=632&Category_ID=28 > Unfortunately, the $2,500 price tag is...

@ThomasEmge Thanks very much for the detailed descriptions of some of the design considerations. There are possibly a couple of things getting mixed up though: > Shapefiles would be nice...

> I do leave it running though, as I am pretty sure it will finish. Despite performance, the Load OSM File tool with memory conserving on, has proven reliable (and...

@OneHwang. Actually, it didn't fail after several weeks. It had loaded all the nodes, but failed on creating the point indexes one day into the process of building the indexes....

> Have you tried using osm2pgsql on large files, and then connecting ArcMap into the PostgreSQL database? That is not an option for me. Besides the fact that I don't...

@OneHwang. Well, bad news again ;(. I now discovered it failed a second time with the same error and a failure to build the point index. Clearly, Europe as a...

Hi Thomas, I am currently concurrently importing Geofabrik *.osm files for both the whole of Germany and the Netherlands to File Geodatabases stored on non Windows system drives, which are...

Thanks Thomas, Yes, you are right, this makes it very likely that I have been running into a disk space issue, especially since all other imports up to now have...

> Correct, assembling the ways requires a read from the OSM file, a read operation for the participating nodes from the point feature class and a write for the resulting...

> I am currently working on a way to separate these operations across drives and simplify the loading process. I am gathering numbers right now on how big the difference...