From what I can tell, ZH GoogleMap lets you leverage just about every API option that Google Maps offers, including KLM and Place files. You can add unlimited locations, including text descriptions, links, and customizable icons and icon behaviors. Moreover, you can organization locations by category and collect them under icon groups, which greatly simplifies both the administration and front-end access to extensive location lists.
Component documentation is pretty spare---the developer doesn't really explain what options are or why you would/wouldn't want to use them. Still, the Google API itself is well documented, and a few searches can tell you everything you want to know.
In all, I can't rate this extension highly enough. It's a truly stunning development effort, both richly functional and intelligently designed. Over the past four years, I've tested and used literally hundreds of Joomla components. I've seen the good, the infuriating, and the ugly---and now I've been honestly delighted by ZH GoogleMap.
Indispensable for adding back-end "editor eyes only" notations to article text, module titles, and other content elements. Nice work, Bigshot!
As other reviewers have noted, support is also a hurdle. During our evaluation period, forums on Ordasoft's site were inaccessible. Unlike most user support forums, Ordasoft's cannot be read by unregistered readers, and the registration process was broken. We also sent multiple support queries directly to the support email (which is synonymous with the sales email). Ordasoft did not respond.
I look forward to seeing this extension evolve. it has good potential. For now, however, I regret the money we spent on it.
Our only (wee) complaint is that CF is designed to work only in the main content position, so CF forms can't directly be published to module positions. While CF offers a workaround to this limitation, it involves a third-party extension (Place Here) that a) isn't well supported and b) has issues of its own.*
So, ultimately, we're a bit limited in how we can use CF. But within those boundaries, it's great.
* Specifically, multiple instances of the Place Here module appear to conflict with each other. So if, for example, you want to publish different forms via PH on different areas of your site, and those areas are associated with different collapsible menu trees, ALL menu structures for ALL areas in which PH is published will open whenever you access any given page with a CF/PH instance.
OK, maybe it's a narrow problem. But it's limiting if you want to use CF to publish forms that let users interact directly from various content pages (without leaving the page). The PH limitation makes that scenario a navigational nightmare for the site user.