<?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 Allow IN_MEMORY datasets to store metadata generated by geo-processing tools in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-in-memory-datasets-to-store-metadata/idi-p/936215</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;BR /&gt;&lt;BR /&gt;One of the great things about running a geo-processing tool is that it inserts information about the tool run on the dataset into the Geoprocessing history section of the metadata. This is incredibly useful for working out how a dataset was created, especially if the user who created the dataset provided no metadata (which in my experience is just about every major organisation on the planet).&lt;BR /&gt;&lt;BR /&gt;Another great thing about the modern ArcGIS is the in_memory workspace, this is great for storing temporary data without clogging up the hard drive and when you close ArcMap it all simply vanishes, love it!&lt;BR /&gt;&lt;BR /&gt;But...&lt;BR /&gt;&lt;BR /&gt;A FeatureClass stored in the in_memory workspace will not store any subsequent geoprocessing history. I may create a temporary dataset do some extra processing on it using geo-processing tools and then decide that it is indeed worth keeping and save out to a permanent location, but none of the geo-processing history is recorded.&lt;BR /&gt;&lt;BR /&gt;It would be an extremely useful improvement to an in_memory dataset to store the metadata. It would ensure a proper "paper trail" exists for a dataset.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Feb 2014 18:03:50 GMT</pubDate>
    <dc:creator>DuncanHornby</dc:creator>
    <dc:date>2014-02-19T18:03:50Z</dc:date>
    <item>
      <title>Allow IN_MEMORY datasets to store metadata generated by geo-processing tools</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-in-memory-datasets-to-store-metadata/idi-p/936215</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;BR /&gt;&lt;BR /&gt;One of the great things about running a geo-processing tool is that it inserts information about the tool run on the dataset into the Geoprocessing history section of the metadata. This is incredibly useful for working out how a dataset was created, especially if the user who created the dataset provided no metadata (which in my experience is just about every major organisation on the planet).&lt;BR /&gt;&lt;BR /&gt;Another great thing about the modern ArcGIS is the in_memory workspace, this is great for storing temporary data without clogging up the hard drive and when you close ArcMap it all simply vanishes, love it!&lt;BR /&gt;&lt;BR /&gt;But...&lt;BR /&gt;&lt;BR /&gt;A FeatureClass stored in the in_memory workspace will not store any subsequent geoprocessing history. I may create a temporary dataset do some extra processing on it using geo-processing tools and then decide that it is indeed worth keeping and save out to a permanent location, but none of the geo-processing history is recorded.&lt;BR /&gt;&lt;BR /&gt;It would be an extremely useful improvement to an in_memory dataset to store the metadata. It would ensure a proper "paper trail" exists for a dataset.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Feb 2014 18:03:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/allow-in-memory-datasets-to-store-metadata/idi-p/936215</guid>
      <dc:creator>DuncanHornby</dc:creator>
      <dc:date>2014-02-19T18:03:50Z</dc:date>
    </item>
  </channel>
</rss>

