1
Vote

Problem with inbound Data

description

Hi,
i have the following problem:
I take small data from db and make a request with mappoint batch geocoder. The request is successfull as i can see on my virtual earth platform. a download-file is built with the right information.
Unfortunately I just receive the following error message:

Error: 0xC0047062 at MappointWebServiceTest, MapPoint Batch Geocoder [19]: System.FormatException: 24201: Latitude values must be between -90 and 90 degrees.
at Microsoft.SqlServer.Types.SqlGeography.Point(Double latitude, Double longitude, Int32 srid)
at MapPointBatchGeocoder.GeocoderTransformation.NewGeoPoint(String latitude, String longitude)
at MapPointBatchGeocoder.GeocoderTransformation.FlushCurrentBatch()
at MapPointBatchGeocoder.GeocoderTransformation.ProcessInput(Int32 inputID, PipelineBuffer buffer)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100 wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket)
Error: 0xC0047022 at MappointWebServiceTest, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "MapPoint Batch Geocoder" (19) failed with error code 0x80131537 while processing input "Input" (21). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.

I was searching for the right function in the geocode and put constant values instead of receiving data from mappoint. In fact my solution is working then, but not in the way it should do...
 
Has anybody some experience with this problem? Thanks.

comments

datherton wrote May 14, 2010 at 6:14 PM

Not too sure if this is relevant now but SQL 2008 Spatial had changed format from lat/long to long/lat so, in short, reverse the values and should be OK...
Just downloading the source now and will take a look to see if that is the issue...
Dave

wrote Feb 13, 2013 at 8:35 PM