On 05/13/2013 10:57 AM, Andrea Aime wrote:
On Mon, May 13, 2013 at 11:34 AM, Nuno Oliveira <nuno-miguel-olive...@ptinovacao.pt <mailto:nuno-miguel-olive...@ptinovacao.pt>> wrote:

    Thanks for merging the pull request.
    Yes we signed the contribution agreement and send it to OpenPlans,
    but no response.
    I will make a post about this situation in the next days.
    (contribution agreement in attach).


I guess I can give you access in the meantime. What is your github id?

Thanks, here my github info:

   /username: //nmco
   mail: //nuno-miguel-olive...@ptinovacao.pt/

As I said in a previous email ,unfortunately I will not be able to have a decent contribution "rate" to W3DS until July 2013. (Need to finish my thesis, some papers to submit, a lot of work in my "oficial" job, and so on ...)

    Both X3D and KML support the inclusion of externals 3D models,
    but infortunatlly they support diferent formats X3D support X3D
    models and KML support Collada models.
    Tools like Blender support the export to X3D, Collada and others
    formats.
    The role of W3DS is only to include that models in the produced
    scene it no regrad tof the model format.
    The user is responsible to provide the model in the correct
    format, using diferent SLDs, SLDs rules, etc ...


Fair enough :-)

    The main objective is that the produced scenes can be directly
    viewed on browsers.
    For KML scenes we need to use the GoogleEarth plugin but for X3D
    the scenes can be
    directly viewed using for example X3DOM ( http://www.x3dom.org/).
    W3DS implementation
    on GeoServer supports the format 'text/html' which produced an
    html+x3dom+x3d page that
    can be viewed in any browser that support WebGL without any
    adicional plugin.

    Example:
    
http://3dwebgis.di.uminho.pt/geoserver3D/geoserver3D/w3ds?version=0.4&service=w3ds&request=GetScene&format=text/html&crs=EPSG:4326&layers=geoserver3D:level_lines&boundingbox=-17.207,32.834,-17.19,32.843&styles=ll_by_type


Ah ha, cool. I find the navigation a bit hard, but it's sure quite interesting With a bit of love to improve a bit the GUI a preview such as this one would make quite the showcase for GeoServer.

Yes, the navigation is hard. X3DOM have nice examples about how the GUI can be improved: http://www.x3dom.org/?page_id=5
I agree with you a decent GUI can make a nice showcase for GeoServer.

Btw, I'd change the output format from text/html to something like application/x3d or application/x3dom, so that it's evident what we are getting back. In the end application/openlayers also produces a html no?

I agree, 'text/html' was the first experience about two years ago :), +1 for application/x3dom.

    For sample visualizations in X3D (test propose) just make the
    request with 'text/hmlt'
    format and make sure you have a browser that support WebGL.
    KML needs a test page with Google Earth Plugin installed.


Right... or it will work with Google Earth desktop edition too, right?

Yes it will, but we can only use the produced KML (No API).
It the GoogleEarth Plugin we have an API that let us make interesting things.

Btw, I've tried stating "application/vnd.google-earth.kml+xml" as the output format, but it did not work.
Checked the caps document, can't find the list of supported output formats

The test server have not been update yet it this version so KML is not available ... sorry.
Until the end of this I will updated it.



    For more advanced uses cases I'm waiting for OpenLayers3. In the
    meantime
    http://www.openwebglobe.org/, http://www.x3dom.org/ and
    http://www.google.com/earth/explore/products/plugin.html.
    Be aware that openwebglobe use a custom format.


Right, so a new output format should be written for it?

In the last Agile conference I have a talk with one of the authors of openwebglobe ( Martin Christen) about the possibility to use GeoServer W3DS service as input for the globe, the drawback as the implementation of a custum format in W3DS. So Yes a new output format (if I am not wrong, based on JSON)
should be implemented.


    Not in an easy way.
    The duplication of code should be removed and I know that the
    use of SLD3D parser is not the solution, is just an workaround.
    When I  have some time i will look at this.


Nice thanks

Cheers
Andrea

--
==
GeoServer training in Milan, 6th & 7th June 2013! Visit http://geoserver.geo-solutions.it <http://geoserver.geo-solutions.it/> for more information.
==

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

-------------------------------------------------------

Best regards,

Nuno Oliveira

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to