<?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: Licenses needed to use and publish oriented Imagery in Oriented Imagery Classic</title>
    <link>https://community.esri.com/t5/oriented-imagery-classic/licenses-needed-to-use-and-publish-oriented/m-p/1173274#M334</link>
    <description>&lt;P&gt;Thanks Emily!&lt;/P&gt;</description>
    <pubDate>Thu, 12 May 2022 12:14:14 GMT</pubDate>
    <dc:creator>BrunoGomesdeSouza</dc:creator>
    <dc:date>2022-05-12T12:14:14Z</dc:date>
    <item>
      <title>Licenses needed to use and publish oriented Imagery</title>
      <link>https://community.esri.com/t5/oriented-imagery-classic/licenses-needed-to-use-and-publish-oriented/m-p/1172975#M332</link>
      <description>&lt;P&gt;Hey Guys,&lt;/P&gt;&lt;P&gt;Could you help me please?&lt;/P&gt;&lt;P&gt;Here in Brazil our team are working with oriented imagery. We saw your article and replicate all functionalities.&lt;/P&gt;&lt;P&gt;But we have a doubt about licensing.&lt;/P&gt;&lt;P&gt;Our clients have a lot of 360º images to put inside oriented imagery.&lt;BR /&gt;We found an extension to ArcGIS Pro and we at the same time built a script to put geographical info inside photos exif.&lt;/P&gt;&lt;P&gt;At the end we could upload all 360º images.&lt;/P&gt;&lt;P&gt;As ESRI distributor we have a lot of licenses attributed for our creator users and we need to understand what kind of licenses are needed for our clients.&lt;BR /&gt;If you could help us to understand what licenses we need to do all the process using AcGIS Pro or direct us to the right person to talk will be a big deal.&lt;/P&gt;&lt;P&gt;Thank you so much&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2022 19:00:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/oriented-imagery-classic/licenses-needed-to-use-and-publish-oriented/m-p/1172975#M332</guid>
      <dc:creator>BrunoGomesdeSouza</dc:creator>
      <dc:date>2022-05-11T19:00:24Z</dc:date>
    </item>
    <item>
      <title>Re: Licenses needed to use and publish oriented Imagery</title>
      <link>https://community.esri.com/t5/oriented-imagery-classic/licenses-needed-to-use-and-publish-oriented/m-p/1173103#M333</link>
      <description>&lt;P&gt;Hi Bruno,&lt;/P&gt;&lt;P&gt;To use the Oriented Imagery add-in for ArcGIS Pro add-in requires any ArcGIS Pro license. Publishing or using the oriented imagery catalog in ArcGIS Online requires an account with the appropriate role enabled (&lt;A href="https://doc.arcgis.com/en/arcgis-online/reference/roles.htm" target="_blank"&gt;https://doc.arcgis.com/en/arcgis-online/reference/roles.htm&lt;/A&gt;). For example, to publish an oriented imagery catalog to ArcGIS Online requires a user account with the publisher role (or greater). To view an oriented imagery catalog, create an oriented imagery app, or edit a feature service would all follow the same user role requirements for oriented imagery as any other ArcGIS Online content.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2022 22:49:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/oriented-imagery-classic/licenses-needed-to-use-and-publish-oriented/m-p/1173103#M333</guid>
      <dc:creator>EmilyWindahl</dc:creator>
      <dc:date>2022-05-11T22:49:04Z</dc:date>
    </item>
    <item>
      <title>Re: Licenses needed to use and publish oriented Imagery</title>
      <link>https://community.esri.com/t5/oriented-imagery-classic/licenses-needed-to-use-and-publish-oriented/m-p/1173274#M334</link>
      <description>&lt;P&gt;Thanks Emily!&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2022 12:14:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/oriented-imagery-classic/licenses-needed-to-use-and-publish-oriented/m-p/1173274#M334</guid>
      <dc:creator>BrunoGomesdeSouza</dc:creator>
      <dc:date>2022-05-12T12:14:14Z</dc:date>
    </item>
  </channel>
</rss>

