The Simple serialization of GeoRSS is designed to be maximally concise, in both representation and conception. Each of the four GeoRSS objects require only a single tag.
This simplicity comes at the cost of direct upward compatibility with GML. However, it is straightforward to devise transformations from this Simple serialization to the GML serialization through the GML model. For many needs, GeoRSS Simple will be sufficient.
Some publishers and users may prefer to seperate lat/long pairs by a comma rather than whitespace. This is permissible in Simple; GeoRSS parsers should just treat commas as whitespace.
The first example shows GeoRSS Simple within an Atom 1.0 entry. This serialization applies just as well to an RSS 2.0 or RSS 1.0 item; it can also be associated with the entire feed. The rest of the examples show only the encoding of the objects and attributes.
A point contains a single latitude-longitude pair, separated by whitespace.
<?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom" xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"> <title>Earthquakes</title> <subtitle>International earthquake observation labs</subtitle> <link href="http://example.org/"/> <updated>2005-12-13T18:30:02Z</updated> <author> <name>Dr. Thaddeus Remor</name> <email>firstname.lastname@example.org</email> </author> <id>urn:uuid:60a76c80-d399-11d9-b93C-0003939e0af6</id> <entry> <title>M 3.2, Mona Passage</title> <link href="http://example.org/2005/09/09/atom01"/> <id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id> <updated>2005-08-17T07:02:32Z</updated> <summary>We just had a big one.</summary> <georss:point>45.256 -71.92</georss:point> </entry> </feed>
A line contains a space seperated list of latitude-longitude pairs, with each pair separated by whitespace. There must be at least two pairs.
<georss:line>45.256 -110.45 46.46 -109.48 43.84 -109.86</georss:line>
A polygon contains a space seperated list of latitude-longitude pairs, with each pair separated by whitespace. There must be at least four pairs, with the last being identical to the first (so a polygon has a minimum of three actual points).
<georss:polygon> 45.256 -110.45 46.46 -109.48 43.84 -109.86 45.256 -110.45 </georss:polygon>
A bounding box is a rectangular region, often used to define the extents of a map or a rough area of interest. A box contains two space seperate latitude-longitude pairs, with each pair separated by whitespace. The first pair is the lower corner, the second is the upper corner.
<georss:box>42.943 -71.032 43.039 -69.856</georss:box>
The Feature Type, Feature Name, and Relationship tags are specified as GeoRSS elements.
<georss:point>45.256 -110.45</georss:point> <georss:featuretypetag>city</georss:featuretypetag> <georss:relationshiptag>is-centered-at</georss:relationshiptag> <georss:featurename>Podunk</georss:featurename>
Elevation, specified in GeoRSS elements, can be expressed as "elev" or "floor". elev is meant to contain "common" GPS elevation readings, i.e. height in meters from the WGS84 ellipsoid, which is a reading that should be easy to get from any GPS device. floor is meant to contain the floor number of a building. In some countries the numbering is different than in other countries, but since we'll know the location of the building, it should be fairly unambiguous.
<georss:point>45.256 -110.45</georss:point> <georss:elev>313</georss:elev> <georss:point>45.256 -110.45</georss:point> <georss:floor>2</georss:floor>
"radius" indicates the size in meters of a radius or buffer around the geometry object, for example, radius of circular area around a point geometry.
<georss:point>45.256 -110.45</georss:point> <georss:radius>500</georss:radius>
The application schema defines <georss:where> as the tag that signals geographic content--either in GeoRSS Simple or GML.
Here is our GeoRSS Application Schema.