<?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 DWG to GeoJSON Conversion in Workato – Best Integration Approach? in Community Chat</title>
    <link>https://systematic.workato.com/t5/community-chat/dwg-to-geojson-conversion-in-workato-best-integration-approach/m-p/12337#M1267</link>
    <description>&lt;P&gt;Has anyone integrated a DWG-to-GeoJSON conversion in a Workato recipe?&lt;/P&gt;&lt;P&gt;I have existing Java code that uses Aspose.CAD to parse DWG entities (lines, polylines, etc.) and generate a GeoJSON FeatureCollection. Since Workato's code step supports only Ruby and can't run Java or load JVM libraries natively, I'm exploring the best way to integrate this Java-based conversion with Workato. I'm &lt;STRONG&gt;not&lt;/STRONG&gt; planning to wrap the Java code as a Spring Boot REST service, so I'm interested in other integration patterns.&lt;/P&gt;&lt;P&gt;Looking for advice on:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;What is the best way to integrate existing Java code with Workato without rewriting the logic in Ruby?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Has anyone implemented a similar CAD-to-GIS conversion workflow in Workato?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Are there recommended approaches for handling large DWG files efficiently during the integration?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;If you've solved a similar problem, what architecture or integration pattern worked well for you?&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Any experience, recommendations, or alternative approaches would be greatly appreciated.&lt;/P&gt;</description>
    <pubDate>Wed, 01 Jul 2026 08:18:28 GMT</pubDate>
    <dc:creator>gopikrishnan</dc:creator>
    <dc:date>2026-07-01T08:18:28Z</dc:date>
    <item>
      <title>DWG to GeoJSON Conversion in Workato – Best Integration Approach?</title>
      <link>https://systematic.workato.com/t5/community-chat/dwg-to-geojson-conversion-in-workato-best-integration-approach/m-p/12337#M1267</link>
      <description>&lt;P&gt;Has anyone integrated a DWG-to-GeoJSON conversion in a Workato recipe?&lt;/P&gt;&lt;P&gt;I have existing Java code that uses Aspose.CAD to parse DWG entities (lines, polylines, etc.) and generate a GeoJSON FeatureCollection. Since Workato's code step supports only Ruby and can't run Java or load JVM libraries natively, I'm exploring the best way to integrate this Java-based conversion with Workato. I'm &lt;STRONG&gt;not&lt;/STRONG&gt; planning to wrap the Java code as a Spring Boot REST service, so I'm interested in other integration patterns.&lt;/P&gt;&lt;P&gt;Looking for advice on:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;What is the best way to integrate existing Java code with Workato without rewriting the logic in Ruby?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Has anyone implemented a similar CAD-to-GIS conversion workflow in Workato?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Are there recommended approaches for handling large DWG files efficiently during the integration?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;If you've solved a similar problem, what architecture or integration pattern worked well for you?&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Any experience, recommendations, or alternative approaches would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2026 08:18:28 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/community-chat/dwg-to-geojson-conversion-in-workato-best-integration-approach/m-p/12337#M1267</guid>
      <dc:creator>gopikrishnan</dc:creator>
      <dc:date>2026-07-01T08:18:28Z</dc:date>
    </item>
  </channel>
</rss>

