<?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 Repair Data Source to Selection Layers in Mapping Questions</title>
    <link>https://community.esri.com/t5/mapping-questions/repair-data-source-to-selection-layers/m-p/75771#M901</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I recently was asked to create a supplementary map showing data that I had until that moment thought I was not ever going to need to revisit. I had archived the .mxd I originally used, moving it off our server. This caused the data sources to become corrupted, but no biggy, I had the original feature classes to repair them with, right? Not so much. I had selected out very precisely multiple sets of line features (pipeline data in reference to certain tracts/projects) and made selection layers from one original feature class. When I went to repair the original feature class I made the selections from, it automatically repaired the subsequent selection layers. Looking at the selection layers, it appears that somehow the data didn't repair correctly (i.e. I know roughly where the pipe should be for each project, and the repaired layer is including line features sporadically that don't accurately reflect the original selection). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know why this is happening and if there is any last ditch effort I can try before having to start from scratch?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Mar 2016 00:44:41 GMT</pubDate>
    <dc:creator>CamillaKaramanlis</dc:creator>
    <dc:date>2016-03-02T00:44:41Z</dc:date>
    <item>
      <title>Repair Data Source to Selection Layers</title>
      <link>https://community.esri.com/t5/mapping-questions/repair-data-source-to-selection-layers/m-p/75771#M901</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I recently was asked to create a supplementary map showing data that I had until that moment thought I was not ever going to need to revisit. I had archived the .mxd I originally used, moving it off our server. This caused the data sources to become corrupted, but no biggy, I had the original feature classes to repair them with, right? Not so much. I had selected out very precisely multiple sets of line features (pipeline data in reference to certain tracts/projects) and made selection layers from one original feature class. When I went to repair the original feature class I made the selections from, it automatically repaired the subsequent selection layers. Looking at the selection layers, it appears that somehow the data didn't repair correctly (i.e. I know roughly where the pipe should be for each project, and the repaired layer is including line features sporadically that don't accurately reflect the original selection). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know why this is happening and if there is any last ditch effort I can try before having to start from scratch?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2016 00:44:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/mapping-questions/repair-data-source-to-selection-layers/m-p/75771#M901</guid>
      <dc:creator>CamillaKaramanlis</dc:creator>
      <dc:date>2016-03-02T00:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: Repair Data Source to Selection Layers</title>
      <link>https://community.esri.com/t5/mapping-questions/repair-data-source-to-selection-layers/m-p/75772#M902</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If by "selection layer" you mean using the selection/save as selection layer, and not a definition query or join-based select, then I don't have a lot of hope.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I stopped using these years ago, as they are unstable. I believe they store a hash-table of the selected keys (ObjectiDs?). These seem to disappear when the layer is changed, so then everything is selected. I have never heard of the wrong records being selected, but it would make sense that that happens sometimes too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Next time, you could try exporting the keys of your chosen records to a file, then using a join to do your selection from your original file. This is kludgy, but reliable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2016 01:23:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/mapping-questions/repair-data-source-to-selection-layers/m-p/75772#M902</guid>
      <dc:creator>DanaNolan</dc:creator>
      <dc:date>2016-03-02T01:23:12Z</dc:date>
    </item>
    <item>
      <title>Re: Repair Data Source to Selection Layers</title>
      <link>https://community.esri.com/t5/mapping-questions/repair-data-source-to-selection-layers/m-p/75773#M903</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah, I believe I just quickly created layers from selected features. Thank you for the tip, I definitely learned my lesson!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2016 16:55:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/mapping-questions/repair-data-source-to-selection-layers/m-p/75773#M903</guid>
      <dc:creator>CamillaKaramanlis</dc:creator>
      <dc:date>2016-03-02T16:55:11Z</dc:date>
    </item>
  </channel>
</rss>

