Google Maps API V3 geocoding with SharePoint 2010

This explains how to show addresses in a SharePoint 2010 list on a Google Map.

This article is based on Kyle Shaeffer’s Plotting Your SharePoint 2010 List Data on a Google Map. The main difference is I upgraded his method to Google Maps API V3.

Here’s how it’s done:

Create a list

Using SharePoint Designer 2010 (free download!), open your SharePoint site and:

  1. Under Site Objects, click Lists and Libraries.
  2. In the Lists and Libraries tab, click Custom List.
  3.  Enter MyData and press OK.
  4. Click on your new list, then select Edit list columns in the Customization section.
  5. Add a Multi Lines of Text field using the Add New Column button at top left:. Name it Address.

Create data view

Still in SharePoint Designer 2010:

  1. Click Site Pages under Site Objects on the left:
  2.  In the ribbon at top, select Page > ASPX. Name your new page map.aspx.
  3. Click on the new page, then click Edit file in the Customization section. If asked to open the page in advanced mode, click Yes.
  4. Make sure that Design or Split are selected at bottom. From the menu at top: Insert > Data View > MyData

Now you’ll see your data in a table in the page.

Add the JavaScripts

You’ll need to reference two script libraries: Google’s Maps API and jQuery.

Find the opening <form> element in the source code. Right after it, paste this code:

<script type="text/javascript" src="https://maps.googleapis.com/maps/api/js?key=API_KEY_GOES_HERE&sensor=false"></script>
<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
 
<div id="map_canvas" style="width: 98%; height: 400px"></div>
 
<script type="text/javascript">
// set up the basic map object
var latlng = new google.maps.LatLng(34.603885, -4.626009);
var myOptions = {
	zoom: 2,
	center: latlng,
	mapTypeId: google.maps.MapTypeId.ROADMAP
};
var map = new google.maps.Map(document.getElementById("map_canvas"), myOptions);
 
// this is used for geocoding
var geocoder = new google.maps.Geocoder();
 
function codeAddress(address, theName) {
    geocoder.geocode( { 'address': address}, function(results, status) {
      if (status == google.maps.GeocoderStatus.OK) {
        var marker = new google.maps.Marker({
            map: map,
            position: results[0].geometry.location
        });
      } else {
        alert("Geocode was not successful for the following reason: " + status);
      }
    });
}
 
// this is called with body's onload to pull addresses after the page is done loading.
function initialize() {
	$("tr.ms-itmhover").each(function(i){
		codeAddress($(this).find('.ms-rtestate-field:eq(0)').text(), $(this).find('.ms-vb-title:eq(0) a').text());
	});
}
</script>

Replace API_KEY_GOES_HERE with your own Google API key. Don’t have one? Get it at https://code.google.com/apis/console/. Be sure to get a Google Maps API v3 key! v2 is deprecated.

Now you need to add an onload attribute to your body tag to fire off the initialize function:

<body onload="initialize()">

Viola! You have a map that dynamically pulls from the below list!

Caveats

The initialize method works by scraping from the rendered HTML. It’s finding every tr with class ms-itmhover–which is what is produced by the data view you inserted above. Then within each of those trs, it finds:

  • The first item with class ms-rtestate-field and gets its text contents. This will be your address.
  • The contents of the a tag within the first element with class ms-vb-title, which is the title field.

You’ll have to do JavaScript surgery if you change fields in a way that alters this. For example, if another multi line text field displays before your address, you’ll have to change .ms-rtestate-field:eq(0) to .ms-rtestate-field:eq(1). Or you’ll need to alter the XSLT behind the data view to produce some other classes or code.

Also, because this uses JavaScript to scrape the screen’s contents, you must deliver the data list in the page . It doesn’t have to be visible–you can make it invisible with CSS. If you don’t want the data to be on the page, you’ll need to use more sophisticated techniques, possibly some kind of AJAX.

Hiding Active Directory user IDs from WordPress author slugs

I recently set up a corporate WordPress blog system. With the Active Directory Integration plugin, users can sign in with their corporate ID and password.

But here’s a problem: each blog post has a link to the author’s profile. That profile’s URL includes the user ID. The corporation’s security standards say we can’t expose user IDs to the world, so the author profile URLs have to be sanitized.

It took a while to figure out a solution, but the end result is reasonable.

I found this post at StackExchange’s WordPress site. Adding the first two code snippets (below) to the end of wp-config.php tells WordPress to use the user’s nickname metadata to construct the profile URLs:

add_filter( 'request', 'wpse5742_request' );function wpse5742_request( $query_vars )
 
{
 if ( array_key_exists( 'author_name', $query_vars ) ) {
 global $wpdb;
 $author_id = $wpdb-&gt;get_var( $wpdb-&gt;prepare( "SELECT user_id FROM {$wpdb-&gt;usermeta} WHERE meta_key='nickname' AND meta_value = %s", $query_vars['author_name'] ) );
 if ( $author_id ) {
 $query_vars['author'] = $author_id;
 unset( $query_vars['author_name'] );
 }
 }
 return $query_vars;
}
 
add_filter( 'author_link', 'wpse5742_author_link', 10, 3 );
function wpse5742_author_link( $link, $author_id, $author_nicename)
{
 $author_nickname = get_user_meta( $author_id, 'nickname', true );
 if ( $author_nickname ) {
 $link = str_replace( $author_nicename, $author_nickname, $link );
 }
 return $link;
}

But wait, there’s more!

Now you have to get a proper value into the nickname field. Active Directory Integration makes this easy. In this plugin’s settings, go to the User Meta tab and enter this into the Additional User Attributes field: mailnickname:string:nickname. You’ll may need to replace mailnickname with your own Active Directory user attribute if it isn’t appropriate for you.

That’s it. The next time a user logs in, the nickname field is updated, and all future profile URLs for that user will not have a user ID.

Did Forrester Research CEO George Colony really say that?

According to CMS Wire, Forrester Research Chief Executive Officer George Colony said, “within 15 years CEOs will need to know the ins and outs of new media, social network technologies and social communities before they get the job.” (emphasis mine)

15 years? I’m scratching my head. The Web 2.0 is relevant today. E.g., Facebook has over 400 million users right now. Fifteen years from now passes through several generations of new technology!

For Colony’s sake, I hope CMS Wire misquoted or he misspoke. I’ll tweet him and see what he says.

Drupal doesn’t “get” enterprise

If http://www.databasepublish.com/blog/presentation-scaling-drupal-enterprise represents Drupal’s enterprise thinking, Drupal doesn’t “get” enterprise.

Drupal apparently thinks enterprise is just performance. That misses other important factors where Drupal falls on its face. For example:

  • It’s security model is stuck in a departmental model. At my work, we looked into an enterprise Drupal calendar, but we passed because it requires fantastic workarounds just to roughly approximate enterprise security.
  • Manageability is improving with the Aegir hosting system, but this just simplifies base management tasks. Enterprise Drupal is still a collection of discrete, departmental-class web systems, each of which has substantially independent configuration.

Drupal has its place in the enterprise for certain departmental solutions. But it’s a huge stretch to intimate that Drupal is “enterprise software.”

Texas GOP’s new web site on kludge

The Texas GOP recently rolled out a new web site at http://www.texasgop.org/.

If you surf it, you’ll see asp file extensions. For example: http://www.texasgop.org/inner.asp?z=6

That means the Texas GOP’s runs its brand new site on a kludge CMS!

“Woah, Aren, isn’t that severe?”

No.

ASP’s most recent version is from 1999.

Microsoft replaced it with ASP.Net 1.0 in January 2002. ASP.Net is now on 3.5, and 4.0 is around the corner.

Vendors still delivering classic ASP code in November 2009 have colossally failed to invest or innovate and may be incompetent.

When I review products, those still on ASP start out such a disadvantage that they’ll probably never make the selection.

What is up with the Texas GOP? How did it get hoodwinked into a kludge CMS?