Difference between revisions of "geo"

From Microformats Wiki
geo
Jump to navigation Jump to search
m (Reverted edits by [[Special:Contributions/000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000)
Line 1: Line 1:
HOW THING OUT
+
<entry-title>Geo</entry-title>
HOW ANYTHING OUT
+
{{latest|h-geo}}
HOW EVERYTHING OUT
+
{{Template:DraftSpecification}}
HOW UNIVERSE OUT
+
 
HOW MAKE THING OUT
+
'''geo''' (pronounced "gee-oh") is a simple format for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude), suitable for embedding in HTML or XHTML, Atom, RSS, and arbitrary XML. '''geo''' is a 1:1 representation of the "geo" property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in HTML, one of several open [[microformats|microformat]] standards.
HOW MAKE ANYTHING OUT
+
 
HOW MAKE EVERYTHING OUT
+
== Draft Specification ==
HOW MAKE UNIVERSE OUT
+
 
HOW THING BE OUT
+
;Editor/Author
HOW ANYTHING BE OUT
+
: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
=== Copyright ===
HOW MAKE THING BE OUT
+
Per the public domain release on [[User:Tantek|my user page]], this specification is released into the public domain.
HOW MAKE ANYTHING BE OUT
+
 
HOW MAKE EVERYTHING BE OUT
+
{{MicroFormatPublicDomainContributionStatement}}
HOW MAKE UNIVERSE BE OUT
+
 
HOW THING OUT
+
=== Patents ===
HOW ANYTHING OUT
+
{{MicroFormatPatentStatement}}
HOW EVERYTHING OUT
+
 
HOW UNIVERSE OUT
+
=== Inspiration and Acknowledgments ===
HOW MAKE THING OUT
+
Thanks to everyone who participated in the [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], and in particular to [http://radar.oreilly.com/nat/ Nat Torkington] and Vee McMillen of [http://oreilly.com O'Reilly] for [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 arranging and hosting the BOF].  Thanks to Chris Hibbbert for providing the [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f real world geo-caching example].
HOW MAKE ANYTHING OUT
+
 
HOW MAKE EVERYTHING OUT
+
== Introduction and Background ==
HOW MAKE UNIVERSE OUT
+
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly and interoperably implemented (e.g. Apple's Address Book application). The [[hcard|hCard]] microformat has similarly received significant adoption, from numerous sites publishing the format, to hCard to vCard proxies, to clientside javascript parsers.
HOW THING BE OUT
+
 
HOW ANYTHING BE OUT
+
At the [http://conferences.oreillynet.com/where/ Where 2.0 conference] in June 2005, there was widespread recognition that the community needed a way to simply and easily publish visible, extractable, geographic location information on the Web, given how often bloggers, and numerous other sites publish such information.  The [[geo-bof-2005-06-30|geo microformat BOF]] discussed this very topic, and concluded with a consensus decision to just try using ''geo'' from vCard/hCard.
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
This specification introduces the '''geo''' microformat, which is a 1:1 representation of the aforementioned ''geo'' property from the vCard standard, by simply reusing the ''geo'' property and sub-properties as-is from the [[hcard|hCard]] microformat.
HOW MAKE THING BE OUT
+
 
HOW MAKE ANYTHING BE OUT
+
Publishers can both embed '''geo''' addresses directly in their web pages and feeds, as well as markup existing latitude/longitude coordinates in the context of the rest of the information in their web pages and feeds.
HOW MAKE EVERYTHING BE OUT
+
 
HOW MAKE UNIVERSE BE OUT
+
If the publisher knows and is publishing the ''name'' of the location in addition to its geo lat/long, then the publisher {{must}} use [[hcard|hCard]] instead of just '''geo''' to publish the name and geo lat/long of the location.
HOW THING OUT
+
 
HOW ANYTHING OUT
+
If the publisher knows and is publishing the address of the location, OR if the address of the location was what was actually entered by a human, and the publisher simply turned that into lat/long using some sort of a service, then the publisher {{should}} use [[adr]] to publish the actual human entered address information since that communicates far more semantic information than a simple geo lat/long coordinate.
HOW EVERYTHING OUT
+
 
HOW UNIVERSE OUT
+
== Semantic XHTML Design Principles ==
HOW MAKE THING OUT
+
{{semantic-xhtml-design-principles}}
HOW MAKE ANYTHING OUT
+
 
HOW MAKE EVERYTHING OUT
+
== Format ==
HOW MAKE UNIVERSE OUT
+
=== Singular Properties ===
HOW THING BE OUT
+
 
HOW ANYTHING BE OUT
+
Note that all the properties in '''geo''' are singular properties, and thus the first descendant element with that class should take effect, any others being ignored.
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
=== Human vs. Machine readable ===
HOW MAKE THING BE OUT
+
 
HOW MAKE ANYTHING BE OUT
+
If an <code>&lt;abbr&gt;</code> element is used for a property, then the <code>title</code> attribute of the <code>&lt;abbr&gt;</code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.
HOW MAKE EVERYTHING BE OUT
+
 
HOW MAKE UNIVERSE BE OUT
+
=== Value excerpting ===
HOW THING OUT
+
 
HOW ANYTHING OUT
+
Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. For this purpose, the special class name <code>value</code> is used to excerpt out the subset of the element that is  the value of the property.  See [[hcard|hCard]] for details on this.
HOW EVERYTHING OUT
+
 
HOW UNIVERSE OUT
+
=== Root Class Name ===
HOW MAKE THING OUT
+
 
HOW MAKE ANYTHING OUT
+
The root class name for an geo location is <code>geo</code>.
HOW MAKE EVERYTHING OUT
+
 
HOW MAKE UNIVERSE OUT
+
=== Property List ===
HOW THING BE OUT
+
 
HOW ANYTHING BE OUT
+
This is the list of properties in geo, taken from [[hcard|hCard]]:
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
* latitude
HOW MAKE THING BE OUT
+
* longitude
HOW MAKE ANYTHING BE OUT
+
 
HOW MAKE EVERYTHING BE OUT
+
=== XMDP Profile ===
HOW MAKE UNIVERSE BE OUT
+
 
HOW THING OUT
+
See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.
HOW ANYTHING OUT
+
 
HOW EVERYTHING OUT
+
=== Parsing Details ===
HOW UNIVERSE OUT
+
 
HOW MAKE THING OUT
+
See [[hcard-parsing|hCard parsing]], with the only difference being that "geo" is the root class name, rather than "vcard".
HOW MAKE ANYTHING OUT
+
 
HOW MAKE EVERYTHING OUT
+
== Examples ==
HOW MAKE UNIVERSE OUT
+
 
HOW THING BE OUT
+
This section is informative.
HOW ANYTHING BE OUT
+
 
HOW EVERYTHING BE OUT
+
=== Example from RFC2426 ===
HOW UNIVERSE BE OUT
+
 
HOW MAKE THING BE OUT
+
Section 3.4.2 of RFC2426 has a simple geo example:
HOW MAKE ANYTHING BE OUT
+
 
HOW MAKE EVERYTHING BE OUT
+
<source lang=text>
HOW MAKE UNIVERSE BE OUT
+
GEO:37.386013;-122.082932
HOW THING OUT
+
</source>
HOW ANYTHING OUT
+
 
HOW EVERYTHING OUT
+
this vCard fragment as a geo, as [http://microformats.org/wiki/hcard-examples#3.4.2_GEO_Type_Definition first documented on the hCard examples page]:
HOW UNIVERSE OUT
+
 
HOW MAKE THING OUT
+
<source lang=html4strict>
HOW MAKE ANYTHING OUT
+
<div class="geo">GEO:
HOW MAKE EVERYTHING OUT
+
<span class="latitude">37.386013</span>,
HOW MAKE UNIVERSE OUT
+
<span class="longitude">-122.082932</span>
HOW THING BE OUT
+
</div>
HOW ANYTHING BE OUT
+
</source>
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
this geo could be displayed as: <!-- this section includes a live Geo microforamt - please edit with care -->
HOW MAKE THING BE OUT
+
 
HOW MAKE ANYTHING BE OUT
+
<div class="geo">GEO: <span class="latitude">37.386013</span>, <span class="longitude">-122.082932</span></div>
HOW MAKE EVERYTHING BE OUT
+
 
HOW MAKE UNIVERSE BE OUT
+
Note that this is a '''live''' geo microformat, which will be found on this page by parsers.
HOW THING OUT
+
 
HOW ANYTHING OUT
+
=== Real world geo example ===
HOW EVERYTHING OUT
+
 
HOW UNIVERSE OUT
+
Here is a sample of published lat/long info (from [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f geocaching: Noble Steed]):
HOW MAKE THING OUT
+
 
HOW MAKE ANYTHING OUT
+
<source lang=text>
HOW MAKE EVERYTHING OUT
+
N 37° 24.491 W 122° 08.313
HOW MAKE UNIVERSE OUT
+
</source>
HOW THING BE OUT
+
 
HOW ANYTHING BE OUT
+
With geo markup:
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
<source lang=html4strict>
HOW MAKE THING BE OUT
+
<div class="geo">
HOW MAKE ANYTHING BE OUT
+
<abbr class="latitude" title="37.408183">N 37° 24.491</abbr>
HOW MAKE EVERYTHING BE OUT
+
<abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
HOW MAKE UNIVERSE BE OUT
+
</div>
HOW THING OUT
+
</source>
HOW ANYTHING OUT
+
 
HOW EVERYTHING OUT
+
This geo might be displayed as: <!-- this section includes a live Geo microformat - please edit with care -->
HOW UNIVERSE OUT
+
 
HOW MAKE THING OUT
+
<div class="geo"><abbr class="latitude" title="37.408183">N 37° 24.491</abbr> <abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
HOW MAKE ANYTHING OUT
+
</div>
HOW MAKE EVERYTHING OUT
+
 
HOW MAKE UNIVERSE OUT
+
Again, this is a '''live''' example.
HOW THING BE OUT
+
 
HOW ANYTHING BE OUT
+
Note that since the real world example used a more human readable presentation of the geo coordinates, we use the [[abbr-design-pattern]] to keep that more human readable presentation, and in addition provide the respective absolute numerical values for the geo.
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
=== with value-title ===
HOW MAKE THING BE OUT
+
There may be instances where you only have text like "the location" in your page, and yet you want to mark it up with geo coordinates. While it is better to markup visible data (for longevity, fidelity, reviewability), if for design reasons you're unable to provide visible display of geo details, you may use the [[value-class-pattern#Parsing_value_from_a_title_attribute|value class pattern value-title]] to markup them up:
HOW MAKE ANYTHING BE OUT
+
 
HOW MAKE EVERYTHING BE OUT
+
<source lang=html4strict>
HOW MAKE UNIVERSE BE OUT
+
We met at a
HOW THING OUT
+
<span class="geo">
HOW ANYTHING OUT
+
<span class="latitude">
HOW EVERYTHING OUT
+
  <span class="value-title" title="37.386013"> </span>
HOW UNIVERSE OUT
+
</span>
HOW MAKE THING OUT
+
<span class="longitude">
HOW MAKE ANYTHING OUT
+
  <span class="value-title" title="-122.082932"> </span>
HOW MAKE EVERYTHING OUT
+
</span>
HOW MAKE UNIVERSE OUT
+
certain location
HOW THING BE OUT
+
</span>
HOW ANYTHING BE OUT
+
</source>
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
This geo may be displayed as:
HOW MAKE THING BE OUT
+
 
HOW MAKE ANYTHING BE OUT
+
We met at a <span class="geo"><span class="latitude"><span class="value-title" title="37.386013"> </span></span><span class="longitude"><span class="value-title" title="-122.082932"> </span></span> certain location</span>
HOW MAKE EVERYTHING BE OUT
+
 
HOW MAKE UNIVERSE BE OUT
+
== Examples in the wild ==
HOW THING OUT
+
 
HOW ANYTHING OUT
+
This section is '''informative'''. The number of Geo examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a separate page, [[geo-examples-in-wild|Geo examples in the wild]].
HOW EVERYTHING OUT
+
 
HOW UNIVERSE OUT
+
== Implementations ==
HOW MAKE THING OUT
+
This section is '''informative'''.
HOW MAKE ANYTHING OUT
+
 
HOW MAKE EVERYTHING OUT
+
The following implementations have been developed which either generate or parse geos outside the context of hCards. If you have an geo implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.
HOW MAKE UNIVERSE OUT
+
 
HOW THING BE OUT
+
*WordPress.com's [http://en.support.wordpress.com/geotagging/ geotagging feature] lets you geotag user profiles and posts. Geo Search is also coming soon.
HOW ANYTHING BE OUT
+
*Clem Rutter's "[http://www.rutter.uklinux.net/ostowiki.html OSGBGridRefs to WGS84]" converter - Takes UK or Irish OS grid references and converts them to WGS84 coordinates, with two types of Geo mark-up (<code>SPAN</code> and <code>ABBR</code>) available to copy & paste.
HOW EVERYTHING BE OUT
+
* GIS-Wiki's "[http://www.giswiki.org/hjl_get_CoorE.htm hjl_getCoor]" now outputs Geo markup, from a Google Maps API.
HOW UNIVERSE BE OUT
+
* [http://www.addressfix.com/ AddressFix] takes any valid address in the listed countries (as at 2003-07) or map point (using GoogleMaps API) and outputs geo markup.
HOW MAKE THING BE OUT
+
**Countries: Andorra, Australia, Austria, Belgium, Canada, France, Germany, Gibraltar, Italy, Japan (but only in Japanese), Liechtenstein, Luxembourg, Monaco, Netherlands, New Zealand, San Marino, Spain, Sweden, Switzerland, United States of America and the Vatican City.
HOW MAKE ANYTHING BE OUT
+
**For countries other than the UK, the British Isles and China it provides geocoding for country names and city names (e.g. "Nairobi, Kenya").
HOW MAKE EVERYTHING BE OUT
+
**For UK, the British Isles and China, Google returns an error.
HOW MAKE UNIVERSE BE OUT
+
* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a [[geo]]. Written by [http://highearthorbit.com Andrew Turner]
HOW THING OUT
+
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
HOW ANYTHING OUT
+
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written a [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html javascript to add maps to geo markup on pages]
HOW EVERYTHING OUT
+
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding geos and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
HOW UNIVERSE OUT
+
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written some javascript to [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html convert the geo microformat to a google map] using [[geo]].
HOW MAKE THING OUT
+
* Brian Suda has written some [http://suda.co.uk/projects/microformats/geo/ geo extracting] code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.
HOW MAKE ANYTHING OUT
+
**GPX export is done, but needs some tweaking and testing. Just change &type=(kml|georss|gpx). Not quite ready for primetime yet. Feel free to test and send feedback.
HOW MAKE EVERYTHING OUT
+
* Fil explains [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].
HOW MAKE UNIVERSE OUT
+
* [http://www.locify.com Locify] uses [[geo]] format for presenting waypoints stored from the mobile client.
HOW THING BE OUT
+
 
HOW ANYTHING BE OUT
+
=== old implementations ===
HOW EVERYTHING BE OUT
+
Implementations that have disappeared or appear to be offline:
HOW UNIVERSE BE OUT
+
 
HOW MAKE THING BE OUT
+
Offline as of 2013-088:
HOW MAKE ANYTHING BE OUT
+
* [http://www.sydneydirectory.org/ Sydney Directory Wiki] supports geographical coordinates for locations
HOW MAKE EVERYTHING BE OUT
+
* [http://blog.codeeg.com/ Calvin Yu] has written a  [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].
HOW MAKE UNIVERSE BE OUT
+
* [http://mmm.iamnear.net Magical Microformat Maker - a Geo Microformat Generator with a big map]
HOW THING OUT
+
 
HOW ANYTHING OUT
+
== References ==
HOW EVERYTHING OUT
+
=== Normative References ===
HOW UNIVERSE OUT
+
* [[hcard|hCard]]
HOW MAKE THING OUT
+
 
HOW MAKE ANYTHING OUT
+
=== Informative References ===
HOW MAKE EVERYTHING OUT
+
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
HOW MAKE UNIVERSE OUT
+
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
HOW THING BE OUT
+
* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]
HOW ANYTHING BE OUT
+
* [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
== Work in progress ==
HOW MAKE THING BE OUT
+
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.
HOW MAKE ANYTHING BE OUT
+
 
HOW MAKE EVERYTHING BE OUT
+
* Proposals for changes, additions and other thoughts about [[geo]] may be found at [[geo-brainstorming]].
HOW MAKE UNIVERSE BE OUT
+
 
HOW THING OUT
+
== Related Work ==
HOW ANYTHING OUT
+
* [[luna]] (proposal for geo-style microformat for co-ordinates on The Moon)
HOW EVERYTHING OUT
+
* [[mars]] (proposal for geo-style microformat for co-ordinates on the planet Mars)
HOW UNIVERSE OUT
+
* [[geo-extension-strawman]] - extends [[geo]] to include the above, and for representing coordinates on other planets, moons etc.
HOW MAKE THING OUT
+
* [[thoughts-on-extending-the-geo-microformat|thoughts on addind time and reference system]] to the geo microformat, that could also be used for places on other celestial bodies
HOW MAKE ANYTHING OUT
+
 
HOW MAKE EVERYTHING OUT
+
== Similar Work ==
HOW MAKE UNIVERSE OUT
+
* [[adr]]
HOW THING BE OUT
+
* [[hcalendar|hCalendar]]
HOW ANYTHING BE OUT
+
* [[XOXO]]
HOW EVERYTHING BE OUT
+
 
HOW UNIVERSE BE OUT
+
== See Also ==
HOW MAKE THING BE OUT
+
* [http://en.wikipedia.org/wiki/Geo_%28microformat%29 Geo on Wikipedia]
HOW MAKE ANYTHING BE OUT
+
* [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]
HOW MAKE EVERYTHING BE OUT
+
 
HOW MAKE UNIVERSE BE OUT
+
== Related Pages ==
HOW THING OUT
+
{{geo-related-pages}}
HOW ANYTHING OUT
+
 
HOW EVERYTHING OUT
+
[[Category:Draft_Specifications]]
HOW UNIVERSE OUT
+
[[Category:Geo]]
HOW MAKE THING OUT
+
[[Category:hCard]]
HOW MAKE ANYTHING OUT
 
HOW MAKE EVERYTHING OUT
 
HOW MAKE UNIVERSE OUT
 
HOW THING BE OUT
 
HOW ANYTHING BE OUT
 
HOW EVERYTHING BE OUT
 
HOW UNIVERSE BE OUT
 
HOW MAKE THING BE OUT
 
HOW MAKE ANYTHING BE OUT
 
HOW MAKE EVERYTHING BE OUT
 
HOW MAKE UNIVERSE BE OUT
 
HOW THING OUT
 
HOW ANYTHING OUT
 
HOW EVERYTHING OUT
 
HOW UNIVERSE OUT
 
HOW MAKE THING OUT
 
HOW MAKE ANYTHING OUT
 
HOW MAKE EVERYTHING OUT
 
HOW MAKE UNIVERSE OUT
 
HOW THING BE OUT
 
HOW ANYTHING BE OUT
 
HOW EVERYTHING BE OUT
 
HOW UNIVERSE BE OUT
 
HOW MAKE THING BE OUT
 
HOW MAKE ANYTHING BE OUT
 
HOW MAKE EVERYTHING BE OUT
 
HOW MAKE UNIVERSE BE OUT
 
HOW THING OUT
 
HOW ANYTHING OUT
 
HOW EVERYTHING OUT
 
HOW UNIVERSE OUT
 
HOW MAKE THING OUT
 
HOW MAKE ANYTHING OUT
 
HOW MAKE EVERYTHING OUT
 
HOW MAKE UNIVERSE OUT
 
HOW THING BE OUT
 
HOW ANYTHING BE OUT
 
HOW EVERYTHING BE OUT
 
HOW UNIVERSE BE OUT
 
HOW MAKE THING BE OUT
 
HOW MAKE ANYTHING BE OUT
 
HOW MAKE EVERYTHING BE OUT
 
HOW MAKE UNIVERSE BE OUT
 
HOW THING OUT
 
HOW ANYTHING OUT
 
HOW EVERYTHING OUT
 
HOW UNIVERSE OUT
 
HOW MAKE THING OUT
 
HOW MAKE ANYTHING OUT
 
HOW MAKE EVERYTHING OUT
 
HOW MAKE UNIVERSE OUT
 
HOW THING BE OUT
 
HOW ANYTHING BE OUT
 
HOW EVERYTHING BE OUT
 
HOW UNIVERSE BE OUT
 
HOW MAKE THING BE OUT
 
HOW MAKE ANYTHING BE OUT
 
HOW MAKE EVERYTHING BE OUT
 
HOW MAKE UNIVERSE BE OUT
 
HOW THING OUT
 
HOW ANYTHING OUT
 
HOW EVERYTHING OUT
 
HOW UNIVERSE OUT
 
HOW MAKE THING OUT
 
HOW MAKE ANYTHING OUT
 
HOW MAKE EVERYTHING OUT
 
HOW MAKE UNIVERSE OUT
 
HOW THING BE OUT
 
HOW ANYTHING BE OUT
 
HOW EVERYTHING BE OUT
 
HOW UNIVERSE BE OUT
 
HOW MAKE THING BE OUT
 
HOW MAKE ANYTHING BE OUT
 
HOW MAKE EVERYTHING BE OUT
 
HOW MAKE UNIVERSE BE OUT
 
HOW THING OUT
 
HOW ANYTHING OUT
 
HOW EVERYTHING OUT
 
HOW UNIVERSE OUT
 
HOW MAKE THING OUT
 
HOW MAKE ANYTHING OUT
 
HOW MAKE EVERYTHING OUT
 
HOW MAKE UNIVERSE OUT
 
HOW THING BE OUT
 
HOW ANYTHING BE OUT
 
HOW EVERYTHING BE OUT
 
HOW UNIVERSE BE OUT
 
HOW MAKE THING BE OUT
 
HOW MAKE ANYTHING BE OUT
 
HOW MAKE EVERYTHING BE OUT
 
HOW MAKE UNIVERSE BE OUT
 
HOW THING OUT
 
HOW ANYTHING OUT
 
HOW EVERYTHING OUT
 
HOW UNIVERSE OUT
 
HOW MAKE THING OUT
 
HOW MAKE ANYTHING OUT
 
HOW MAKE EVERYTHING OUT
 
HOW MAKE UNIVERSE OUT
 
HOW THING BE OUT
 
HOW ANYTHING BE OUT
 
HOW EVERYTHING BE OUT
 
HOW UNIVERSE BE OUT
 
HOW MAKE THING BE OUT
 
HOW MAKE ANYTHING BE OUT
 
HOW MAKE EVERYTHING BE OUT
 
HOW MAKE UNIVERSE BE OUT
 
HOW THING OUT
 
HOW ANYTHING OUT
 
HOW EVERYTHING OUT
 
HOW UNIVERSE OUT
 
HOW MAKE THING OUT
 
HOW MAKE ANYTHING OUT
 
HOW MAKE EVERYTHING OUT
 
HOW MAKE UNIVERSE OUT
 
HOW THING BE OUT
 
HOW ANYTHING BE OUT
 
HOW EVERYTHING BE OUT
 
HOW UNIVERSE BE OUT
 
HOW MAKE THING BE OUT
 
HOW MAKE ANYTHING BE OUT
 
HOW MAKE EVERYTHING BE OUT
 
HOW MAKE UNIVERSE BE OUT
 
HOW THING OUT
 
HOW ANYTHING OUT
 
HOW EVERYTHING OUT
 
HOW UNIVERSE OUT
 
HOW MAKE THING OUT
 
HOW MAKE ANYTHING OUT
 
HOW MAKE EVERYTHING OUT
 
HOW MAKE UNIVERSE OUT
 
HOW THING BE OUT
 
HOW ANYTHING BE OUT
 
HOW EVERYTHING BE OUT
 
HOW UNIVERSE BE OUT
 
HOW MAKE THING BE OUT
 
HOW MAKE ANYTHING BE OUT
 
HOW MAKE EVERYTHING BE OUT
 
HOW MAKE UNIVERSE BE OUT
 

Revision as of 05:23, 19 August 2013

<entry-title>Geo</entry-title>

See latest version: h-geo

This document represents a draft microformat specification. Although drafts are somewhat mature in the development process, the stability of this document cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Watch this wiki page, or follow discussions on the #microformats Freenode IRC channel to stay up-to-date.

geo (pronounced "gee-oh") is a simple format for marking up WGS84 geographic coordinates (latitude; longitude), suitable for embedding in HTML or XHTML, Atom, RSS, and arbitrary XML. geo is a 1:1 representation of the "geo" property in the vCard standard (RFC2426) in HTML, one of several open microformat standards.

Draft Specification

Editor/Author
Tantek Çelik (Technorati, Inc.)

Copyright

Per the public domain release on my user page, this specification is released into the public domain.

Public Domain Contribution Requirement. Since the author(s) released this work into the public domain, in order to maintain this work's public domain status, all contributors to this page agree to release their contributions to this page to the public domain as well. Contributors may indicate their agreement by adding the public domain release template to their user page per the Voluntary Public Domain Declarations instructions. Unreleased contributions may be reverted/removed.

Patents

This specification is subject to a royalty free patent policy, e.g. per the W3C Patent Policy, and IETF RFC3667 & RFC3668.

Inspiration and Acknowledgments

Thanks to everyone who participated in the Geo Microformat BOF at O'Reilly's Where 2.0 conference, and in particular to Nat Torkington and Vee McMillen of O'Reilly for arranging and hosting the BOF. Thanks to Chris Hibbbert for providing the real world geo-caching example.

Introduction and Background

The vCard standard (RFC2426), has been broadly and interoperably implemented (e.g. Apple's Address Book application). The hCard microformat has similarly received significant adoption, from numerous sites publishing the format, to hCard to vCard proxies, to clientside javascript parsers.

At the Where 2.0 conference in June 2005, there was widespread recognition that the community needed a way to simply and easily publish visible, extractable, geographic location information on the Web, given how often bloggers, and numerous other sites publish such information. The geo microformat BOF discussed this very topic, and concluded with a consensus decision to just try using geo from vCard/hCard.

This specification introduces the geo microformat, which is a 1:1 representation of the aforementioned geo property from the vCard standard, by simply reusing the geo property and sub-properties as-is from the hCard microformat.

Publishers can both embed geo addresses directly in their web pages and feeds, as well as markup existing latitude/longitude coordinates in the context of the rest of the information in their web pages and feeds.

If the publisher knows and is publishing the name of the location in addition to its geo lat/long, then the publisher MUST use hCard instead of just geo to publish the name and geo lat/long of the location.

If the publisher knows and is publishing the address of the location, OR if the address of the location was what was actually entered by a human, and the publisher simply turned that into lat/long using some sort of a service, then the publisher SHOULD use adr to publish the actual human entered address information since that communicates far more semantic information than a simple geo lat/long coordinate.

Semantic XHTML Design Principles

Note: the Semantic XHTML Design Principles were written primarily within the context of developing hCard and hCalendar, thus it may be easier to understand these principles in the context of the hCard design methodology (i.e. read that first). Tantek

XHTML is built on XML, and thus XHTML based formats can be used not only for convenient display presentation, but also for general purpose data exchange. In many ways, XHTML based formats exemplify the best of both HTML and XML worlds. However, when building XHTML based formats, it helps to have a guiding set of principles.

  1. Reuse the schema (names, objects, properties, values, types, hierarchies, constraints) as much as possible from pre-existing, established, well-supported standards by reference. Avoid restating constraints expressed in the source standard. Informative mentions are ok.
    1. For types with multiple components, use nested elements with class names equivalent to the names of the components.
    2. Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.
  2. Use the most accurately precise semantic XHTML building block for each object etc.
  3. Otherwise use a generic structural element (e.g. <span> or <div>), or the appropriate contextual element (e.g. an <li> inside a <ul> or <ol>).
  4. Use class names based on names from the original schema, unless the semantic XHTML building block precisely represents that part of the original schema. If names in the source schema are case-insensitive, then use an all lowercase equivalent. Components names implicit in prose (rather than explicit in the defined schema) should also use lowercase equivalents for ease of use. Spaces in component names become dash '-' characters.
  5. Finally, if the format of the data according to the original schema is too long and/or not human-friendly, use <abbr> instead of a generic structural element, and place the literal data into the 'title' attribute (where abbr expansions go), and the more brief and human readable equivalent into the element itself. Further informative explanation of this use of <abbr>: Human vs. ISO8601 dates problem solved

Format

Singular Properties

Note that all the properties in geo are singular properties, and thus the first descendant element with that class should take effect, any others being ignored.

Human vs. Machine readable

If an <abbr> element is used for a property, then the title attribute of the <abbr> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

Value excerpting

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. For this purpose, the special class name value is used to excerpt out the subset of the element that is the value of the property. See hCard for details on this.

Root Class Name

The root class name for an geo location is geo.

Property List

This is the list of properties in geo, taken from hCard:

  • latitude
  • longitude

XMDP Profile

See hCard Profile for the XMDP profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

Parsing Details

See hCard parsing, with the only difference being that "geo" is the root class name, rather than "vcard".

Examples

This section is informative.

Example from RFC2426

Section 3.4.2 of RFC2426 has a simple geo example:

GEO:37.386013;-122.082932

this vCard fragment as a geo, as first documented on the hCard examples page:

<div class="geo">GEO: 
 <span class="latitude">37.386013</span>, 
 <span class="longitude">-122.082932</span>
</div>

this geo could be displayed as:

GEO: 37.386013, -122.082932

Note that this is a live geo microformat, which will be found on this page by parsers.

Real world geo example

Here is a sample of published lat/long info (from geocaching: Noble Steed):

N 37° 24.491 W 122° 08.313

With geo markup:

<div class="geo">
 <abbr class="latitude" title="37.408183">N 37° 24.491</abbr> 
 <abbr class="longitude" title="-122.13855">W 122° 08.313</abbr>
</div>

This geo might be displayed as:

N 37° 24.491 W 122° 08.313

Again, this is a live example.

Note that since the real world example used a more human readable presentation of the geo coordinates, we use the abbr design pattern to keep that more human readable presentation, and in addition provide the respective absolute numerical values for the geo.

with value-title

There may be instances where you only have text like "the location" in your page, and yet you want to mark it up with geo coordinates. While it is better to markup visible data (for longevity, fidelity, reviewability), if for design reasons you're unable to provide visible display of geo details, you may use the value class pattern value-title to markup them up:

We met at a 
<span class="geo">
 <span class="latitude">
  <span class="value-title" title="37.386013"> </span>
 </span>
 <span class="longitude">
  <span class="value-title" title="-122.082932"> </span>
 </span>
 certain location
</span>

This geo may be displayed as:

We met at a certain location

Examples in the wild

This section is informative. The number of Geo examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a separate page, Geo examples in the wild.

Implementations

This section is informative.

The following implementations have been developed which either generate or parse geos outside the context of hCards. If you have an geo implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

  • WordPress.com's geotagging feature lets you geotag user profiles and posts. Geo Search is also coming soon.
  • Clem Rutter's "OSGBGridRefs to WGS84" converter - Takes UK or Irish OS grid references and converts them to WGS84 coordinates, with two types of Geo mark-up (SPAN and ABBR) available to copy & paste.
  • GIS-Wiki's "hjl_getCoor" now outputs Geo markup, from a Google Maps API.
  • AddressFix takes any valid address in the listed countries (as at 2003-07) or map point (using GoogleMaps API) and outputs geo markup.
    • Countries: Andorra, Australia, Austria, Belgium, Canada, France, Germany, Gibraltar, Italy, Japan (but only in Japanese), Liechtenstein, Luxembourg, Monaco, Netherlands, New Zealand, San Marino, Spain, Sweden, Switzerland, United States of America and the Vatican City.
    • For countries other than the UK, the British Isles and China it provides geocoding for country names and city names (e.g. "Nairobi, Kenya").
    • For UK, the British Isles and China, Google returns an error.
  • GreaseRoute is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a Geo. Written by Andrew Turner
  • podster.de finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
  • Philip Tellis has written a javascript to add maps to geo markup on pages
  • pnh_mf is a plugin for Textpattern that supports embedding geos and other microformats in templates and blog posts. Written by Chris Casciano.
  • Philip Tellis has written some javascript to convert the geo microformat to a google map using Geo.
  • Brian Suda has written some geo extracting code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.
    • GPX export is done, but needs some tweaking and testing. Just change &type=(kml|georss|gpx). Not quite ready for primetime yet. Feel free to test and send feedback.
  • Fil explains how to use the geo microformat with the javascript library jQuery [1].
  • Locify uses Geo format for presenting waypoints stored from the mobile client.

old implementations

Implementations that have disappeared or appear to be offline:

Offline as of 2013-088:

References

Normative References

Informative References

Work in progress

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

Related Work

  • luna (proposal for geo-style microformat for co-ordinates on The Moon)
  • mars (proposal for geo-style microformat for co-ordinates on the planet Mars)
  • geo-extension-nonWGS84 - extends Geo to include the above, and for representing coordinates on other planets, moons etc.
  • thoughts on addind time and reference system to the geo microformat, that could also be used for places on other celestial bodies

Similar Work

See Also

Related Pages