Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
XML
data.xmlanalysis
mappoint.webservice
msf
msxml-webrelease
netmyservices.sdk
passport.sdk
soap
soapsdk
uddi.general
uddi.programming
uddi.specification
xml
xmlsqlwebrelease
xsl
  
 
date: Tue, 22 Jan 2008 18:18:27 -0800,    group: microsoft.public.mappoint.webservice        back       


Best practices for selecting data sources?   
Hello, I need to be able to do an address lookup given a set of lat long 
coordinates from anywhere in the world.    I am currently using 
GetLocationInfo to do so.    However, the problem is, if I use 
"MapPoint.World" as my data source, the resulting location is too generic (it 
only returns an entity, not an address).    For example, 61.4483, 23.8544 
returns "western finland".   If I use "MapPoint.EU", then I get detailed 
address info (this is the desired result I want) of "Korkeakoulunkatu, 33720 
Tampere".      Likewise, "25.1549, 121.5217" gives me only "Taiwan" when I 
use "MapPoint.World", whereas it returns "Dengshan Rd, Taipei" when I use 
"MapPoint.AP".     

Basically, I always want the most detailed address information possible.   
It looks like I will have to dynamically determine what data source to use 
given the lat, long coordinates.    My questions are:

1.     Is there an API call I can make that returns the best data source to 
use given a lat, long?   Best being the one that gives the detailed address 
info?
2.     If not, what is the best practice for doing so?     For example, do I 
use a bounding rectangle for the various data sources, and then if the lat 
long falls within these rectangles, I use that data source (otherwise 
defaulting to world)?   If so, what are the coordinates that I should use for 
the rectangles?    Or, do I first make the call using "MapPoint.World" as my 
data source, and then do some additional logic to make a second call using a 
specific data source?   If so, what is this logic, and will I have to 
implement this logic on the client side, or does this logic already exist in 
the API?
date: Tue, 22 Jan 2008 18:18:27 -0800   author:   Jieyang

RE: Best practices for selecting data sources?   
Hi,

Your going to need to create a list of which countries belong to which 
datasource.  That way you can pick the appropriate datasource rather then 
resorting to the generic Mappoint.World.  You can refer to this list to 
determine which countries match to which datasource:

http://msdn2.microsoft.com/en-us/library/ms982193.aspx

Regards,
-- 
Infusion Development
http://www.infusion.com


"Jieyang" wrote:

> Hello, I need to be able to do an address lookup given a set of lat long 
> coordinates from anywhere in the world.    I am currently using 
> GetLocationInfo to do so.    However, the problem is, if I use 
> "MapPoint.World" as my data source, the resulting location is too generic (it 
> only returns an entity, not an address).    For example, 61.4483, 23.8544 
> returns "western finland".   If I use "MapPoint.EU", then I get detailed 
> address info (this is the desired result I want) of "Korkeakoulunkatu, 33720 
> Tampere".      Likewise, "25.1549, 121.5217" gives me only "Taiwan" when I 
> use "MapPoint.World", whereas it returns "Dengshan Rd, Taipei" when I use 
> "MapPoint.AP".     
> 
> Basically, I always want the most detailed address information possible.   
> It looks like I will have to dynamically determine what data source to use 
> given the lat, long coordinates.    My questions are:
> 
> 1.     Is there an API call I can make that returns the best data source to 
> use given a lat, long?   Best being the one that gives the detailed address 
> info?
> 2.     If not, what is the best practice for doing so?     For example, do I 
> use a bounding rectangle for the various data sources, and then if the lat 
> long falls within these rectangles, I use that data source (otherwise 
> defaulting to world)?   If so, what are the coordinates that I should use for 
> the rectangles?    Or, do I first make the call using "MapPoint.World" as my 
> data source, and then do some additional logic to make a second call using a 
> specific data source?   If so, what is this logic, and will I have to 
> implement this logic on the client side, or does this logic already exist in 
> the API?
date: Thu, 24 Jan 2008 07:34:08 -0800   author:   Derek Chan

RE: Best practices for selecting data sources?   
Okay.    I will do a call using mappoint.world to get the country the 
lat,long appears in, and then check it against a lookup table to see if its 
covered by one of the more specific data sources.   If so, I will follow up 
call with the more specific one.

In the future versions of the API, will this logic be handled by mappoint?   
  As a developer I don't really want to worry about all this location logic.  
  It means I have to maintain tables that map countries to data sources.    
It would be nice to have a simple API that I call that returns an address 
based on a lat/long.    The implementation details abstracted out; however 
using all these different data sources makes such a simplification difficult.

"Derek Chan" wrote:

> Hi,
> 
> Your going to need to create a list of which countries belong to which 
> datasource.  That way you can pick the appropriate datasource rather then 
> resorting to the generic Mappoint.World.  You can refer to this list to 
> determine which countries match to which datasource:
> 
> http://msdn2.microsoft.com/en-us/library/ms982193.aspx
> 
> Regards,
> -- 
> Infusion Development
> http://www.infusion.com
> 
> 
> "Jieyang" wrote:
> 
> > Hello, I need to be able to do an address lookup given a set of lat long 
> > coordinates from anywhere in the world.    I am currently using 
> > GetLocationInfo to do so.    However, the problem is, if I use 
> > "MapPoint.World" as my data source, the resulting location is too generic (it 
> > only returns an entity, not an address).    For example, 61.4483, 23.8544 
> > returns "western finland".   If I use "MapPoint.EU", then I get detailed 
> > address info (this is the desired result I want) of "Korkeakoulunkatu, 33720 
> > Tampere".      Likewise, "25.1549, 121.5217" gives me only "Taiwan" when I 
> > use "MapPoint.World", whereas it returns "Dengshan Rd, Taipei" when I use 
> > "MapPoint.AP".     
> > 
> > Basically, I always want the most detailed address information possible.   
> > It looks like I will have to dynamically determine what data source to use 
> > given the lat, long coordinates.    My questions are:
> > 
> > 1.     Is there an API call I can make that returns the best data source to 
> > use given a lat, long?   Best being the one that gives the detailed address 
> > info?
> > 2.     If not, what is the best practice for doing so?     For example, do I 
> > use a bounding rectangle for the various data sources, and then if the lat 
> > long falls within these rectangles, I use that data source (otherwise 
> > defaulting to world)?   If so, what are the coordinates that I should use for 
> > the rectangles?    Or, do I first make the call using "MapPoint.World" as my 
> > data source, and then do some additional logic to make a second call using a 
> > specific data source?   If so, what is this logic, and will I have to 
> > implement this logic on the client side, or does this logic already exist in 
> > the API?
date: Mon, 28 Jan 2008 13:45:00 -0800   author:   Jieyang

RE: Best practices for selecting data sources?   
You posted a Link with the available datasources. Do yo have a link what will 
display
a list of country's and for each country the datasouce to use.

"Derek Chan" wrote:

> Hi,
> 
> Your going to need to create a list of which countries belong to which 
> datasource.  That way you can pick the appropriate datasource rather then 
> resorting to the generic Mappoint.World.  You can refer to this list to 
> determine which countries match to which datasource:
> 
> http://msdn2.microsoft.com/en-us/library/ms982193.aspx
> 
> Regards,
> -- 
> Infusion Development
> http://www.infusion.com
> 
> 
> "Jieyang" wrote:
> 
> > Hello, I need to be able to do an address lookup given a set of lat long 
> > coordinates from anywhere in the world.    I am currently using 
> > GetLocationInfo to do so.    However, the problem is, if I use 
> > "MapPoint.World" as my data source, the resulting location is too generic (it 
> > only returns an entity, not an address).    For example, 61.4483, 23.8544 
> > returns "western finland".   If I use "MapPoint.EU", then I get detailed 
> > address info (this is the desired result I want) of "Korkeakoulunkatu, 33720 
> > Tampere".      Likewise, "25.1549, 121.5217" gives me only "Taiwan" when I 
> > use "MapPoint.World", whereas it returns "Dengshan Rd, Taipei" when I use 
> > "MapPoint.AP".     
> > 
> > Basically, I always want the most detailed address information possible.   
> > It looks like I will have to dynamically determine what data source to use 
> > given the lat, long coordinates.    My questions are:
> > 
> > 1.     Is there an API call I can make that returns the best data source to 
> > use given a lat, long?   Best being the one that gives the detailed address 
> > info?
> > 2.     If not, what is the best practice for doing so?     For example, do I 
> > use a bounding rectangle for the various data sources, and then if the lat 
> > long falls within these rectangles, I use that data source (otherwise 
> > defaulting to world)?   If so, what are the coordinates that I should use for 
> > the rectangles?    Or, do I first make the call using "MapPoint.World" as my 
> > data source, and then do some additional logic to make a second call using a 
> > specific data source?   If so, what is this logic, and will I have to 
> > implement this logic on the client side, or does this logic already exist in 
> > the API?
date: Tue, 12 Feb 2008 01:39:01 -0800   author:   Lanzo van Slooten Lanzo van

RE: Best practices for selecting data sources?   
I call google earth's REST api to get the country. Then i call MapPoint, with 
the correct DataSource based upon the country looked up.

The reason i use Google's REST api is because i don't want to waste my 
transactions with MapPoint if i don't really have to.

It's woeful how MapPoint is too stupid to split the info into datasources. 
they should all be in one dataseource. it shouldn't be our problem .. how do 
we know what datasource a certain lat/long is?? that's exactly why we're 
asking MP for that info!

Just another lame design decision hampering our MP development :(
date: Wed, 20 Feb 2008 16:21:02 -0800   author:   Pure Krome

RE: Best practices for selecting data sources?   
agreed, it should all be one datasource.

"Pure Krome" wrote:

> I call google earth's REST api to get the country. Then i call MapPoint, with 
> the correct DataSource based upon the country looked up.
> 
> The reason i use Google's REST api is because i don't want to waste my 
> transactions with MapPoint if i don't really have to.
> 
> It's woeful how MapPoint is too stupid to split the info into datasources. 
> they should all be in one dataseource. it shouldn't be our problem .. how do 
> we know what datasource a certain lat/long is?? that's exactly why we're 
> asking MP for that info!
> 
> Just another lame design decision hampering our MP development :(
date: Thu, 21 Feb 2008 13:28:02 -0800   author:   Jieyang

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us