<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Google Map&#8217;s medical center phone data: Code Red!</title>
	<atom:link href="http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/feed/" rel="self" type="application/rss+xml" />
	<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/</link>
	<description>Developing Knowledge about Local Search</description>
	<lastBuildDate>Sun, 20 May 2012 21:09:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Google Maps and Hospital Hell Soon Coming to an End? Three Cheers! &#124; Understanding Google Maps &#38; Local Search</title>
		<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/comment-page-1/#comment-427121</link>
		<dc:creator>Google Maps and Hospital Hell Soon Coming to an End? Three Cheers! &#124; Understanding Google Maps &#38; Local Search</dc:creator>
		<pubDate>Fri, 18 Sep 2009 16:17:55 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=139#comment-427121</guid>
		<description>[...] issues compounded by the lack of customer support. This has been an on-going problem and was first reported as long ago as March, [...]</description>
		<content:encoded><![CDATA[<p>[...] issues compounded by the lack of customer support. This has been an on-going problem and was first reported as long ago as March, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Understanding Google Maps &#38; Yahoo Local Search &#187; Google Maps: Don&#8217;t get pregnant in Wellsville &#124; Developing Knowledge about Local Search</title>
		<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/comment-page-1/#comment-280256</link>
		<dc:creator>Understanding Google Maps &#38; Yahoo Local Search &#187; Google Maps: Don&#8217;t get pregnant in Wellsville &#124; Developing Knowledge about Local Search</dc:creator>
		<pubDate>Tue, 04 Nov 2008 10:32:25 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=139#comment-280256</guid>
		<description>[...] an unsuspecting user, in a life threatening situation, will be searching for an emergency room or hospital and be sent in the wrong direction and to a disastrous outcome.   &#171; Google Responds to [...]</description>
		<content:encoded><![CDATA[<p>[...] an unsuspecting user, in a life threatening situation, will be searching for an emergency room or hospital and be sent in the wrong direction and to a disastrous outcome.   &laquo; Google Responds to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Blumenthal</title>
		<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/comment-page-1/#comment-9778</link>
		<dc:creator>Mike Blumenthal</dc:creator>
		<pubDate>Wed, 21 Mar 2007 15:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=139#comment-9778</guid>
		<description>Yes, the ironies certainly do abound, don&#039;t they?

According to Bill Slawski&#039;s patent review they are attempting to do this, why so unsuccessfully in the medical arena escapes me.

Mike</description>
		<content:encoded><![CDATA[<p>Yes, the ironies certainly do abound, don&#8217;t they?</p>
<p>According to Bill Slawski&#8217;s patent review they are attempting to do this, why so unsuccessfully in the medical arena escapes me.</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Earlpearl</title>
		<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/comment-page-1/#comment-9775</link>
		<dc:creator>Earlpearl</dc:creator>
		<pubDate>Wed, 21 Mar 2007 15:30:59 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=139#comment-9775</guid>
		<description>Mike: 

I noticed how G maps recently added a picture off my website to the G maps data.  They chose and pulled the picture, from amongst a number of different pics.

It was interesting and an interesting choice...and one that as a business owner I wouldn&#039;t argue with...but might possibly have suggested a different pic.

Now if they can pull a pic...independantly determine relevancy...and post the pic....then they can review phone numbers on the site.

Seeing how the phone number issue is one that has caused some problems for some sites/institutions/businesses and certainly the people calling those numbers...it might be appropriate to focus on that aspect of the vast G maps data base.  Even starting with one type of entry;  say medical centers.

1.  Scrape the site for appropriate phone numbers.
2.  Match the phone numbers against those accumulated through the vast amount of directories
3.  Check to make sure that most current and appropriate phone numbers are listed within G maps data.

That would be a big improvement...and were they to be successful G would be lightyears ahead of other local data sources.  (of course any version of a local SE could try the same.)

Dave</description>
		<content:encoded><![CDATA[<p>Mike: </p>
<p>I noticed how G maps recently added a picture off my website to the G maps data.  They chose and pulled the picture, from amongst a number of different pics.</p>
<p>It was interesting and an interesting choice&#8230;and one that as a business owner I wouldn&#8217;t argue with&#8230;but might possibly have suggested a different pic.</p>
<p>Now if they can pull a pic&#8230;independantly determine relevancy&#8230;and post the pic&#8230;.then they can review phone numbers on the site.</p>
<p>Seeing how the phone number issue is one that has caused some problems for some sites/institutions/businesses and certainly the people calling those numbers&#8230;it might be appropriate to focus on that aspect of the vast G maps data base.  Even starting with one type of entry;  say medical centers.</p>
<p>1.  Scrape the site for appropriate phone numbers.<br />
2.  Match the phone numbers against those accumulated through the vast amount of directories<br />
3.  Check to make sure that most current and appropriate phone numbers are listed within G maps data.</p>
<p>That would be a big improvement&#8230;and were they to be successful G would be lightyears ahead of other local data sources.  (of course any version of a local SE could try the same.)</p>
<p>Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Earlpearl</title>
		<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/comment-page-1/#comment-9297</link>
		<dc:creator>Earlpearl</dc:creator>
		<pubDate>Tue, 20 Mar 2007 00:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=139#comment-9297</guid>
		<description>Mike:

I looked at your first example, Pittsburgh, Pa Medical Center.  The link takes you to the G maps listing for Mercy Hospital with 2 phone numbers.  Then I went to the website.  That is for Pittsburgh Mercy Health System.  This is a large institution with 11 separate locations in the region for all types of facilities.  Scroll through the locations and you&#039;ll find that one of the two phone numbers listed is for Mercy Hospital.  The 412-232-8111 number is accurate for one facility.

I scrolled through the other locations and it didn&#039;t match the 2nd number in the G maps directory information.  Each of the 11 facilities has a different main number but not the 2nd number listed; 412-232-7950.  I went to the main contact number for the website and it was a 3rd phone number;  412-232-5660.

I would think that G maps specifically and other similar sources, like Y and MSN Local need to take a step to clean the data--primarily sourcing the information from the website and not any other source.  Directory information can be old and outdated.  Website information should be the most updated.  

Of all sources of this ilk, though, Google insertion of maps is clearly seeing more traffic than any other source and is driving more calls off the G maps inserts.  Its clearly something that needs to be fixed.

How this is corrected is up to Google.  It certainly needs some reconstructive surgery.  

Dave</description>
		<content:encoded><![CDATA[<p>Mike:</p>
<p>I looked at your first example, Pittsburgh, Pa Medical Center.  The link takes you to the G maps listing for Mercy Hospital with 2 phone numbers.  Then I went to the website.  That is for Pittsburgh Mercy Health System.  This is a large institution with 11 separate locations in the region for all types of facilities.  Scroll through the locations and you&#8217;ll find that one of the two phone numbers listed is for Mercy Hospital.  The 412-232-8111 number is accurate for one facility.</p>
<p>I scrolled through the other locations and it didn&#8217;t match the 2nd number in the G maps directory information.  Each of the 11 facilities has a different main number but not the 2nd number listed; 412-232-7950.  I went to the main contact number for the website and it was a 3rd phone number;  412-232-5660.</p>
<p>I would think that G maps specifically and other similar sources, like Y and MSN Local need to take a step to clean the data&#8211;primarily sourcing the information from the website and not any other source.  Directory information can be old and outdated.  Website information should be the most updated.  </p>
<p>Of all sources of this ilk, though, Google insertion of maps is clearly seeing more traffic than any other source and is driving more calls off the G maps inserts.  Its clearly something that needs to be fixed.</p>
<p>How this is corrected is up to Google.  It certainly needs some reconstructive surgery.  </p>
<p>Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Blumenthal</title>
		<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/comment-page-1/#comment-9255</link>
		<dc:creator>Mike Blumenthal</dc:creator>
		<pubDate>Mon, 19 Mar 2007 19:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=139#comment-9255</guid>
		<description>Hi earl

The data pretty much speak for themselves, no?

I didn&#039;t check the website....that is a good idea.  If the data doesn&#039;t get cleaned up in a 2 or 3 months perhaps I will revisit.

This particular problem seems to afflict this vertical more so than others and I am not really sure why. Perhaps meidcal centers have more to worry about than their Google listing or perhaps because they are somewhat outside of the profit incentives that motivates others to get  their records squared away. 

As I pointed out, one really needs to test the OneBox results and see if the are &quot;accurate enough&quot; as I am sure that they have more impact than these results.

Mike</description>
		<content:encoded><![CDATA[<p>Hi earl</p>
<p>The data pretty much speak for themselves, no?</p>
<p>I didn&#8217;t check the website&#8230;.that is a good idea.  If the data doesn&#8217;t get cleaned up in a 2 or 3 months perhaps I will revisit.</p>
<p>This particular problem seems to afflict this vertical more so than others and I am not really sure why. Perhaps meidcal centers have more to worry about than their Google listing or perhaps because they are somewhat outside of the profit incentives that motivates others to get  their records squared away. </p>
<p>As I pointed out, one really needs to test the OneBox results and see if the are &#8220;accurate enough&#8221; as I am sure that they have more impact than these results.</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Earlpearl</title>
		<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/comment-page-1/#comment-9250</link>
		<dc:creator>Earlpearl</dc:creator>
		<pubDate>Mon, 19 Mar 2007 19:08:04 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=139#comment-9250</guid>
		<description>Mike:

You are much nicer about this stuff than me.  LOL.  And your research is great.  Did you check the actual websites also?  I&#039;d assume their contact information is more accurate.

I&#039;d think there needs to be a way to get contact information directly from existing websites rather than the directories.  

It is so easy to change those numbers all the time.  That is why websites are so terrific.  You can update them immediately and represent new accurate information...rather than something that was recorded a long time ago.

Nice research.

Dave</description>
		<content:encoded><![CDATA[<p>Mike:</p>
<p>You are much nicer about this stuff than me.  LOL.  And your research is great.  Did you check the actual websites also?  I&#8217;d assume their contact information is more accurate.</p>
<p>I&#8217;d think there needs to be a way to get contact information directly from existing websites rather than the directories.  </p>
<p>It is so easy to change those numbers all the time.  That is why websites are so terrific.  You can update them immediately and represent new accurate information&#8230;rather than something that was recorded a long time ago.</p>
<p>Nice research.</p>
<p>Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Local Data Accuracy: An Ongoing Challenge &#171; Screenwerk</title>
		<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/comment-page-1/#comment-9243</link>
		<dc:creator>Local Data Accuracy: An Ongoing Challenge &#171; Screenwerk</dc:creator>
		<pubDate>Mon, 19 Mar 2007 16:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=139#comment-9243</guid>
		<description>[...] Local Data Accuracy: An Ongoing&#160;Challenge  (Spotted via Barry at SEL) Mike Blumenthal, who writes a local search blog, has been devoting serious time to understanding the nuts and bolts and what&#8217;s under the hood at Google and Yahoo! local. He posts about the quality of basic listings data (poor) in the medical category: [...]</description>
		<content:encoded><![CDATA[<p>[...] Local Data Accuracy: An Ongoing&nbsp;Challenge  (Spotted via Barry at SEL) Mike Blumenthal, who writes a local search blog, has been devoting serious time to understanding the nuts and bolts and what&#8217;s under the hood at Google and Yahoo! local. He posts about the quality of basic listings data (poor) in the medical category: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Search Engine Land: News About Search Engines &#38; Search Marketing</title>
		<link>http://blumenthals.com/blog/2007/03/19/google-maps-medical-center-phone-data-code-red/comment-page-1/#comment-9213</link>
		<dc:creator>Search Engine Land: News About Search Engines &#38; Search Marketing</dc:creator>
		<pubDate>Mon, 19 Mar 2007 12:48:53 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=139#comment-9213</guid>
		<description>&lt;strong&gt;Analysis Of Inaccuracies In Google Local Results&lt;/strong&gt;

Mike Blumenthal has a detailed look at some of the inaccuracies Google Maps and other local search engines have when it comes to phone listings of medical centers. Mike has been following these inaccuracies for a while and has come up with a grid showi...</description>
		<content:encoded><![CDATA[<p><strong>Analysis Of Inaccuracies In Google Local Results</strong></p>
<p>Mike Blumenthal has a detailed look at some of the inaccuracies Google Maps and other local search engines have when it comes to phone listings of medical centers. Mike has been following these inaccuracies for a while and has come up with a grid showi&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 485/498 objects using disk: basic

Served from: blumenthals.com @ 2012-05-21 02:58:05 -->
