<?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: New Meetinghouse Locator on LDS.org &#8211; Beta Release</title>
	<atom:link href="http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/feed/" rel="self" type="application/rss+xml" />
	<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/</link>
	<description>Sharing technology ideas for LDS parents and youth</description>
	<lastBuildDate>Sat, 07 Nov 2009 17:31:52 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ted</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15934</link>
		<dc:creator>Ted</dc:creator>
		<pubDate>Wed, 02 Jul 2008 20:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15934</guid>
		<description>Thanks everyone for all the feedback. The enhancement requests have all been noted. I&#039;ll probably stop checking this post for new ideas, so anything else should be funneled through the Feedback link on the site. Thanks again!</description>
		<content:encoded><![CDATA[<p>Thanks everyone for all the feedback. The enhancement requests have all been noted. I&#8217;ll probably stop checking this post for new ideas, so anything else should be funneled through the Feedback link on the site. Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Nico</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15917</link>
		<dc:creator>Matt Nico</dc:creator>
		<pubDate>Tue, 01 Jul 2008 14:53:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15917</guid>
		<description>I&#039;ll vote up ward boundaries being delineated on the map.

I&#039;m also wondering if there&#039;s any way to tap into the information available on the site.  I&#039;m creating some all-inclusive mapping software that helps LDS people when they relocate to a new area.  I&#039;m wondering if there&#039;s a way I can find out which ward each home in a group of listings is located in.  Is there an API for that?</description>
		<content:encoded><![CDATA[<p>I&#8217;ll vote up ward boundaries being delineated on the map.</p>
<p>I&#8217;m also wondering if there&#8217;s any way to tap into the information available on the site.  I&#8217;m creating some all-inclusive mapping software that helps LDS people when they relocate to a new area.  I&#8217;m wondering if there&#8217;s a way I can find out which ward each home in a group of listings is located in.  Is there an API for that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15874</link>
		<dc:creator>Ted</dc:creator>
		<pubDate>Sat, 28 Jun 2008 05:05:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15874</guid>
		<description>Hey Brian -- killer schedule! Good luck with that. Hope this is an improvement. The meeting times are up to the local wards and branches to keep updated.</description>
		<content:encoded><![CDATA[<p>Hey Brian &#8212; killer schedule! Good luck with that. Hope this is an improvement. The meeting times are up to the local wards and branches to keep updated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian J. Hill</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15863</link>
		<dc:creator>Brian J. Hill</dc:creator>
		<pubDate>Thu, 26 Jun 2008 20:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15863</guid>
		<description>THANK YOU!!!!!
My job requires me to be in a new town EVERY week (currently I&#039;ve been in a new ward each week for 83 consecutive weeks,) and I&#039;ve had a terrible time using the old meetinghouse locator.  The interface was terrible and Mapquest isn&#039;t nearly as useful as Google or Microsoft maps.  I&#039;m sooooo glad there&#039;s a new version.  One suggestion:  I&#039;ve found that the meeting times on the old meetinghouse locator weren&#039;t always accurate, meaning I&#039;d end up missing church for that week.  If there&#039;s a way of updating the meeting times more otften than with the old locator, I sure would appreciate it!</description>
		<content:encoded><![CDATA[<p>THANK YOU!!!!!<br />
My job requires me to be in a new town EVERY week (currently I&#8217;ve been in a new ward each week for 83 consecutive weeks,) and I&#8217;ve had a terrible time using the old meetinghouse locator.  The interface was terrible and Mapquest isn&#8217;t nearly as useful as Google or Microsoft maps.  I&#8217;m sooooo glad there&#8217;s a new version.  One suggestion:  I&#8217;ve found that the meeting times on the old meetinghouse locator weren&#8217;t always accurate, meaning I&#8217;d end up missing church for that week.  If there&#8217;s a way of updating the meeting times more otften than with the old locator, I sure would appreciate it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15843</link>
		<dc:creator>Ted</dc:creator>
		<pubDate>Wed, 25 Jun 2008 21:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15843</guid>
		<description>Also see comments and responses on http://www.ldscio.org/2008/06/21/moving-forward/#comments</description>
		<content:encoded><![CDATA[<p>Also see comments and responses on <a href="http://www.ldscio.org/2008/06/21/moving-forward/#comments" rel="nofollow">http://www.ldscio.org/2008/06/21/moving-forward/#comments</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LDS Art Collector</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15836</link>
		<dc:creator>LDS Art Collector</dc:creator>
		<pubDate>Wed, 25 Jun 2008 15:24:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15836</guid>
		<description>Great Post</description>
		<content:encoded><![CDATA[<p>Great Post</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New LDS Meeting House Locator - Corndogs + Avocados</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15808</link>
		<dc:creator>New LDS Meeting House Locator - Corndogs + Avocados</dc:creator>
		<pubDate>Sun, 22 Jun 2008 18:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15808</guid>
		<description>[...] LDS Media Talk lists many new features not available on the current meetinghouse locator, including: [...]</description>
		<content:encoded><![CDATA[<p>[...] LDS Media Talk lists many new features not available on the current meetinghouse locator, including: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silus Grok</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15807</link>
		<dc:creator>Silus Grok</dc:creator>
		<pubDate>Sun, 22 Jun 2008 04:52:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15807</guid>
		<description>… another reason to have unit boundaries!

YAY!</description>
		<content:encoded><![CDATA[<p>… another reason to have unit boundaries!</p>
<p>YAY!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CuriousGIS</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15803</link>
		<dc:creator>CuriousGIS</dc:creator>
		<pubDate>Sat, 21 Jun 2008 14:34:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15803</guid>
		<description>This is a big improvement over the current meetinghouse locator, the membership will enjoy it. It did have issues with rural route / box addresses. Then again I am assuming they are using a standard geocoder to find addresses. Most rural routes will never geocode using standard fair street data. 

To help those that do have rural routes and or places where they do not have a street files, and/or the geocoder source data is not robust they should include a layer to view the boundaries of the units. I searched for a few rural routes in our unit and none of them even came close to being properly geocoded. I also tried some less developed countries and the application would tell me to please wait while it searched but never continue. 

If they set up multiple geocoders the application could try each in turn until it had a match, for those areas that it could not find a good match it could return the boundaries of the units/stakes based on city, state equivalent, or even country.</description>
		<content:encoded><![CDATA[<p>This is a big improvement over the current meetinghouse locator, the membership will enjoy it. It did have issues with rural route / box addresses. Then again I am assuming they are using a standard geocoder to find addresses. Most rural routes will never geocode using standard fair street data. </p>
<p>To help those that do have rural routes and or places where they do not have a street files, and/or the geocoder source data is not robust they should include a layer to view the boundaries of the units. I searched for a few rural routes in our unit and none of them even came close to being properly geocoded. I also tried some less developed countries and the application would tell me to please wait while it searched but never continue. </p>
<p>If they set up multiple geocoders the application could try each in turn until it had a match, for those areas that it could not find a good match it could return the boundaries of the units/stakes based on city, state equivalent, or even country.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://ldsmediatalk.com/2008/06/19/new-meetinghouse-locator-on-ldsorg-beta-release/comment-page-1/#comment-15800</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Sat, 21 Jun 2008 00:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldsmediatalk.com/?p=359#comment-15800</guid>
		<description>Greg,
We are using ESRI&#039;s ArcGIS Manager on the back end to do proximity analysis (closest meetinghouses) and to query the Church layers to see which wards/branches are at a location.  We have also created a custom geocoder for certain high-growth areas in Utah and other locations that is being published and used by ArcGIS Manager.

Thanks for all the comments!</description>
		<content:encoded><![CDATA[<p>Greg,<br />
We are using ESRI&#8217;s ArcGIS Manager on the back end to do proximity analysis (closest meetinghouses) and to query the Church layers to see which wards/branches are at a location.  We have also created a custom geocoder for certain high-growth areas in Utah and other locations that is being published and used by ArcGIS Manager.</p>
<p>Thanks for all the comments!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
