Hi Andrea,
Thanks for the quick response. Maybe it's a different issue then because we
are able to extrude polygons as explained here [1]. After placing the
height.ftl file on the corresponding directory, the KML file returned by:
http://localhost:8080/geoserver/wms/reflect?layers=topp:states&format=application/vnd.google-earth.kml+xml
returns something like this:
...
<MultiGeometry>
<Point>
<extrude>1</extrude>
<altitudeMode>relativeToGround</altitudeMode>
<coordinates>...</coordinates>
</Point>
<Polygon>
<extrude>1</extrude>
<altitudeMode>relativeToGround</altitudeMode>
<outerBoundaryIs>
...
</outerBoundaryIs>
</Polygon>
</MultiGeometry>
...
And it is displayed as in the screenshots. However, if we use a point layer
(I'm using a test layer with a single point) and perform the same request
we obtain a KML with:
...
<Point>
<coordinates>...</coordinates>
</Point>
...
which doesn't contain the <extrude/> or the <altitudeMode/> tags, even if
the latter is specified in the request. I assumed that's what the issue was
talking about: internally always uses clampToGround, which results in
missing tags in the KML output.
Regarding the extrusion, probably the most useful result would be to place
the point over the ground with altitudeMode:relativeToGround and
extrusion:false. But that's not a real extrusion, actually. If you edit by
hand the generated KML to add <altitudeMode> and <extrusion>, Google Earth
draws the extrusion as a line from the ground to the point, as you say.
Regards,
Víctor.
2013/12/16 Andrea Aime <andrea.a...@geo-solutions.it>
> On Mon, Dec 16, 2013 at 7:04 PM, Victor Gonzalez <
> victor.gonza...@geomati.co> wrote:
>
>> Hello,
>>
>> I'm Víctor González, I am a developer. Currently I work with a customer
>> that needs to extrude KML data using GeoServer. When we extrude polygons it
>> works as expected, but we found a problem when doing it with points. The
>> version we are using is 2.4.0.
>>
>> I found that this has been already reported [1]. Also, I know that there
>> was a codesprint las friday [2]. However, I didn't find any update in the
>> issue tracker or any commit referencing the issue in the github repo.
>>
>> Is there any progress with this? Is anybody else currently working on it?
>> Provided that we can spend some time on fixing it ourselves and contribute
>> the solution, any advices?
>>
>> Best regards,
>> Víctor.
>>
>> [1] http://jira.codehaus.org/browse/GEOS-6167
>>
>
> This report is related to all geometries, not only points, the issue
> there is that the code always refers to the
> ground, not to the sea level, and supposedly there is a parameter to make
> it refer the sea level, that is not honored.
>
> The issue you report is not being worked on by anyone, that I know of.
> However... not sure what you'd expect
> from a point "extrusion", a single line from the ground to the point maybe?
>
> Cheers
> Andrea
>
> --
> *== GeoSolutions will be closed for seasonal holidays from 23/12/2013 to
> 06/01/2014 ==*
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
