[uf-new] Re: Exposing place names whose property type (street-adr, locality...) is unknown

Kevin Marks kevinmarks at gmail.com
Mon Feb 2 14:32:45 PST 2009

The other way to do this is to use the "label" property of hcard,
which is an unstructured address. if you wrap the vaguer information
in a "label", that can be fed into a geocoder that accepts fuzzier

On Mon, Feb 2, 2009 at 12:29 PM, JMesserly <swarmers at gmail.com> wrote:
> Brian, thank you for your advice.  You suggested:
> >--- i would use extended-address for something like "Bailie's Bar" it
> >is not the street-address, and it is not the locality, but it is
> >useful. Infact, i probably would work in ORG and FN if this were an
> >hCard.
> >>  Red alert? case two:
> >>  <div class="adr">
> >>    <span class="locality">Teal street</span>,
> >>    <span class="locality">Honolulu</span>
> >>  </div>

How about

<div class="vcard" >
<span class="label">
<div class="adr">
<span class="locality">Teal street</span>,
<span class="locality">Honolulu</span>

You could use a structured geocoder to feed the raw information into,
and output that for possible human correction; for example Google's


 will give you back:

  "name": "teal street, honolulu",
  "Status": {
    "code": 200,
    "request": "geocode"
  "Placemark": [ {

    "id": "p1",
    "address": "Teal St, HI 96860, USA",
    "AddressDetails": {"Country": {"CountryNameCode":
"US","CountryName": "USA","AdministrativeArea":
{"AdministrativeAreaName": "HI","Thoroughfare":{"ThoroughfareName":
"Teal St"},"PostalCode": {"PostalCodeNumber": "96860"}}},"Accuracy":

    "ExtendedData": {
      "LatLonBox": {
        "north": 21.3685381,
        "south": 21.3622429,
        "east": -157.9489099,
        "west": -157.9552051

    "Point": {
      "coordinates": [ -157.9520480, 21.3654570, 0 ]
  } ]

which you could expand back to an hcard

More information about the microformats-new mailing list