Comments on: links for 2006-10-11 http://highearthorbit.com/links-for-2006-10-11/ Transmitting ideas, observations, and images from 42,000 km. Tue, 07 Feb 2012 14:15:16 -0800 http://wordpress.org/?v=2.9-rare hourly 1 By: 8eff2c48f75a http://highearthorbit.com/links-for-2006-10-11/comment-page-1/#comment-176184 8eff2c48f75a Thu, 15 May 2008 01:57:24 +0000 http://highearthorbit.com/links-for-2006-10-11/#comment-176184 <strong>8eff2c48f75a...</strong> 8eff2c48f75a4065e13e... 8eff2c48f75a…

8eff2c48f75a4065e13e…

]]> By: Andrew http://highearthorbit.com/links-for-2006-10-11/comment-page-1/#comment-50144 Andrew Wed, 11 Oct 2006 23:48:03 +0000 http://highearthorbit.com/links-for-2006-10-11/#comment-50144 Underneath, BoomTrek is using GeoNome, which claims "FREE Geo-Location Technology API for Software Web Developers and Mapping Applications" - though you have to contact them to find out. BoomTrek is then just building up the application on top of the tech, but obviously they also then have to be aware of what happens to their business if that tech fails. Underneath, BoomTrek is using GeoNome, which claims “FREE Geo-Location Technology API for Software Web Developers and Mapping Applications” – though you have to contact them to find out.

BoomTrek is then just building up the application on top of the tech, but obviously they also then have to be aware of what happens to their business if that tech fails.

]]> By: Will http://highearthorbit.com/links-for-2006-10-11/comment-page-1/#comment-50131 Will Wed, 11 Oct 2006 17:26:06 +0000 http://highearthorbit.com/links-for-2006-10-11/#comment-50131 The geo-identifier at Boomtrek is behaving interestingly. It correctly deduced that I was in Arlington, VA, but it chose the wrong Arlington, VA when giving mileage estimates, believing I was far closer to Staunton than I actually am. Also odd was the problem that Navtek users can recognize -- overly specific identifications. Washington, DC, is listed as a separate entry from District of Columbia, and therefore receives a slightly different distance calculation. It seems like there should be a tag that can discern that Washington and D.C. are the same, just as there should be some type of comparison that asks which of the three Arlington, VA I am currently in. While Google Maps can find the proper Arlington, Mapquest identifies Arlington, Arlington County, VA; Arlington, Hopewell City, VA; and Arlington, Northampton County, VA. The geo-identifier at Boomtrek is behaving interestingly. It correctly deduced that I was in Arlington, VA, but it chose the wrong Arlington, VA when giving mileage estimates, believing I was far closer to Staunton than I actually am.

Also odd was the problem that Navtek users can recognize — overly specific identifications. Washington, DC, is listed as a separate entry from District of Columbia, and therefore receives a slightly different distance calculation. It seems like there should be a tag that can discern that Washington and D.C. are the same, just as there should be some type of comparison that asks which of the three Arlington, VA I am currently in. While Google Maps can find the proper Arlington, Mapquest identifies Arlington, Arlington County, VA; Arlington, Hopewell City, VA; and Arlington, Northampton County, VA.

]]>