<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic CityEngine collada export vertex percision? in ArcGIS CityEngine Questions</title>
    <link>https://community.esri.com/t5/arcgis-cityengine-questions/cityengine-collada-export-vertex-percision/m-p/379689#M5244</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a question about exporting CGA created models to collada files.&amp;nbsp; My problem being when exporting extruded building footprints to collada I would like not to have to recenter them.&amp;nbsp; This leaves them in the real world position just in collada format.&amp;nbsp; This leads to vertices that very large number of significant figures for example a vertex would look something like X = 123456.7891 Y = 12.1234 Z = 1234567.1234. Instead of a re-centered value of X = 12.123 Y = 1.23 Z = 12.123.&amp;nbsp; The problem is that CityEngine is converting some of the longer numbers to scientific notation and rounding numbers off.&amp;nbsp; This causes a loss of precision and is stretching footprints in odd ways. This has shifted vertices as much as 10 meters in places.&amp;nbsp; The vertex precision is correct when looking at the shape inspector under the vertex tab.&amp;nbsp; However when looking at the collada file in notepad the vertex now looks like Y = 1.12345e6.&amp;nbsp; Any thoughts on how to keep CityEngine from converting to scientific notation would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Jan 2015 18:41:55 GMT</pubDate>
    <dc:creator>leewinslow1</dc:creator>
    <dc:date>2015-01-07T18:41:55Z</dc:date>
    <item>
      <title>CityEngine collada export vertex percision?</title>
      <link>https://community.esri.com/t5/arcgis-cityengine-questions/cityengine-collada-export-vertex-percision/m-p/379689#M5244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a question about exporting CGA created models to collada files.&amp;nbsp; My problem being when exporting extruded building footprints to collada I would like not to have to recenter them.&amp;nbsp; This leaves them in the real world position just in collada format.&amp;nbsp; This leads to vertices that very large number of significant figures for example a vertex would look something like X = 123456.7891 Y = 12.1234 Z = 1234567.1234. Instead of a re-centered value of X = 12.123 Y = 1.23 Z = 12.123.&amp;nbsp; The problem is that CityEngine is converting some of the longer numbers to scientific notation and rounding numbers off.&amp;nbsp; This causes a loss of precision and is stretching footprints in odd ways. This has shifted vertices as much as 10 meters in places.&amp;nbsp; The vertex precision is correct when looking at the shape inspector under the vertex tab.&amp;nbsp; However when looking at the collada file in notepad the vertex now looks like Y = 1.12345e6.&amp;nbsp; Any thoughts on how to keep CityEngine from converting to scientific notation would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jan 2015 18:41:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-cityengine-questions/cityengine-collada-export-vertex-percision/m-p/379689#M5244</guid>
      <dc:creator>leewinslow1</dc:creator>
      <dc:date>2015-01-07T18:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: CityEngine collada export vertex percision?</title>
      <link>https://community.esri.com/t5/arcgis-cityengine-questions/cityengine-collada-export-vertex-percision/m-p/379690#M5245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lee,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For georeferenced data, do not use Collade. Use GDB or KML what can deal with this properly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ok?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;SPAN lang="EN-US"&gt;Matthias Buehler&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN lang="EN-US"&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;SPAN lang="EN-US"&gt;Head of 3D Technologies&lt;/SPAN&gt;&lt;/EM&gt;&lt;STRONG&gt;&lt;SPAN lang="EN-US"&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #999999; font-size: 10pt;"&gt;&lt;SPAN lang="EN-US"&gt;twitter: @MattB3D&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN lang="EN-US"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US"&gt;-------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US"&gt;Garsdale Design Limited &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:matthias.buehler@garsdaledesign.co.uk" target="_blank"&gt;matthias.buehler@garsdaledesign.co.uk&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.garsdaledesign.co.uk/" target="_blank"&gt;www.garsdaledesign.co.uk&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jan 2015 15:05:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-cityengine-questions/cityengine-collada-export-vertex-percision/m-p/379690#M5245</guid>
      <dc:creator>MatthiasBuehler</dc:creator>
      <dc:date>2015-01-08T15:05:52Z</dc:date>
    </item>
  </channel>
</rss>

