<?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 Better Attachments REST API (Batch and Image Resizing) in Developers Ideas</title>
    <link>https://community.esri.com/t5/developers-ideas/better-attachments-rest-api-batch-and-image/idi-p/934716</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In our company we ended up having to spend a lot of resources resizing image attachments after downloading them using the REST API, I feel like this is an expected feature of any image-serving API that is severely missing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also another major issue is that you have to make a different request for every feature to get it's attachment info, why can't we just send an array of OIDs and get an array of attachment infos? Also this has spawned a temporary 503 error on your CloudFront that took some time to get solved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, in short :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Endpoint to get attachment image resized&lt;/P&gt;&lt;P&gt;- Endpoint to get batch attachments&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Mar 2019 14:36:32 GMT</pubDate>
    <dc:creator>GeoprocessamentoCarusoJR</dc:creator>
    <dc:date>2019-03-29T14:36:32Z</dc:date>
    <item>
      <title>Better Attachments REST API (Batch and Image Resizing)</title>
      <link>https://community.esri.com/t5/developers-ideas/better-attachments-rest-api-batch-and-image/idi-p/934716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In our company we ended up having to spend a lot of resources resizing image attachments after downloading them using the REST API, I feel like this is an expected feature of any image-serving API that is severely missing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also another major issue is that you have to make a different request for every feature to get it's attachment info, why can't we just send an array of OIDs and get an array of attachment infos? Also this has spawned a temporary 503 error on your CloudFront that took some time to get solved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, in short :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Endpoint to get attachment image resized&lt;/P&gt;&lt;P&gt;- Endpoint to get batch attachments&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2019 14:36:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-ideas/better-attachments-rest-api-batch-and-image/idi-p/934716</guid>
      <dc:creator>GeoprocessamentoCarusoJR</dc:creator>
      <dc:date>2019-03-29T14:36:32Z</dc:date>
    </item>
  </channel>
</rss>

