Product Delivery Methods
This is a brief description of the data transfer methodologies AccuWeather, Inc. has in place and how they work for AccuNet subscribers. The purpose of this is to list the options and to discuss the pros and cons of each.
FTP PULL: The client logs onto the AccuWeather system and downloads data. AccuWeather provides the subscriber with a username, password and a separate directory. AccuWeather gathers the requested data in large files at predetermined times. For example, 5-day forecasts would be in "5day.txt" and current conditions in "CUR.TXT." The subscriber would then need to write scripts to initiate the transfer. This is our preferred methodology because it is allows for the greatest control and tracking. Unfortunately, some subscribers have trouble configuring their FTP client to work with our system, and it is not the best method for time-sensitive products such as watches and warnings.
FTP PUSH: AccuWeather's system logs onto the subscriber's system and places files in it. The subscriber needs to provide AccuWeather with an IP address or host name, username, password, and the directory to place the data. The subscriber would also need to configure the directory in a manner that gives AccuWeather write, delete, and overwrite privileges. AccuWeather would provide the subscriber a list of the IP addresses from which we push, and would then send data in the same large files that would be used in a pull scenario. This is the best method for more time-sensitive products such as watches and warnings. However, it is more difficult to diagnose problems with content delivery, and some system administrators are reluctant to open their firewalls to all the IP addresses that are used.
HTTPGet: This method is exactly the same as FTP PULL, except the subscriber uses a browser to download data rather than using a special FTP client. AccuWeather provides the subscriber with a unique URL that has the username and password embedded. This is becoming increasingly popular because many subscribers are using a content management product called ColdFusion that cannot perform an FTP transfer. (The term "HTTPget" is actually a ColdFusion command.) Any client who is set up for FTP Pull can use HTTPget. AccuWeather generally discourages this method for three reasons: (1) it is not as efficient as a true FTP Pull; (2) it represents a potential security breach in that the URL contains a valid username and password; (3) we cannot perform accurate tracking of client usage, which makes it more difficult to track potential problems.
Email: AccuWeather bundles content and sends data as email messages or attachments. The email method is similar to the FTP Push. This method is strongly discouraged because email is an extremely inefficient and unreliable delivery medium. Also, many subscriber systems have a maximum size for an email message, so data is likely to be truncated or undeliverable.
Hosting: All the data resides at AccuWeather's end. AccuWeather gives the subscriber a special "partner" code, which allows the subscriber to access a custom section of our site. This allows the subscriber to access their data "on demand" or on a "per query" basis. In other words, if a user entered a zip code, the subscriber would ask AccuWeather's server for data for that zip code. A document would then be returned to the subscriber with just that data. This document can be in the form of XML data or a full HTML page that matches the subscriber's template. Hosting is the best choice for clients who lack the technical knowledge or infrastructure to support AccuWeather content on their side.
Data Formats for AccuNet Products
This document describes some of the common file formats for most AccuNet products, as well as some of the pros and cons for each.
Graphical Content:
-GIF:
Due to a licensing issue, we can only provide static content (icons, etc.) as .GIFs. All other graphical content (radar, satellite, etc.) may only be .JPG or .PNG
-Animated Images:
If the images are hosted on AccuWeather.com, they can be animated .GIF images. However, delivered to subscribers can only be .PNG or .JPG. These formats do not support animation layers, and instead are animated by cycling through a series of images, typically by using JavaScript. AccuWeather, Inc., can provide a template script that subscribers can modify for use on their sites.
Text Content:
-Plain/Delimited Text (.TXT):
Data is delivered in large files, with a delimiter (typically the vertical bar) between elements. This method allows for a large amount of data to be sent in a small file, but requires scripting on the subscriber's end to parse the file.
-Comma-separated values (.CSV):
These are delimited text files, with a comma acting as the delimiter. .CSV files can be loaded directly into spreadsheet applications.
-XML:
Data is encapsulated using XML. We have a standard DTD for most products, and we can generate the data using a client-supplied schema for an additional fee. The advantage to this method is that there are many tools which can read XML and load the data from it into a web site or a database. The disadvantage is that for large datasets (for example the 5-day forecast for all US zip codes) the files can be very large, which uses more system resources and time to build, transfer, and parse.
-HTML/xHTML:
We deliver finished HTML pages, or "include" files for each location, for all areas in which the subscriber receives data. We can design the page ourselves, or the subscriber can send us the HTML template they want us to use. If the subscriber designs the page, they will need to send us an HTML representation of the finished product so we can write code to place data elements in the correct place. With HTML/xHTML there is very little processing to be done on the subscriber side, but there is greater cost associated with it, and it takes longer to make changes.