• zuko105

    Hey Silver,
    I’d add, if you’re going to use Google Maps as your client side mapping, to go ahead and only use the google geocoding api. They limit it at 15k (free) requests per 24 hour period, which ain’t bad.

    Also, when using the microformat to mark up location information, be sure to include the profile attribute in the head tag:


  • zuko105

    Looks like the comment monitor took out my code.

    Head tag –
    Let’s try this again:

  • http://silvery.com Chris Smith

    Zuko, most tagging is suppressed in these comments — maybe you could provide a link to a page that describes the profile attribute in the head?

    Also, what’s the reason for using that? I’ve used Microformat software to read out the hCard info from webpages without using this profile attribute tag.


  • http://silvery.com Chris Smith

    Also, I didn’t recommend using the Google geocoding API because I believe it’s less user-friendly for inexperienced webmasters.

    Most small business webmasters only have one website with one address, so requiring them to write software to submit addresses and receive back geocodes to cache into their map webpage seems too heavy.

    Certainly, doing geocoding for dozens and hundreds of addresses would demand use of the API or a batch geocoder.

  • zuko105

    Sure thing. I know you’re a fan of w3c validation. This is the equivalent for microformats.

    Here’s links to a couple of examples:


    Live example:

    Point taken on the google geocode api.

  • http://silvery.com Chris Smith

    Zuko – you’re right – my bad!

    The Head Profile attribute is not necessarily required for adding meta data to a webpage, but it’s apparent that inclusion of this is ideal to insure that the program which interprets the webpage will know with higher confidence that it’s marked up with hCard microformats.