<?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>idea Documentation about true curves (aka CAD data) being stored separately from ST_GEOMETRY info (within SHAPE object/column) in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/documentation-about-true-curves-aka-cad-data-being/idi-p/1191102</link>
    <description>&lt;P&gt;Regarding SDE.ST_GEOMETRY shape object columns (Oracle):&lt;/P&gt;&lt;P&gt;Rumor has it, true curve info (aka CAD blob data) is stored separately from ST_GEOMETRY info — all within the same shape object/column. In other words, if we query the geometry via ST_GEOMETRY functions, we don't have access to true curve data, since it's stored in a separate object attribute (an LOB attribute).&lt;/P&gt;&lt;P&gt;(I imagine the wording above is wrong, but that's because I don't have any documentation to reference.)&lt;/P&gt;&lt;P&gt;Could information about the above be added to the docs? Otherwise, I'm just fumbling around in the dark.&lt;/P&gt;&lt;P&gt;I know the usual suspects are likely to say, "You can't access the CAD blob via ST_GEOMETRY anyway, so it's a moot point." That might be, but I still need to understand how it's been set up...so I can understand what the limitations are and how to work around them. For example, I need to understand how ST_GEOMETRY pre-densifies the true curves into straight segments. What logic is used for the pre-densification?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit - Related:&amp;nbsp;&lt;A href="https://community.esri.com/t5/geodatabase-questions/why-did-a-polygon-lose-76-sqft-shape-area-when/m-p/1269082/highlight/true#M8349" target="_self"&gt;Why did a polygon lose 76 sqft (Shape.Area) when exporting from Oracle ST_Geometery to File GDB?&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Mar 2023 20:43:40 GMT</pubDate>
    <dc:creator>Bud</dc:creator>
    <dc:date>2023-03-23T20:43:40Z</dc:date>
    <item>
      <title>Documentation about true curves (aka CAD data) being stored separately from ST_GEOMETRY info (within SHAPE object/column)</title>
      <link>https://community.esri.com/t5/data-management-ideas/documentation-about-true-curves-aka-cad-data-being/idi-p/1191102</link>
      <description>&lt;P&gt;Regarding SDE.ST_GEOMETRY shape object columns (Oracle):&lt;/P&gt;&lt;P&gt;Rumor has it, true curve info (aka CAD blob data) is stored separately from ST_GEOMETRY info — all within the same shape object/column. In other words, if we query the geometry via ST_GEOMETRY functions, we don't have access to true curve data, since it's stored in a separate object attribute (an LOB attribute).&lt;/P&gt;&lt;P&gt;(I imagine the wording above is wrong, but that's because I don't have any documentation to reference.)&lt;/P&gt;&lt;P&gt;Could information about the above be added to the docs? Otherwise, I'm just fumbling around in the dark.&lt;/P&gt;&lt;P&gt;I know the usual suspects are likely to say, "You can't access the CAD blob via ST_GEOMETRY anyway, so it's a moot point." That might be, but I still need to understand how it's been set up...so I can understand what the limitations are and how to work around them. For example, I need to understand how ST_GEOMETRY pre-densifies the true curves into straight segments. What logic is used for the pre-densification?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit - Related:&amp;nbsp;&lt;A href="https://community.esri.com/t5/geodatabase-questions/why-did-a-polygon-lose-76-sqft-shape-area-when/m-p/1269082/highlight/true#M8349" target="_self"&gt;Why did a polygon lose 76 sqft (Shape.Area) when exporting from Oracle ST_Geometery to File GDB?&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 20:43:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/documentation-about-true-curves-aka-cad-data-being/idi-p/1191102</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2023-03-23T20:43:40Z</dc:date>
    </item>
    <item>
      <title>Documentation about ST_Geometry curves/CAD BLOB</title>
      <link>https://community.esri.com/t5/data-management-ideas/documentation-about-true-curves-aka-cad-data-being/idc-p/1269799#M2130</link>
      <description>&lt;P&gt;&lt;EM&gt;(merged from a separate idea)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;It would be helpful if documentation could be added about&amp;nbsp;about curves and CAD BLOBs in&amp;nbsp;ST_Geometry.&lt;/P&gt;&lt;P&gt;For example, expand on details like this:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;From &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/1250"&gt;@ShannonShields&lt;/a&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Features with curve geometry/circular arcs have two representations in enterprise geodatabases. The ST_Geometry shape stores a densified arc version of the geometry, and the true curve is stored in a blob format read by ArcGIS, but not by the DBMS.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/t5/geodatabase-questions/why-did-a-polygon-lose-76-sqft-shape-area-when/m-p/1269082/highlight/true#M8349" target="_blank" rel="noopener"&gt;https://community.esri.com/t5/geodatabase-questions/why-did-a-polygon-lose-76-sqft-shape-area-when/m-p/1269082/highlight/true#M8349&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Some related GIS Stack Exchange posts:&amp;nbsp;&lt;BR /&gt;&lt;A href="https://gis.stackexchange.com/search?q=%5Bst-geometry%5D+cad" target="_blank" rel="noopener"&gt;https://gis.stackexchange.com/search?q=%5Bst-geometry%5D+cad&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 20:44:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/documentation-about-true-curves-aka-cad-data-being/idc-p/1269799#M2130</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2023-03-23T20:44:23Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation about ST_Geometry curves/CAD BLOB</title>
      <link>https://community.esri.com/t5/data-management-ideas/documentation-about-true-curves-aka-cad-data-being/idc-p/1269803#M2131</link>
      <description>&lt;P&gt;&lt;A href="https://community.esri.com/t5/data-management-ideas/need-documentation-about-true-curves-aka-cad-data/idi-p/1191102" target="_blank"&gt;Need documentation about true curves (aka CAD data... - Esri Community&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2023 13:20:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/documentation-about-true-curves-aka-cad-data-being/idc-p/1269803#M2131</guid>
      <dc:creator>DanPatterson</dc:creator>
      <dc:date>2023-03-21T13:20:47Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation about true curves (aka CAD data) being stored separately from ST_GEOMETRY info (within SHAPE object/column)</title>
      <link>https://community.esri.com/t5/data-management-ideas/documentation-about-true-curves-aka-cad-data-being/idc-p/1271112#M2133</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/351335"&gt;@Bud&lt;/a&gt;&amp;nbsp;I have merged your two posts so that both of your comments are preserved in the same space.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks as always for your ideas!&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 19:46:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/documentation-about-true-curves-aka-cad-data-being/idc-p/1271112#M2133</guid>
      <dc:creator>SSWoodward</dc:creator>
      <dc:date>2023-03-23T19:46:10Z</dc:date>
    </item>
  </channel>
</rss>

