I'm writing and installation profile and need a module which can convert an XML document into a KML (Google Earth) document. I could package this module so that it only works with the installation profile, but would much prefer to release it separately - if anybody would have any use for it.

Basically, the module would allow you to specify the location of an XML file, which could be an RSS feed or any other valid XML document. The module would then load the XML document and analyze the various tags that are used. The user would then need to specify which XML tags correspond to pertinent information. For example, the user could specify that the <title> tag contains to the title of the story and that the <location> tag contains the GPS coordinates which point to the location where this story was written. Using this information, the module would be able to create KML files on-the-fly by loading and converting the XML document.

I know that there are plenty of modules which convert Drupal stories into a KML file which can be loaded into Google Earth. The only problem with these modules is that they depend upon the Location API/module, which is still in development for Drupal 5 and has not even begun to be developed for Drupal 6. Thus, I will not be able to use any of these modules in the installation profile. I will not be able to join on as a developer for any of these modules due to the complexity of them, and the amount of time it would take to upgrade them.

There would of course be benefits and disadvantages to an XML-to-KML module. The user would first have to find some way (Views or other) to generate an XML document from their stories. However, they would have more flexibility than other KML-generating modules allow. Most notably, they would not need to rely on the Location API. As long as the GPS coordinates were contained somewhere in the XML, those coordinates could be used in the KML file. Thus, it would allow the user the flexibility to use CCK, hardcoding, or any other method to get those coordinates there.

But like I said, the primary reason I am interested in developing this module is because it will be needed for an installation profile I am writing. I would love to release it separately as well, but if you all in the Drupal don't think you would have any user for it, I will make it suitable for use in the Installation Profile only. Any other suggestions are welcome also.

Thanks alot!

Comments

john.karahalis’s picture

Would anybody care to comment on what they think about a XML-to-KML module?

Even if you think it is a bad idea, we would love to know about it. We're just trying to get an understanding of what the community is looking for.

Thanks alot!