forked from isc-rsingh/georss
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathsimple.html
120 lines (100 loc) · 5.98 KB
/
simple.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
<html>
<head>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="The GeoRSS specification simple encoding for adding geography to Atom and RSS feeds">
<title>GeoRSS Simple</title>
<link href='http://fonts.googleapis.com/css?family=Open+Sans' rel='stylesheet' type='text/css'><link href="global.css" type="text/css" rel="stylesheet">
</head>
<body>
<div class="nav"><a href="index.html">home</a> | <a href="overview.html">overview</a> | <a href="model.html">model</a> | <a href="gml.html">gml</a> | <a href="simple.html">simple</a> | <a href="w3c.html">W3C Geo</a> | <a href="atom.html">atom</a> | <a href="rdf_rss1.html">rdf/rss1</a> | <a href="implementations.html">implementations</a> | <a href="proposals.html">proposals</a></div>
<h4>GeoRSS ::<br/>Geographically Encoded Objects for RSS feeds</h4>
<h2>GeoRSS Simple</h2>
<p>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.</p>
<p>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.</p>
<p>Some publishers and users may prefer to separate lat/long pairs by a comma rather than whitespace. This is permissible in Simple; GeoRSS parsers should just treat commas as whitespace.</p>
<p>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.<p/>
<h2>Geometry</h2>
<h3> Point</h3>
<p>A point contains a single latitude-longitude pair, separated by whitespace. </p>
<blockquote>
<pre style="z-index: 3;"><span><?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"
<strong> xmlns:georss="http://www.georss.org/georss</strong>"
<span><strong>xmlns:gml="http://www.opengis.net/gml</strong>"</span>></span>
<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>tremor@quakelab.edu</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>
<span> <strong><georss:point>45.256 -71.92</georss:point>
</strong></span><<span>/entry>
</feed></span></pre>
</blockquote>
<h3> Line</h3>
<p>A line contains a space separated list of latitude-longitude pairs, with each pair separated by whitespace. There must be at least two pairs.</p>
<blockquote>
<pre><georss:line>45.256 -110.45 46.46 -109.48 43.84 -109.86</georss:line>
</pre>
</blockquote>
<h3>Polygon</h3>
<p>A polygon contains a space separated 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).</p>
<blockquote>
<pre><georss:polygon>
45.256 -110.45 46.46 -109.48 43.84 -109.86 45.256 -110.45
</georss:polygon>
</pre>
</blockquote>
<h3>Box</h3>
<p>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 separate latitude-longitude pairs, with each pair separated by whitespace. The first pair is the lower corner, the second is the upper corner.</p>
<blockquote>
<pre><georss:box>42.943 -71.032 43.039 -69.856</georss:box>
</pre>
</blockquote>
<h2>Additional Properties</h2>
<h3>Feature Type, Feature Name, and Relationship Tags</h3>
<p>The Feature Type, Feature Name, and Relationship tags are specified as GeoRSS elements.</p>
<blockquote>
<pre>
<georss:point>45.256 -110.45</georss:point>
<b><georss:featuretypetag>city</georss:featuretypetag>
<georss:relationshiptag>is-centered-at</georss:relationshiptag>
<georss:featurename>Podunk</georss:featurename></b>
</pre>
</pre>
</blockquote>
<h3>Elevation</h3>
<p>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.<p/>
<blockquote>
<pre>
<georss:point>45.256 -110.45</georss:point>
<b><georss:elev>313</georss:elev></b>
<georss:point>45.256 -110.45</georss:point>
<b><georss:floor>2</georss:floor></b>
</pre>
</blockquote>
<h3>Radius</h3>
<p>"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.<p/>
<blockquote>
<pre>
<georss:point>45.256 -110.45</georss:point>
<b><georss:radius>500</georss:radius></b>
</pre>
</blockquote>
<h3>GeoRSS Application Schema</h3>
<p>The application schema defines <georss:where> as the tag that signals geographic content--either in GeoRSS Simple or GML.</p>
<p><a href="http://www.georss.org/xml/1.1/georss.xsd">Here is our GeoRSS Application Schema</a>.</p>
</body>
</html>