Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was wondering if anyone has come across a tool, or can point to code snippets, for batch importing Collada (.dae) files into a MultiPatch format. I have found a good "How to", but it is all manual. Also with this manual process the Collada file is not imported into is exact geospatial location.

Here is the youtube link to the "How to"

share|improve this question
Do you have FME or the Data Interoperability Extension? – blah238 Jan 18 '13 at 3:30
I believe I have both, but I know I have Data Interoperability – Ryan Garnett Jan 18 '13 at 16:03
up vote 3 down vote accepted

I have successfully used FME in the past to do this type of conversion. I can't remember if there were any other quirks to the translation, but if you've never used it before you would essentially just add the appropriate readers and writers, hook them up and see if it works.

In my case I was converting from Google Earth (KMZ) files, which use COLLADA (.dae) models internally. The KML in the KMZ file is what provides the georeferencing information, and FME reads it automatically. I believe the COLLADA specification provides no place to store georeferencing information, so you will need to address that issue somehow. This FME Evangelist post talks about the georeferencing issue: GeoNerds, Breadcrumbs, and 3D Georeferencing

See also, related question: How can I export a sketchup Model to ArcGIS's Multipatch?

share|improve this answer
Thank you, this is great. I am having the georeferencing issue with Collada, so I was looking at other options. I will look into FME and give it a test. As a side note, when I loaded the Collada files manually, ArcScene crashed after 5 or 6 were loaded. Just a note to other who are looking at doing this. – Ryan Garnett Jan 18 '13 at 16:47
Actually turns out the specification does include georeferencing information. See section 5-40, "geographic_location". It may be that it's simply not present in your files. – blah238 Jan 18 '13 at 16:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.