Importing KML - Why Use Data Interop instead of "KML to Layer" tool?

452
3
Jump to solution
08-30-2013 08:05 AM
RobinPaone
New Contributor II
I am not seeing an advantage to using the Data Interoperability Extension for importing Google Earth map data.  Let me know if you disagree.

The "Direct Read" option that Data Interop provides has disadvantages: 
- For a simple point KML map it displays several other empty layers.  I found the map points are in the "Placemark Point" layer but the other layers are all seeming void of geometry and data
- The sybology is not transferred at all
- I could not find any attribute data set in Google Earth (e.g. pop-up info)

I also tried the "Quick Import" option with Data Interop and got the same results.

When I use the "KML to Layer" tool all of the sybology and attributes are brought in.

Am I missing something?  What are the advantages of using Data Interop for KML?  Let me know.  Thanks!
0 Kudos
1 Solution

Accepted Solutions
BruceHarold
Esri Regular Contributor
Hello Robin

Data Interoperability does have significant functionality beyond the core KML/Layer tools.  For example DI can manage a schema object so that attributes exported from ArcGIS to KML can later be correctly imported from KML to typed fields, and not an HTML description object.  Attachments (network links) are accessible too, plus many more parameters.  You will however need to look into how to get the most from DI for your data and workflows.  FMEpedia is a good place to start, or contact me if you cannot find what you need bharold@esri.com.

http://fmepedia.safe.com/fmeSearch?q=kml

http://cdn.safe.com/training/course-materials/KML-Pathway-Tutorial.pdf

Regards

View solution in original post

0 Kudos
3 Replies
BruceHarold
Esri Regular Contributor
Hello Robin

Data Interoperability does have significant functionality beyond the core KML/Layer tools.  For example DI can manage a schema object so that attributes exported from ArcGIS to KML can later be correctly imported from KML to typed fields, and not an HTML description object.  Attachments (network links) are accessible too, plus many more parameters.  You will however need to look into how to get the most from DI for your data and workflows.  FMEpedia is a good place to start, or contact me if you cannot find what you need bharold@esri.com.

http://fmepedia.safe.com/fmeSearch?q=kml

http://cdn.safe.com/training/course-materials/KML-Pathway-Tutorial.pdf

Regards
0 Kudos
ChristineMcMahon
New Contributor
I am trying to use data interoperability but it has disappeared. It is no longer on the Customise Extensions drop down list. The toolbox gives an error message when I click on the tools saying ' the item's XML contains errors'.

I tried installing again but now it will not, perhaps because of a license condition? It says it can't find some file it needs to install.

And the only time I did try to use it to import SLIP data from WA.gov.au I didn't get a good import of data. It brought in a few squiggles...

Any ideas?
0 Kudos
BruceHarold
Esri Regular Contributor
Hello Christine

I think you should open a support call, the analyst will be able to tell if this is an install or licensing issue.

Regards
0 Kudos