<?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: NC Law Requirements (SB 355) in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/nc-law-requirements-sb-355/m-p/1535913#M45374</link>
    <description>&lt;P&gt;Hi. This is the &lt;U&gt;user&lt;/U&gt; forums, where users communicate with other users (and some Esri employees&amp;nbsp; who also use the software, but most not authorized to speak on behalf of the company). Communicating vendor requirements to Esri should be done through Tech Support and/or Customer Service and/or your local government representative. I would note that backfitting fundamental changes to software in Mature or Retired support status is not a likely outcome, especially if modern software in active support already has that capability.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;</description>
    <pubDate>Fri, 06 Sep 2024 14:15:03 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2024-09-06T14:15:03Z</dc:date>
    <item>
      <title>NC Law Requirements (SB 355)</title>
      <link>https://community.esri.com/t5/data-management-questions/nc-law-requirements-sb-355/m-p/1535259#M45372</link>
      <description>&lt;P&gt;On January 1, 2025 North Carolina local governments will have to comply with section 13 a &amp;amp; b of the North Carolina Farm Act of 2024 requiring a disclaimer on a splash screen with an agree button for all public facing GIS "tools". Not all of ESRI's web maps and apps have this option available. Especially on versions earlier that 11x.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We need a patch provided by ESRI to be able to comply with this law.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.ncleg.gov/Sessions/2023/Bills/Senate/PDF/S355v3.pdf" target="_blank" rel="noopener"&gt;https://www.ncleg.gov/Sessions/2023/Bills/Senate/PDF/S355v3.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Sep 2024 20:11:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/nc-law-requirements-sb-355/m-p/1535259#M45372</guid>
      <dc:creator>NAOMIPAUL</dc:creator>
      <dc:date>2024-09-04T20:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: NC Law Requirements (SB 355)</title>
      <link>https://community.esri.com/t5/data-management-questions/nc-law-requirements-sb-355/m-p/1535913#M45374</link>
      <description>&lt;P&gt;Hi. This is the &lt;U&gt;user&lt;/U&gt; forums, where users communicate with other users (and some Esri employees&amp;nbsp; who also use the software, but most not authorized to speak on behalf of the company). Communicating vendor requirements to Esri should be done through Tech Support and/or Customer Service and/or your local government representative. I would note that backfitting fundamental changes to software in Mature or Retired support status is not a likely outcome, especially if modern software in active support already has that capability.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2024 14:15:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/nc-law-requirements-sb-355/m-p/1535913#M45374</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2024-09-06T14:15:03Z</dc:date>
    </item>
  </channel>
</rss>

