<?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: Does GeoEvent work with Fleetmatics? in ArcGIS GeoEvent Server Questions</title>
    <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/does-geoevent-work-with-fleetmatics/m-p/467862#M2064</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anything's possible. &amp;nbsp;I know, I know, you just rolled your eyes, but hear me out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The key here is to not think of the vendors' ability or non-ability to work directly with GeoEvent. &amp;nbsp;Unless the vendor, or an otherwise interested party, creates the GeoEvent connectors, it's impossible for the Esri GeoEvent team to make and maintain a connector for every possible vendor - it's just not a realistic development and maintenance feasibility.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So then what's the key? &amp;nbsp;The key is to find out lower level details about these vendors' APIs and data formats. &amp;nbsp;How does a developer or integrator communicate with the vendors' products/APIs - HTTP? &amp;nbsp;TCP? &amp;nbsp;Web socket? &amp;nbsp;UDP? &amp;nbsp;What is the format of the actual data? &amp;nbsp;Comma-separated fields? Tab-separated fields? &amp;nbsp;XML? &amp;nbsp;JSON?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GeoEvent ships with native support for a bunch of industry standard transport mechanisms (HTTP, TCP, UDP, Web socket, etc) as well as native support for a a bunch of data formats (CSV, JSON, etc). &amp;nbsp;If a vendor's connector doesn't exist natively (which is most likely the case), but&amp;nbsp;you find out their API is REST-based and returns tab-separated data, then you could "marry-up" the HTTP transport with the Text adapter and make a new GeoEvent connector with no development required. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are possibilities to integrate vendors' products APIs with GeoEvent, but I won't go into it here. &amp;nbsp;Anybody interested in hearing more can contact me if desired.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps clarify some things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark Bramer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 27 Sep 2016 15:06:53 GMT</pubDate>
    <dc:creator>MarkBramer</dc:creator>
    <dc:date>2016-09-27T15:06:53Z</dc:date>
    <item>
      <title>Does GeoEvent work with Fleetmatics?</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/does-geoevent-work-with-fleetmatics/m-p/467861#M2063</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are currently using Fleetmatics to track our field vehicles and would like to integrate this into our web maps. They have their own API that allows real time tracking so I figured that it would work with the geoevent extension. However, after talking with our fleetmatics rep they said it was not possible. They also didn't know what ESRI was either so I am a little bit skeptical. Just want to reach out and see if anyone has looked into using this particular software with the extension before?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Sep 2016 15:40:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-questions/does-geoevent-work-with-fleetmatics/m-p/467861#M2063</guid>
      <dc:creator>ShawnHibbs</dc:creator>
      <dc:date>2016-09-23T15:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: Does GeoEvent work with Fleetmatics?</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/does-geoevent-work-with-fleetmatics/m-p/467862#M2064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anything's possible. &amp;nbsp;I know, I know, you just rolled your eyes, but hear me out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The key here is to not think of the vendors' ability or non-ability to work directly with GeoEvent. &amp;nbsp;Unless the vendor, or an otherwise interested party, creates the GeoEvent connectors, it's impossible for the Esri GeoEvent team to make and maintain a connector for every possible vendor - it's just not a realistic development and maintenance feasibility.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So then what's the key? &amp;nbsp;The key is to find out lower level details about these vendors' APIs and data formats. &amp;nbsp;How does a developer or integrator communicate with the vendors' products/APIs - HTTP? &amp;nbsp;TCP? &amp;nbsp;Web socket? &amp;nbsp;UDP? &amp;nbsp;What is the format of the actual data? &amp;nbsp;Comma-separated fields? Tab-separated fields? &amp;nbsp;XML? &amp;nbsp;JSON?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GeoEvent ships with native support for a bunch of industry standard transport mechanisms (HTTP, TCP, UDP, Web socket, etc) as well as native support for a a bunch of data formats (CSV, JSON, etc). &amp;nbsp;If a vendor's connector doesn't exist natively (which is most likely the case), but&amp;nbsp;you find out their API is REST-based and returns tab-separated data, then you could "marry-up" the HTTP transport with the Text adapter and make a new GeoEvent connector with no development required. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are possibilities to integrate vendors' products APIs with GeoEvent, but I won't go into it here. &amp;nbsp;Anybody interested in hearing more can contact me if desired.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps clarify some things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark Bramer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Sep 2016 15:06:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-questions/does-geoevent-work-with-fleetmatics/m-p/467862#M2064</guid>
      <dc:creator>MarkBramer</dc:creator>
      <dc:date>2016-09-27T15:06:53Z</dc:date>
    </item>
  </channel>
</rss>

