<?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 Re: Failing in using Data Interoperability in PRO to convert IFC solids into multipatch featureclasses in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407408#M18131</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Bruce for taking the time to test it. Anyway, I will come back to this and possibly mark your answer as correct, but I would need time to see the differences in the settings (I am newbie with FME stuff). What I saw looking at the parameters quickly, is that we used a different output format (you chose GEODATABASE_FILE (ArcObjects) I have FILEGDB). Also, you have two voices under Feature Types under the output which I don't have, namely "PropertySetDefinition" and "QuantitySetDefinition". Again, I'll ome back to this as soon as I can. Thanks for the response, and meanwhile if you could give me some details on what you did it would be very appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 May 2017 16:19:29 GMT</pubDate>
    <dc:creator>AlessandroValra</dc:creator>
    <dc:date>2017-05-30T16:19:29Z</dc:date>
    <item>
      <title>Failing in using Data Interoperability in PRO to convert IFC solids into multipatch featureclasses</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407406#M18129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to use the Data Interoperability extension within ArcGIS Pro (1.4.1) to reproduce what I was able to do from within ArcMap: converting a IFC to a ESRI fGDB format. The IFC has solid geometries and I would need to export them as multipatch. I attached the IFC if anybody is interested in helping.&lt;/P&gt;&lt;P&gt;First thing I noted: there is no Quick Import in PRO. With ArcMap, I sued to use the Quick Import with the settings provided in &lt;A href="https://blogs.esri.com/esri/arcgis/2016/09/22/bim-gis-integration-with-ifc/"&gt;this ESRI post&lt;/A&gt; and the translation was succesfull.&lt;/P&gt;&lt;P&gt;In PRO I tried this workflow with no success (steps, figures, and results):&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Creation of a new ETL Tool from the Project Pane&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;IMG alt="Creation of a new ETL Tool from the Project Pane" class="image-1 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/354428_01.png" style="height: auto;" /&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Location and Name choice&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;IMG alt="Location and Name choice" class="image-2 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/354430_02.png" style="width: 620px; height: 310px;" /&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Generate Workspace Window settings (Coord. System should be correct, and it worked with the Quick Import in ArcMap)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;IMG alt="Generate Workspace Window settings" class="image-7 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/354435_03.png" style="height: auto;" /&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;IFC parameters settings as in &lt;A href="https://blogs.esri.com/esri/arcgis/2016/09/22/bim-gis-integration-with-ifc/"&gt;ESRI post&lt;/A&gt;.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;IMG alt="IFC parameters settings as in ESRI post." class="image-4 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/354432_04.png" style="height: auto;" /&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Choice of the Feature Types (I left everything checked as the default)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;IMG alt="Choice of the Feature Types (I left everything checked as the default)" class="image-5 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/354433_06.png" style="height: auto;" /&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Model execution (through the green RUN button)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;IMG alt="Model execution (through the green RUN button)" class="image-6 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/354434_07.png" style="width: 620px; height: 333px;" /&gt;&lt;/P&gt;&lt;P&gt;The output is just a bunch of Tables and some empty linear featureclasses. Also, I attached the Translation Log if it might help.&lt;/P&gt;&lt;P&gt;&lt;IMG alt="(wrong) Result of the whole process." class="image-8 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/354436_08.png" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From ArcMap, using the same dataset, same coordinate system, and same IFC parameters as in the linked post, I am able to export multipatch geometries. Unfortunately, ArcMap is not an option right now, and I have to stick with PRO to do this. Any help will be greatly appreciated.&lt;/P&gt;&lt;P&gt;Finally, I attached the zipped GDB derived from this process (&lt;STRONG&gt;test_DataInteropPRO_SR.gdb.zip&lt;/STRONG&gt;).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2017 09:40:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407406#M18129</guid>
      <dc:creator>AlessandroValra</dc:creator>
      <dc:date>2017-05-30T09:40:46Z</dc:date>
    </item>
    <item>
      <title>Re: Failing in using Data Interoperability in PRO to convert IFC solids into multipatch featureclasses</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407407#M18130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alessandro&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I successfully processed your data, please see the parameters in the attached ETL tool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bruce&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2017 14:51:33 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407407#M18130</guid>
      <dc:creator>BruceHarold</dc:creator>
      <dc:date>2017-05-30T14:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: Failing in using Data Interoperability in PRO to convert IFC solids into multipatch featureclasses</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407408#M18131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Bruce for taking the time to test it. Anyway, I will come back to this and possibly mark your answer as correct, but I would need time to see the differences in the settings (I am newbie with FME stuff). What I saw looking at the parameters quickly, is that we used a different output format (you chose GEODATABASE_FILE (ArcObjects) I have FILEGDB). Also, you have two voices under Feature Types under the output which I don't have, namely "PropertySetDefinition" and "QuantitySetDefinition". Again, I'll ome back to this as soon as I can. Thanks for the response, and meanwhile if you could give me some details on what you did it would be very appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2017 16:19:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407408#M18131</guid>
      <dc:creator>AlessandroValra</dc:creator>
      <dc:date>2017-05-30T16:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: Failing in using Data Interoperability in PRO to convert IFC solids into multipatch featureclasses</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407409#M18132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alessandro&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My apologies for not being specific, the File Geodatabase API writer does not support multipatch writing:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="http://docs.safe.com/fme/2017.0/html/FME_Desktop_Documentation/FME_ReadersWriters/filegdb/quick_facts_filegdb.htm" title="http://docs.safe.com/fme/2017.0/html/FME_Desktop_Documentation/FME_ReadersWriters/filegdb/quick_facts_filegdb.htm"&gt;Esri Geodatabase (File Geodatabase API) Quick Facts&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bruce&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2017 16:28:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407409#M18132</guid>
      <dc:creator>BruceHarold</dc:creator>
      <dc:date>2017-05-30T16:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: Failing in using Data Interoperability in PRO to convert IFC solids into multipatch featureclasses</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407410#M18133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is great news! Indeed, I tried the exact same procedure I described above, this time choosing "GEODATABASE_FILE (ArcObjects)" as output format instead of "File Geodatabase API". Everything worked just fine! Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 May 2017 15:14:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/failing-in-using-data-interoperability-in-pro-to/m-p/407410#M18133</guid>
      <dc:creator>AlessandroValra</dc:creator>
      <dc:date>2017-05-31T15:14:21Z</dc:date>
    </item>
  </channel>
</rss>

