<?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 GeoEvent Processor - add email parsing as an input in ArcGIS GeoEvent Server Ideas</title>
    <link>https://community.esri.com/t5/arcgis-geoevent-server-ideas/geoevent-processor-add-email-parsing-as-an-input/idi-p/939565</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like to be able to take an incoming email and use it as an input to a GeoEvent. Furthermore, it would be great if GEP could parse the email. One example of how I have seen this done is sending a sample with email with a set format and highlighting the sections of the email and configuring a field name for the highlight section.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 May 2015 19:57:31 GMT</pubDate>
    <dc:creator>SimonMorgan</dc:creator>
    <dc:date>2015-05-08T19:57:31Z</dc:date>
    <item>
      <title>GeoEvent Processor - add email parsing as an input</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-ideas/geoevent-processor-add-email-parsing-as-an-input/idi-p/939565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like to be able to take an incoming email and use it as an input to a GeoEvent. Furthermore, it would be great if GEP could parse the email. One example of how I have seen this done is sending a sample with email with a set format and highlighting the sections of the email and configuring a field name for the highlight section.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 May 2015 19:57:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-ideas/geoevent-processor-add-email-parsing-as-an-input/idi-p/939565</guid>
      <dc:creator>SimonMorgan</dc:creator>
      <dc:date>2015-05-08T19:57:31Z</dc:date>
    </item>
    <item>
      <title>Re: GeoEvent Processor - add email parsing as an input</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-ideas/geoevent-processor-add-email-parsing-as-an-input/idc-p/939566#M43</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I would add sms messages as an input. My example would be texting an action and a facility id number, e.g. "Close VAL4235" would close valve 4235.

&lt;!-- content transformation source ID: 00aE000000I99yV --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Apr 2016 15:00:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-ideas/geoevent-processor-add-email-parsing-as-an-input/idc-p/939566#M43</guid>
      <dc:creator>SamJenkins1</dc:creator>
      <dc:date>2016-04-11T15:00:35Z</dc:date>
    </item>
    <item>
      <title>Re: GeoEvent Processor - add email parsing as an input</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-ideas/geoevent-processor-add-email-parsing-as-an-input/idc-p/939567#M44</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did this using a custom extension. Open sourced the code, it reads and parses emails from a CBYD system&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://github.com/quick6black/CBYD-Email-for-geoevent" title="https://github.com/quick6black/CBYD-Email-for-geoevent"&gt;GitHub - quick6black/CBYD-Email-for-geoevent: GeoEvent Processor input connector to Read and parse CBYD emails&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Aug 2018 19:13:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-ideas/geoevent-processor-add-email-parsing-as-an-input/idc-p/939567#M44</guid>
      <dc:creator>AaronNash1</dc:creator>
      <dc:date>2018-08-02T19:13:51Z</dc:date>
    </item>
  </channel>
</rss>

