ScenarioThis example demonstrates how FME Server can be used to:
How It WorksAs with most FME Server scenarios, a workspace is designed using FME Desktop (Workbench) and uploaded to FME Server - in this case three workspaces.
WorkspacesTweet Search and Archive (D008-tweet-archiver.fmw)
The first workspace searches for tweets that contain the text @safesoftware OR @fmedoctors OR @fmeevangelist OR @betabuilder. If a tweet isn't geotagged, an attempt is made to give the tweet a location by geocoding the tweeter's profile location. Ultimately, the tweets are output into a database for retrieval by another workspace that outputs KML. This intermediate or caching database is required to avoid exceeding the Twitter API rate limit of 150 requests per hour.
KML Output (D008-tweet-kml.fmw)
The second workspace reads the cached tweets, styles each tweet for KML and then writes them out to KML. This workspace is published to FME Server and registered with the KML Network Link Service.
Tweet Search and Archive Runner (D008-tweet-archive-runner.fmw) A third workspace uses the FMEServerJobSubmitter transformer to run the Tweet Search and Archive workspace on FME Server. The workspace is run at a set interval using a bat file. The interval is set to a value that won't exceed the Twitter API rate limit of 150 requests per hour.
Setting up the ExampleTo actually set up and run the example on your own system requires a certain set of software and setup.
Geotagged Tweets in KML
Article Number: 000001483 - Last Modified: Jan 8, 2015
This article describes how FME Server can be used to search, geocode, store and serve tweets as KML.