<?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"
	>
<channel>
	<title>Comments on: iBegin Geocoder: Soft Launch</title>
	<atom:link href="http://www.techsoapbox.com/ibegin-geocoder-soft-launch/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techsoapbox.com/ibegin-geocoder-soft-launch/</link>
	<description>Soapboxing every damn day</description>
	<pubDate>Fri, 21 Nov 2008 01:07:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Ahmed</title>
		<link>http://www.techsoapbox.com/ibegin-geocoder-soft-launch/#comment-6167</link>
		<dc:creator>Ahmed</dc:creator>
		<pubDate>Mon, 18 Jun 2007 15:47:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.techsoapbox.com/ibegin-geocoder-soft-launch/#comment-6167</guid>
		<description>It is possible that the nearest intersection is also the nearest major intersection. 

What the system does (when doing reverse geocoding is) is figure out the closest intersection (in this case Sussex and MacKay). Afterwards it sort of spreads out, going over intersections close by, and assigning a score on how probable it is that this is the nearest major intersection. After it completes the radial search, it lists the intersection with the highest score - in this case, Sussex and MacKay again.

I will say that this isn't perfect - there is no simple way of knowing if a road is major or not. You can see at my former residence: http://geocoder.ibegin.com/geolive.php?latitude=43.671849&#038;longitude=-79.388433&#038;cross=1&#038;sup=1 - while Google Maps doesn't have Davenport displayed as a major road, most denizens of Toronto do know where Davenport and Yonge meet.

It is in-exact, and we decided it is better to include it than not to.</description>
		<content:encoded><![CDATA[<p>It is possible that the nearest intersection is also the nearest major intersection. </p>
<p>What the system does (when doing reverse geocoding is) is figure out the closest intersection (in this case Sussex and MacKay). Afterwards it sort of spreads out, going over intersections close by, and assigning a score on how probable it is that this is the nearest major intersection. After it completes the radial search, it lists the intersection with the highest score - in this case, Sussex and MacKay again.</p>
<p>I will say that this isn&#8217;t perfect - there is no simple way of knowing if a road is major or not. You can see at my former residence: <a href="http://geocoder.ibegin.com/geolive.php?latitude=43.671849&#038;longitude=-79.388433&#038;cross=1&#038;sup=1" rel="nofollow">http://geocoder.ibegin.com/geolive.php?latitude=43.671849&#038;longitude=-79.388433&#038;cross=1&#038;sup=1</a> - while Google Maps doesn&#8217;t have Davenport displayed as a major road, most denizens of Toronto do know where Davenport and Yonge meet.</p>
<p>It is in-exact, and we decided it is better to include it than not to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.techsoapbox.com/ibegin-geocoder-soft-launch/#comment-6165</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 18 Jun 2007 15:22:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.techsoapbox.com/ibegin-geocoder-soft-launch/#comment-6165</guid>
		<description>I'm thrilled that iBegin is going to be doing geocoding. It seems to fit well with the rest of the offerings.

I'm interested in the calculation method for the nearest intersection vs. major intersection.  When looking up 24 Sussex, the two have different values but list the same intersection.  Looks like a bug.


---------------------------

Geocoding Results
Geocoding for
Latitude: 45.443799
Longitude: -75.693272

Nearest Intersection:
Street 1: Sussex DR
Street 2: MacKay ST
Distance: 16 meters

Nearest Major Intersection:
Street 1: Sussex DR
Street 2: MacKay ST
Distance: 19 meters</description>
		<content:encoded><![CDATA[<p>I&#8217;m thrilled that iBegin is going to be doing geocoding. It seems to fit well with the rest of the offerings.</p>
<p>I&#8217;m interested in the calculation method for the nearest intersection vs. major intersection.  When looking up 24 Sussex, the two have different values but list the same intersection.  Looks like a bug.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>Geocoding Results<br />
Geocoding for<br />
Latitude: 45.443799<br />
Longitude: -75.693272</p>
<p>Nearest Intersection:<br />
Street 1: Sussex DR<br />
Street 2: MacKay ST<br />
Distance: 16 meters</p>
<p>Nearest Major Intersection:<br />
Street 1: Sussex DR<br />
Street 2: MacKay ST<br />
Distance: 19 meters</p>
]]></content:encoded>
	</item>
</channel>
</rss>
