[Fiware-miwi] Asset instancing mechanism for XML3D query responses of GIS Data Provider

[Torsten Spieldenner]

Hello,

as mentioned in the call yesterday, I think the delivery of the XML3D 
ground geometry as reply from GIS-Data-Provider could be improved based 
on the new asset instancing technique of XML3D.

Currently, the result is returned as .xml3d - file, that contains the 
geometry in a format similar to that:

<group>
     <mesh>
         ..... // indices, positions, texcoords ... // ///
    </mesh>
</group>

Client handles the request by copying this reply into the client's 
xml3d-node. This works fine, the drawback here is just that all geometry 
is present in the DOM.

What could work instead, is returning an .xml file (response-type 
application/xml) with the following content:

<?xml version="1.0" encoding="utf-8" ?>
<xml3d xmlns="http://www.xml3d.org/2009/xml3d">
     <asset id="asset">
         <assetmesh>
             ..... // indices, positions, texcoords as before // ...
         </assetmesh>
     </asset>
</xml3d>

Now instead of querying $PROVIDER-HOST/QUERY and copy the response, the 
client would create and add a <model> node that references the <asset> 
by specifying the query as external source:

<model src="$PROVIDER-HOST/QUERY#asset" />

What happens then, is that the client creates an instance of the 
externally described asset that describes the ground geometry. This 
should create exactly the same scene as before, just that the 
description of the ground geometry in the client's DOM is reduced from 
the full vertex data to this single model node.

Best
Torsten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140626/20483ac7/attachment.html>