Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.7.1
-
Component/s: Google Earth KML Output
-
Labels:None
-
Number of attachments :
Description
This isn't on the critical path, but it'd be a nice capability to have. Hopefully someone will fund us to do it. I did some hacking and got it to work:
http://docs.codehaus.org/display/GEOS/Google+Earth+2.5d
It's all hard coded, but there's probably a wee bit of code that might be useful. For some reason svn isn't working for me at the moment, so I can't throw the diff up. But if anyone wants to see it just bug me.
Ideally the value to use as the extrude could be a filter, so you could just use an attribute, or some kind of function/equation, that even the user would be able to pass in to the server, so we can have dynamic extrudes. It should perhaps be part of the SLD. See http://trac.osgeo.org/mapguide/wiki/MapGuideRfc16 for how mapguide approached the problem.
Ok, looks like we already had an issue for this.
So the new idea is to do this with templates. We could do some nice stuff with the template, do simple math and functions to let people not only stick in their building heights and convert them properly to google units, but could also do cool visualizations of data using the Z coordinate (like population is represented by height).
To get this to work there are two magic tags that you must do in addition to setting the Z coordinate correctly (can just set it the same for all the points in a single geometry, which is why we're 2.5d and not 3d, deriving that value from the template).
<extrude>1</extrude>
<altitudeMode>relativeToGround</altitudeMode>
I think most all our stuff will be relative. If someone down the line asks for absolute altitude mode we can deal with that then.