A couple weeks ago I found myself trying to remember how to create a KML-enabled ArcGIS map service through ArcGIS Server Manager. Luckily for me I wrote a blog on this topic about a year and a half ago. Reading the blog helped me with the task at hand, but I felt an update would be valuable. Therefore, this month’s blog post focuses on returning attribute data from KML-enabled ArcGIS map services as well as things to watch out for when WFS-enabling ArcGIS map services.
Why doesn’t my KML-enabled map service display tabular data???
In my previous post, I described the steps involved in creating the map service’s KMZ file on an ArcGIS server. However, I didn’t relay how one goes about ensuring that the tabular data tied to the features in that service will be returned when a user clicks on the feature in Google Earth. In order to do this, one must enable the feature layer’s HTML Popup tool within the map service’s MXD. For detailed instructions on how to complete this task, refer to the “How to set HTML properties for feature layers” section.
I can’t WFS-enable my ArcGIS Server map service, why???
If one is interested in providing users of their dynamic ArcGIS Server map service with the ability to use the data within the service in geospatial analysis scenarios, then one solution is to WFS enable the service. Just like KML enabling, the process of actually WFS enabling the ArcGIS map service is quite simple. However, there are two very important things to keep in mind when WFS enabling an ArcGIS map service.
1) If one’s ArcGIS map service is published using a MSD, as opposed to a MXD, then the map service cannot be WFS enabled. The solution is publishing the service from the service’s MXD.
2) If one’s ArcGIS map service consists of at least two layers that reference the same feature class then the map service cannot be WFS enabled. A solution is to create a copy of the feature class and reference one of the layers to the copy. NOTE: This solution can be painful from a data management perspective, especially if one is working with large datasets that are frequently updated.
Hopefully now that I have written these tasks in a blog I will not forget them. However, it is nice to know that if I do I can always refer back to my blog for guidance. I guess blogging can sometimes be viewed as a unique type of documentation.

Posted by Jeremy Monn 


















