<?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: File Geodatabase API 1.4 now posted at Esri Downloads in File Geodatabase API Questions</title>
    <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603426#M976</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It appears that there has been a change to the licensing, at least with respect that the Apache 2.0 license is in the license/ folder.&amp;nbsp; The E204_E300 license document in the 1.3 releases is dated 2012-09-06, while the E204_E300 bound to the download site is dated 2013-04-26.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not a lawyer, and I don't speak as a legal representative of Esri (the license speaks of a "signed" alternative anyway), but to the best of my understanding, the E204_E300 license is intended to protect API distribution (the include files and link libraries) but that the runtime libraries (in the Windows distributions, the files in the "bin" directory, not the "lib"), are freely distributable with applications that use them.&amp;nbsp; That is, you can code with the API, and make royalty-free applications that reference and distribute the runtime DLLs, but you cannot redistribute the API itself without written permission.&amp;nbsp; If you distribute source that could be compiled using the SDK, then others would need to license the SDK themselves in order to compile your source.&amp;nbsp; Which is all pretty much standard in the COTS world (except for the runtime distribution, which is atypical [and pretty cool]).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've contacted Contracts to get clarification on this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 21 Mar 2015 16:34:28 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2015-03-21T16:34:28Z</dc:date>
    <item>
      <title>File Geodatabase API 1.4 now posted at Esri Downloads</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603424#M974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The wait is over! Head on over to &lt;A href="http://www.esri.com/apps/products/download/index.cfm?fuseaction=download.all#File_Geodatabase_API_1.4" title="http://www.esri.com/apps/products/download/index.cfm?fuseaction=download.all#File_Geodatabase_API_1.4"&gt;Esri Downloads&lt;/A&gt; !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WHAT'S NEW:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Support for reading Compressed fgdb data.. (NIM071731)&lt;/LI&gt;&lt;LI&gt;Custom projection support. (NIM073951)&lt;/LI&gt;&lt;LI&gt;Non-XML creation of tables.&lt;/LI&gt;&lt;LI&gt;The field list is now honored on Searches, only returning the requested fields. (NIM082242)&lt;/LI&gt;&lt;LI&gt;Upgrade to libxlt (1.1.28) to pickup fix for memory leak. (NIM098151)&lt;/LI&gt;&lt;LI&gt;Added Compact geodatabase (NIM098323).&lt;/LI&gt;&lt;LI&gt;MS Visual Studio 2013 support.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Mar 2015 18:51:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603424#M974</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2015-03-20T18:51:45Z</dc:date>
    </item>
    <item>
      <title>Re: File Geodatabase API 1.4 now posted at Esri Downloads</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603425#M975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's great news Vince.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the license agreement for the two binary libraries? Can they be bundled in an application or do they require end users to download the binaries themselves?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I couldn't figure it out from the license directory in the downloads. Most of that seems to be reference to libraries that you use to build your binaries or the sample source code.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Mar 2015 23:57:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603425#M975</guid>
      <dc:creator>PaulAustin</dc:creator>
      <dc:date>2015-03-20T23:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: File Geodatabase API 1.4 now posted at Esri Downloads</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603426#M976</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It appears that there has been a change to the licensing, at least with respect that the Apache 2.0 license is in the license/ folder.&amp;nbsp; The E204_E300 license document in the 1.3 releases is dated 2012-09-06, while the E204_E300 bound to the download site is dated 2013-04-26.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not a lawyer, and I don't speak as a legal representative of Esri (the license speaks of a "signed" alternative anyway), but to the best of my understanding, the E204_E300 license is intended to protect API distribution (the include files and link libraries) but that the runtime libraries (in the Windows distributions, the files in the "bin" directory, not the "lib"), are freely distributable with applications that use them.&amp;nbsp; That is, you can code with the API, and make royalty-free applications that reference and distribute the runtime DLLs, but you cannot redistribute the API itself without written permission.&amp;nbsp; If you distribute source that could be compiled using the SDK, then others would need to license the SDK themselves in order to compile your source.&amp;nbsp; Which is all pretty much standard in the COTS world (except for the runtime distribution, which is atypical [and pretty cool]).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've contacted Contracts to get clarification on this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Mar 2015 16:34:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603426#M976</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2015-03-21T16:34:28Z</dc:date>
    </item>
    <item>
      <title>Re: File Geodatabase API 1.4 now posted at Esri Downloads</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603427#M977</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The license displayed in the Download dialog in incorrect and will be changed shortly. At 1.4 we are using the Apache license. The license included in the license directory in the download is the Apache license. I will post more information about the 1.4 release when we get the license issue resolved.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Mar 2015 22:22:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603427#M977</guid>
      <dc:creator>LanceShipman</dc:creator>
      <dc:date>2015-03-23T22:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: File Geodatabase API 1.4 now posted at Esri Downloads</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603428#M978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The license issue has been corrected. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Mar 2015 17:29:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603428#M978</guid>
      <dc:creator>LanceShipman</dc:creator>
      <dc:date>2015-03-25T17:29:51Z</dc:date>
    </item>
    <item>
      <title>Re: File Geodatabase API 1.4 now posted at Esri Downloads</title>
      <link>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603429#M979</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are there any code samples showing how to get and insert arcs? I didn't see any in the samples.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Aug 2015 12:33:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/file-geodatabase-api-questions/file-geodatabase-api-1-4-now-posted-at-esri/m-p/603429#M979</guid>
      <dc:creator>DonnyVelazquez</dc:creator>
      <dc:date>2015-08-13T12:33:19Z</dc:date>
    </item>
  </channel>
</rss>

