<?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 Pure View Only Layers in ArcGIS Online Ideas</title>
    <link>https://community.esri.com/t5/arcgis-online-ideas/pure-view-only-layers/idi-p/1528107</link>
    <description>&lt;P&gt;I work for an agency that works to make data publicly viewable. We are limited by some use-contracts that these layers remain internal to our public tools, not exposed to others who might want to put the layers on their own web tools.&amp;nbsp;&lt;/P&gt;&lt;P&gt;To be able to remove the ability to reach the service definition / endpoint would be great in securing data and controlling its use to those intended.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This was spurred from a proprietary flood-model dataset that we can share the extent of, but the company that makes the product is apprehensive about their model being reverse engineered / used by those who have no legal ties to the product's agreement.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 27 Aug 2024 18:28:32 GMT</pubDate>
    <dc:creator>AndrewWhite2</dc:creator>
    <dc:date>2024-08-27T18:28:32Z</dc:date>
    <item>
      <title>Pure View Only Layers</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/pure-view-only-layers/idi-p/1528107</link>
      <description>&lt;P&gt;I work for an agency that works to make data publicly viewable. We are limited by some use-contracts that these layers remain internal to our public tools, not exposed to others who might want to put the layers on their own web tools.&amp;nbsp;&lt;/P&gt;&lt;P&gt;To be able to remove the ability to reach the service definition / endpoint would be great in securing data and controlling its use to those intended.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This was spurred from a proprietary flood-model dataset that we can share the extent of, but the company that makes the product is apprehensive about their model being reverse engineered / used by those who have no legal ties to the product's agreement.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2024 18:28:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/pure-view-only-layers/idi-p/1528107</guid>
      <dc:creator>AndrewWhite2</dc:creator>
      <dc:date>2024-08-27T18:28:32Z</dc:date>
    </item>
    <item>
      <title>Re: Pure View Only Layers</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/pure-view-only-layers/idc-p/1569764#M11994</link>
      <description>&lt;P&gt;Hey, for those that are trying to hide their service endpoint while still publicly displaying data in AGOL, here is the solution I used. Seems a bit cumbersome, and you do have to host the layers that you are trying to obscure. This made it a bit tricky for us as originally, we wanted to use a company's API to display the data.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.esri.com/en-us/knowledge-base/how-to-limit-access-to-secured-hosted-services-or-map-s-000017029" target="_blank"&gt;How To: Limit Access to Secured Hosted Services or Map Services in ArcGIS Online for Publi&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 14:45:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/pure-view-only-layers/idc-p/1569764#M11994</guid>
      <dc:creator>AndrewWhite2</dc:creator>
      <dc:date>2024-12-18T14:45:47Z</dc:date>
    </item>
  </channel>
</rss>

