<?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 Add support for time aware and multi-dimensional cached services (wmts/rest) in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/add-support-for-time-aware-and-multi-dimensional/idi-p/1144426</link>
    <description>&lt;P&gt;There is a lot of support for multi-dimensional data in the desktop environment but when publishing to ArcGIS Server and ArcGIS Image Server there is no ability to cache a multi-dimensional or time aware service.&lt;/P&gt;&lt;P&gt;The WMTS standard does have a dimension component, which has been implemented in other software.&lt;/P&gt;&lt;P&gt;My organisation (weather bureau) publishes forecast and observational data, vector and raster data types, to the public and gets billions of hits a year. Our radar service in our app delivers ~15 billion tiles per month. This amount of usage cannot be supported by a dynamic service, even using CRF.&lt;/P&gt;&lt;P&gt;To support this requirement we are currently using a third party software that adds a lot of overhead to our it support and complexity to our development of services.&lt;/P&gt;&lt;P&gt;The new ArcGIS Imagery for ArcGIS Online beta did seem to have some of this functionality as it prompted to add a tiled service from a multi-dimensional NetCDF or CRF.&lt;/P&gt;&lt;P&gt;Even adding the ability to request an image service in tiled mode to enable the use of a CDN would be great.&lt;/P&gt;&lt;P&gt;Example endpoint: &lt;A href="https://server.domain/arcgis/rest/services/radar/time/z/x/y.png" target="_blank"&gt;https://server.domain/arcgis/rest/services/radar/time/z/x/y.png&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 16 Feb 2022 00:57:20 GMT</pubDate>
    <dc:creator>MarkMenzel1</dc:creator>
    <dc:date>2022-02-16T00:57:20Z</dc:date>
    <item>
      <title>Add support for time aware and multi-dimensional cached services (wmts/rest)</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/add-support-for-time-aware-and-multi-dimensional/idi-p/1144426</link>
      <description>&lt;P&gt;There is a lot of support for multi-dimensional data in the desktop environment but when publishing to ArcGIS Server and ArcGIS Image Server there is no ability to cache a multi-dimensional or time aware service.&lt;/P&gt;&lt;P&gt;The WMTS standard does have a dimension component, which has been implemented in other software.&lt;/P&gt;&lt;P&gt;My organisation (weather bureau) publishes forecast and observational data, vector and raster data types, to the public and gets billions of hits a year. Our radar service in our app delivers ~15 billion tiles per month. This amount of usage cannot be supported by a dynamic service, even using CRF.&lt;/P&gt;&lt;P&gt;To support this requirement we are currently using a third party software that adds a lot of overhead to our it support and complexity to our development of services.&lt;/P&gt;&lt;P&gt;The new ArcGIS Imagery for ArcGIS Online beta did seem to have some of this functionality as it prompted to add a tiled service from a multi-dimensional NetCDF or CRF.&lt;/P&gt;&lt;P&gt;Even adding the ability to request an image service in tiled mode to enable the use of a CDN would be great.&lt;/P&gt;&lt;P&gt;Example endpoint: &lt;A href="https://server.domain/arcgis/rest/services/radar/time/z/x/y.png" target="_blank"&gt;https://server.domain/arcgis/rest/services/radar/time/z/x/y.png&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 00:57:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/add-support-for-time-aware-and-multi-dimensional/idi-p/1144426</guid>
      <dc:creator>MarkMenzel1</dc:creator>
      <dc:date>2022-02-16T00:57:20Z</dc:date>
    </item>
  </channel>
</rss>

