Hi Jarkko, It would mainly affect the delivery of the data itself and hardly the documentation as it would still be XML3D. Talk to you later, Philipp Am 30.06.2014 09:37, schrieb Jarkko Vatjus-Anttila: > Torsten, > > The changes you suggest are surely doable and we should take those into > the "TODO" -list. However, I would not yet pursue in changing the code > related to this since it would affect the deliverables and also > documents. I am uncertain how those changes would be incorporated at > this point, given that we we have had some trouble in finalizing the > documentation in the past. Maybe this could go (among other things) to > the task list of Fi-Core enhancements for GIS. > > - j > > > On Thu, Jun 26, 2014 at 3:42 PM, Torsten Spieldenner > <torsten.spieldenner at dfki.de <mailto:torsten.spieldenner at dfki.de>> wrote: > > 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" > <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 > > > > > -- > Jarkko Vatjus-Anttila > CTO > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com <mailto:jarkko at cyberlightning.com> > > See our new press release: > http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ > > www.cyberlightning.com <http://www.cyberlightning.com/> > > This e-mail and all attached material are confidential and may contain > legally privileged information. If you are not the intended recipient, > please contact the sender and delete the e-mail from your system without > producing, distributing or retaining copies thereof. > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Geschäftsführung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140702/aa16fb5a/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy