I must be going mad, as at some point during testing the latest release and dev versions of the KML module, I'm sure there were a set of configuration options available, possibly including one that allows a height to be set for the altitude value in the KML element output by views feed (defaulted at 0).

I'm hoping being able to change this will help render a set KML layer of points above polylines defined seperately in a Google map script.

After scouring the module code for both 6.x-2.0-alpha1 and current 6.x-dev, I'm stumped as to where the KML admin options have gone. Found references to admin/config/kml in previous releases, but nothing at that path for 6.x-2.0-alpha1. Have all configuration options been removed?

Module installed via Drush, Views 6.x-2.16, Core 6.22.

Thanks.

Comments

Elder Brother’s picture

Elder Brother commented

Although Still perplexed by the elusive configuration options, have adjusted the altitude of elements for all kml feeds by amending kml.placemark.tpl.php as follows -

<?php
// $Id$
?><Placemark>
  <styleUrl>#highlight</styleUrl>
  <name>
    <![CDATA[<?php print $name ?>]]>
  </name>
  <description>
    <![CDATA[<?php print $description ?>]]>
  </description>
  <?php if ($styleUrl): ?>
  <styleUrl><?php echo $styleUrl; ?></styleUrl>
  <?php endif; ?>
  <Point>
    <coordinates><?php print substr($coords, 0, -1). '100'; ?></coordinates>
  </Point>
</Placemark>

The default '0' becomes '100'.

This didn't raise my KML markers above my script-drawn polyline anyway, but there you go.

jeffschuler’s picture

jeffschuler
Location Boulder, Colorado
commented
Version: 6.x-2.0-alpha1 » 6.x-2.x-dev

You're not mad: there was a module configuration page in 6.x-1.x. In 6.x-2.x, with implementation made more views-dependent, this was removed.

Hard-coding altitude here is silly. We should probably make altitude configurable; allowing to not include at all, to set to a static value (default 0,) or to derive from a views field. Would that suit your needs?