Revision as of 19:23, 28 November 2006

Geo cheatsheet

1 - Single occurrence required

2 - single occurrence optional

If latitude is present, so MUST be longitude, and vice versa.
If the secondary classes are omitted, the two values MUST be comma separated and latitude MUST be first:<span class=geo">37.386013,-122.082932</span>
The same number of decimal places SHOULD be used in each value.

Geo
Geo cheatsheet
Geo examples
geo formats - previous/other attempts at geo related formats
Geo brainstorming - brainstorms and other explorations relating to Geo (and Geo in hCard).
- see also hCard brainstorming
Geo advocacy - encourage others to use Geo.
Geo examples in the wild
Geo forms part of hcard, so please use:
- hCard FAQ. If you have any questions about Geo, check the hCard FAQ.
- hCard feedback
- hCard issues
location-formats - research which led to the development of Geo.
proposed extensions
- geo-extension-nonWGS84 - extend Geo for representing coordinates on other planets, moons etc.; and for other terrestrial schema
- geo-extension-waypoints - extend Geo for representing: sets of waypoints; tracks; routes; and boundaries
Geo profile - draft

@@ Line 13: / Line 13: @@
 ==Notes==
 *If latitude is present, so MUST be longitude, and vice versa.
-*If the secondary classes are omitted, the two values MUST be comma separated and latitude MUST be first:<code><nowiki><span class=geo">37.386013,-122.082932</span></nowiki></code>
+*If the secondary classes are omitted, the two values MUST be comma <!-- OR IS IT A SEMICOLON? Not specified on [[geo]] --> separated and latitude MUST be first:<code><nowiki><span class=geo">37.386013,-122.082932</span></nowiki></code>
 *The same number of decimal places SHOULD be used in each value.
 ==Related pages==
 {{geo}}