<?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: Best practices for serving contours to end users in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/best-practices-for-serving-contours-to-end-users/m-p/1590976#M93577</link>
    <description>&lt;P&gt;are you working with a "chess-board" of DEM GeoTiff files in a mosaic dataset?&lt;/P&gt;</description>
    <pubDate>Fri, 28 Feb 2025 22:10:56 GMT</pubDate>
    <dc:creator>BillFox</dc:creator>
    <dc:date>2025-02-28T22:10:56Z</dc:date>
    <item>
      <title>Best practices for serving contours to end users</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/best-practices-for-serving-contours-to-end-users/m-p/1590896#M93574</link>
      <description>&lt;P&gt;Hi, I'm curious how everyone is serving contours to your end users, if you aren't pointing people to a public rest service at the state level or something similar.&lt;/P&gt;&lt;P&gt;Vector Tiles? Cached map service? Straight feature service?&lt;/P&gt;&lt;P&gt;I'm looking at publishing vector tiles because the area I'm in has a lot of elevation changes so contours at anything below a 10-20ft interval are so dense that performance is terrible for a regular feature service.&lt;/P&gt;&lt;P&gt;Are vector tiles the way to go or should I be looking at something else? Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2025 19:53:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/best-practices-for-serving-contours-to-end-users/m-p/1590896#M93574</guid>
      <dc:creator>AVLGISADMIN</dc:creator>
      <dc:date>2025-02-28T19:53:18Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for serving contours to end users</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/best-practices-for-serving-contours-to-end-users/m-p/1590976#M93577</link>
      <description>&lt;P&gt;are you working with a "chess-board" of DEM GeoTiff files in a mosaic dataset?&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2025 22:10:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/best-practices-for-serving-contours-to-end-users/m-p/1590976#M93577</guid>
      <dc:creator>BillFox</dc:creator>
      <dc:date>2025-02-28T22:10:56Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for serving contours to end users</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/best-practices-for-serving-contours-to-end-users/m-p/1593807#M93810</link>
      <description>&lt;P&gt;No I'm working with a dense contour feature class. They are 1ft contours which is what my end users are asking for but given the mountainous region we are in its a lot of data and vertices. I was thinking of using generalize to reduce the number of vertices, but I'm not sure if I can do that and stay within tolerance for 1ft contours, maybe I can go up to 2ft.&lt;/P&gt;&lt;P&gt;If you have any workflow advice I'd be happy to hear it, I tried creating a vector tile set to upload to agol but it seemed like it didnt work correctly, it would only draw in certain sections of the contours.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 14:32:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/best-practices-for-serving-contours-to-end-users/m-p/1593807#M93810</guid>
      <dc:creator>AVLGISADMIN</dc:creator>
      <dc:date>2025-03-10T14:32:56Z</dc:date>
    </item>
  </channel>
</rss>

