Getting an RSS feed to appear on a feature service

4053
1
10-24-2014 10:17 AM
JeremyMullins1
New Contributor III

I have an issue concerning my GEP not drawing information to my feature service. I believe it has something to do with the RSS feed itself, as my administrator and I have run through countless ideas of what the issue could be. I have a simple set up in my GeoEvent services: RSS Feed -> Field Mapper -> Feature Service Out. The URL for the RSS feed is http://www.ndbc.noaa.gov/data/latest_obs/pclf1.rss and what follows is the page source information:

 

 

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="https://community.esri.com/rss/ndbcrss.xsl"?>
<rss version="2.0" xmlns:georss="http://www.georss.org/georss" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>NDBC - Station PCLF1 - 8729840 - Pensacola, FL Observations</title>
<description><![CDATA[This feed shows recent marine weather observations from Station PCLF1.]]></description>
<link>http://www.ndbc.noaa.gov/</link>
<pubDate>Tue, 21 Oct 2014 20:29:09 UT</pubDate>
<lastBuildDate>Tue, 21 Oct 2014 20:29:09 UT</lastBuildDate>
<ttl>30</ttl>
<language>en-us</language>
<managingEditor>webmaster.ndbc@noaa.gov</managingEditor>
<webMaster>webmaster.ndbc@noaa.gov</webMaster>
<image>
<url>http://weather.gov/images/xml_logo.gif</url>
<title>NOAA - National Weather Service</title>
<link>http://www.ndbc.noaa.gov/</link>
</image>
<item>
<pubDate>Tue, 21 Oct 2014 20:29:09 UT</pubDate>
<title>Station PCLF1 - 8729840 - Pensacola, FL</title>
<description><![CDATA[
<strong>October 21, 2014 3:00 pm CDT</strong><br />
<strong>Location:</strong> 30.404N 87.211W<br />
<strong>Wind Direction:</strong> ENE (70&#176;)<br />
<strong>Wind Speed:</strong> 2.9 knots<br />
<strong>Wind Gust:</strong> 7.0 knots<br />
<strong>Atmospheric Pressure:</strong> 29.96 in (1014.7 mb)<br />
<strong>Pressure Tendency:</strong> -0.08 in (-2.6 mb)<br />
<strong>Air Temperature:</strong> 80.6&#176;F (27.0&#176;C)<br />
<strong>Water Temperature:</strong> 73.6&#176;F (23.1&#176;C)<br />
]]></description>
<link>http://www.ndbc.noaa.gov/station_page.php?station=pclf1</link>
<guid>http://www.ndbc.noaa.gov/station_page.php?station=pclf1&amp;ts=1413921600</guid>
<georss:point>30.404 -87.211</georss:point>
</item>
</channel>
</rss>

 

While this isn't formatted (there are indentations) exactly as in the browser, I think my point is still valid. When my GeoEvent Definition (GED) is created, I get title, link, guid, geo_lat, geo_long, and geometry. What I want to look at is wind speed and direction (using the rotation of the symbol in the web map options to signify which direction it is going - this angle is shown next to the "ENE" in the example above as the number "70"; what follows appears to be syntax for the degree symbol). I have tried looking into the Field Calculator RegEx option, but it doesn't seem like it will do the trick.

 

So basically what happens is that I get RSS feed data, it goes through the GeoEvent Service and the Monitor page shows an output to the Feature Service. However, when I try to view the feature service in the Operations Dashboard or do a simple GET query on the REST endpoint of the feature layer, I get no results and no symbols. I believe the presence of <strong> before each field may be causing an issue. It appears exactly like this when I attempt to output the information to a TCP Socket. I hope this makes sense - I am new to this so forgive my misappropriation for any definitions.
Reply
0 Kudos
1 Reply
ThomasPaschke
New Contributor III

Hi Jeremy,

your suspicion is correct. The embedded HTML presents some issue, since ArcGIS for Server would discover and reject those.

It should be possible to get the values for wind speed and direction using the Field Calculator RegEx though. Try a lookbehind for the field name and the html tag to discover the value. Something like:

(?<=ENE\s\()\d* for the direction

(?<=Wind\sSpeed\:\<\/strong\>\s)\d+\.\d+

Alternative you can use string calculations or a combination of both. I unfortunately do not have time to verify what works best right now.

I hope that helps.

Best,

Thomas