geo-cheatsheet: Difference between revisions
Jump to navigation
Jump to search
AndyMabbett (talk | contribs) (→Notes: WGS84) |
AndyMabbett (talk | contribs) (→Notes: correction (pending firther clarification on mailing list)) |
||
| Line 11: | Line 11: | ||
==Notes== | ==Notes== | ||
*If latitude is present, so MUST be longitude, and vice versa. | *If latitude is present, so MUST be longitude, and vice versa. | ||
*If the secondary classes are omitted, the two values MUST be | *If the secondary classes are omitted, the two values MUST be separated by a semicolon 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. | *The same number of decimal places SHOULD be used in each value. | ||
*Coordinates use the datum of [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84]. | *Coordinates use the datum of [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84]. | ||
Revision as of 14:48, 17 December 2006
geo cheatsheet
Properties (Class Names)
- geo {1}
- latitude?
- longitude?
Key
Based on Perl's standard quantifiers:
| bold {1} | MUST be present exactly once |
| italic* | OPTIONAL, and MAY occur more than once |
| + | MUST be present, and MAY occur more than once |
| ? | OPTIONAL, but MUST NOT occur more than once |
| [square brackets] | list of common values |
| (parentheses) | data format |
| # | comment |
| ! | awaiting documentation |
Notes
- If latitude is present, so MUST be longitude, and vice versa.
- If the secondary classes are omitted, the two values MUST be separated by a semicolon 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.
- Coordinates use the datum of WGS84.
Related pages
- 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
- Other cheatsheets: hAtom cheatsheet, hCard cheatsheet (also adr cheatsheet + geo cheatsheet), hCalendar cheatsheet, hResume cheatsheet, hReview cheatsheet, PDF cheatsheet