none
Geocode Dataflow performance RRS feed

  • Question

  • Hi There:

    Is anybody experiencing a very slow responce time for Geocode Dataflow REST.

    I takes me about 20 to get the geocode result of 40 addresses.

    thx

    • Moved by Ricky_Brundritt Friday, March 9, 2012 2:15 PM (From:Bing Maps: Map Control and Web services Development)
    Sunday, December 26, 2010 10:29 PM

Answers

  • I don't believe there is a guarantee that any dataflow job will finish within an expected time limit. However, for 2000 records you could consider geocoding each address separately rather than use the dataflow service if you need a better known response time. The dataflow service may have been slow lately, but I would consider dataflow to be quicker than single-record geocoding each address, and you also get your results in a defined format.
    Wednesday, December 29, 2010 10:42 PM

All replies

  • Can you clarify the time units  i.e. 20 minutes/seconds/hours. Note that the geocode dataflow is meant to be a batch process. This type of process will take some time to run.
    Windows Live Developer MVP - http://rbrundritt.spaces.live.com | http://inknowledge.co.uk
    Tuesday, December 28, 2010 3:55 PM
  • HI Richard

    A batch job of 40 addresses takes about 25 seconds to return. When I release the project I might have scenarios where I need to geocode 2000 adddresses. I believe that the DataFlow might not be the approach for me to take. What do you think?

    On a different note ( i have been follwing your threads ) Im working on the Silverlight control I have a situation where I reduce polygons on the server based on the LocationRect I pass from the client. My problem is when I have the east cooridinate less than the west, I know its a common scenario but I haven't found the right algorithim to get the right east and west points. Can you direct me please?

    thanks in advance

    Roi 

    Tuesday, December 28, 2010 4:01 PM
  • I don't believe there is a guarantee that any dataflow job will finish within an expected time limit. However, for 2000 records you could consider geocoding each address separately rather than use the dataflow service if you need a better known response time. The dataflow service may have been slow lately, but I would consider dataflow to be quicker than single-record geocoding each address, and you also get your results in a defined format.
    Wednesday, December 29, 2010 10:42 PM
  • Hello Roi

    The issue with DataFlow GeoCode REST is something I noticed since last week. But ideally DataFlow is the correct approach for batch geocoding.

     


    Aditya Tadakaluru MCPD, MCITP, MCTS(Bing Maps)
    Tuesday, January 4, 2011 8:57 PM
  • Just to add to this topic. Just so people know the Geocode Dataflow service is meant to be a replacement for the MapPoint Customer Data service. These MapPoint services often took 20+ minutes to geocode data. This service is not meant to be used by client facing applications and it should be noted that there is a limit on the 50 geocode jobs in a 24 hour s period as noted here: http://msdn.microsoft.com/en-us/library/ff701733.aspx
    Windows Live Developer MVP - http://rbrundritt.spaces.live.com | http://inknowledge.co.uk
    Wednesday, January 26, 2011 1:58 PM