|
|
Line 1: |
Line 1: |
| <entry-title>Geo</entry-title>
| | HOW THING THROUGH |
| {{latest|h-geo}}
| | HOW MAKE THING THROUGH |
| {{Template:DraftSpecification}}
| | HOW THING BE THROUGH |
| | | HOW MAKE THING BE THROUGH |
| '''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 ANYTHING THROUGH |
| | | HOW MAKE ANYTHING THROUGH |
| == Draft Specification ==
| | HOW ANYTHING BE THROUGH |
| | | HOW MAKE ANYTHING BE THROUGH |
| ;Editor/Author
| | HOW EVERYTHING THROUGH |
| : [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])
| | HOW MAKE EVERYTHING THROUGH |
| | | HOW EVERYTHING BE THROUGH |
| === Copyright ===
| | HOW MAKE EVERYTHING BE THROUGH |
| Per the public domain release on [[User:Tantek|my user page]], this specification is released into the public domain.
| | HOW UNIVERSE THROUGH |
| | | HOW MAKE UNIVERSE THROUGH |
| {{MicroFormatPublicDomainContributionStatement}}
| | HOW UNIVERSE BE THROUGH |
| | | HOW MAKE UNIVERSE BE THROUGH |
| === Patents ===
| | HOW THING OUT |
| {{MicroFormatPatentStatement}}
| | HOW MAKE THING OUT |
| | | HOW THING BE OUT |
| === Inspiration and Acknowledgments ===
| | HOW MAKE THING BE 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 ANYTHING OUT |
| | | HOW MAKE ANYTHING OUT |
| == Introduction and Background ==
| | HOW ANYTHING BE 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 MAKE ANYTHING BE OUT |
| | | HOW EVERYTHING 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 MAKE EVERYTHING OUT |
| | | HOW EVERYTHING 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 EVERYTHING BE OUT |
| | | HOW UNIVERSE 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 UNIVERSE OUT |
| | | HOW 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 MAKE UNIVERSE BE OUT |
| | | HOW THING THROUGH |
| 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 MAKE THING THROUGH |
| | | HOW THING BE THROUGH |
| == Semantic XHTML Design Principles ==
| | HOW MAKE THING BE THROUGH |
| {{semantic-xhtml-design-principles}}
| | HOW ANYTHING THROUGH |
| | | HOW MAKE ANYTHING THROUGH |
| == Format ==
| | HOW ANYTHING BE THROUGH |
| === Singular Properties ===
| | HOW MAKE ANYTHING BE THROUGH |
| | | HOW EVERYTHING THROUGH |
| 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 MAKE EVERYTHING THROUGH |
| | | HOW EVERYTHING BE THROUGH |
| === Human vs. Machine readable ===
| | HOW MAKE EVERYTHING BE THROUGH |
| | | HOW UNIVERSE THROUGH |
| If an <code><abbr></code> element is used for a property, then the <code>title</code> attribute of the <code><abbr></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 UNIVERSE THROUGH |
| | | HOW UNIVERSE BE THROUGH |
| === Value excerpting ===
| | HOW MAKE UNIVERSE BE THROUGH |
| | | HOW THING 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 MAKE THING OUT |
| | | HOW THING BE OUT |
| === Root Class Name ===
| | HOW MAKE THING BE OUT |
| | | HOW ANYTHING OUT |
| The root class name for an geo location is <code>geo</code>.
| | HOW MAKE ANYTHING OUT |
| | | HOW ANYTHING BE OUT |
| === Property List ===
| | HOW MAKE ANYTHING BE OUT |
| | | HOW EVERYTHING OUT |
| This is the list of properties in geo, taken from [[hcard|hCard]]:
| | HOW MAKE EVERYTHING OUT |
| | | HOW EVERYTHING BE OUT |
| * latitude
| | HOW MAKE EVERYTHING BE OUT |
| * longitude
| | HOW UNIVERSE OUT |
| | | HOW MAKE UNIVERSE OUT |
| === XMDP Profile ===
| | HOW UNIVERSE BE OUT |
| | | HOW MAKE UNIVERSE BE 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.
| |
| | |
| === Parsing Details ===
| |
| | |
| See [[hcard-parsing|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:
| |
| | |
| <source lang=text>
| |
| GEO:37.386013;-122.082932
| |
| </source>
| |
| | |
| 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]:
| |
| | |
| <source lang=html4strict>
| |
| <div class="geo">GEO:
| |
| <span class="latitude">37.386013</span>,
| |
| <span class="longitude">-122.082932</span>
| |
| </div>
| |
| </source>
| |
| | |
| this geo could be displayed as: <!-- this section includes a live Geo microforamt - please edit with care -->
| |
| | |
| <div class="geo">GEO: <span class="latitude">37.386013</span>, <span class="longitude">-122.082932</span></div>
| |
| | |
| 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 [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f geocaching: Noble Steed]):
| |
| | |
| <source lang=text>
| |
| N 37° 24.491 W 122° 08.313
| |
| </source>
| |
| | |
| With geo markup:
| |
| | |
| <source lang=html4strict>
| |
| <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>
| |
| </source>
| |
| | |
| This geo might be displayed as: <!-- this section includes a live Geo microformat - please edit with care -->
| |
| | |
| <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>
| |
| | |
| 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#Parsing_value_from_a_title_attribute|value class pattern value-title]] to markup them up:
| |
| | |
| <source lang=html4strict>
| |
| 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>
| |
| </source>
| |
| | |
| This geo may be displayed as:
| |
| | |
| 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>
| |
| | |
| == 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-wild|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 [http://en.support.wordpress.com/geotagging/ geotagging feature] lets you geotag user profiles and posts. Geo Search is also coming soon.
| |
| *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.
| |
| * GIS-Wiki's "[http://www.giswiki.org/hjl_get_CoorE.htm hjl_getCoor]" now outputs Geo markup, from a Google Maps API.
| |
| * [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.
| |
| **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.
| |
| * [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]
| |
| * [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)
| |
| * [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]
| |
| * [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].
| |
| * [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]].
| |
| * 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.
| |
| **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 [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].
| |
| * [http://www.locify.com 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:
| |
| * [http://www.sydneydirectory.org/ Sydney Directory Wiki] supports geographical coordinates for locations
| |
| * [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]].
| |
| * [http://mmm.iamnear.net Magical Microformat Maker - a Geo Microformat Generator with a big map]
| |
| | |
| == References ==
| |
| === Normative References ===
| |
| * [[hcard|hCard]]
| |
| | |
| === Informative References ===
| |
| * [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
| |
| * [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
| |
| * [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]
| |
| * [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]
| |
| | |
| == Work in progress ==
| |
| This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.
| |
| | |
| * Proposals for changes, additions and other thoughts about [[geo]] may be found at [[geo-brainstorming]].
| |
| | |
| == 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-strawman]] - extends [[geo]] to include the above, and for representing coordinates on other planets, moons etc.
| |
| * [[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
| |
| | |
| == Similar Work ==
| |
| * [[adr]]
| |
| * [[hcalendar|hCalendar]]
| |
| * [[XOXO]]
| |
| | |
| == See Also ==
| |
| * [http://en.wikipedia.org/wiki/Geo_%28microformat%29 Geo on Wikipedia]
| |
| * [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]
| |
| | |
| == Related Pages ==
| |
| {{geo-related-pages}}
| |
| | |
| [[Category:Draft_Specifications]]
| |
| [[Category:Geo]]
| |
| [[Category:hCard]]
| |