ThinkGeo.com    |     Documentation    |     Premium Support

Issues moving from dll 9.0.0.142 to 9.0.0.335

#1

We have tried to change out the dll for our application to a newer dll (9.0.0.335). When we do this, our application no longer works. Our application is used for reverse geocoding. We noticed the the file size seems significantly smaller than the 9.0.0.142 version. I checked the releases and since this isn’t a major release, I don’t see the documentation. The main function we are using is geocoder.match. After doing some tracing through the program, it looks like we aren’t getting values for state and city for the array that is returned. Did those names change perhpas?

#2

Hi Kiffany,

I compared with the two version and didn’t found any changes and I found there are many changes between Development version. Please make sure that you are using Production Version 9.0.0.142 and 9.0.0.335. Could you please provide us your data or where do you search?

This image shows the size of the two version and there is no changes.

Pasted image749×370 30.7 KB

Thanks,
Peter

#3

Thanks! I went back and looked again and it looks like it is actually the 9.0.0.0 version which is what we got when we first bought our license. I tried to upload the DLL, but it wouldn’t accept that file extension.

#4

Hi Kiffany,

I did some tests with our data and was unable to recreated your issue. Could you please provide a sample to help us to recreated this issue?

Attached is the screenshot shows the test results, the upper shows the result by referencing version 9.0.0.335 and the lower shows the result of version 9.0.0.142.

Pasted image1207×886 260 KB

Thanks,
Peter

#5

We are using the following to get the state and city to return. Our log file shows it isn’t returning. With the older DLL it returns, but we can’t get it to return on the newest one. Please Note: We just tested the current development version and City/State are returned. We think there is an issue with the current DLL

Class: GeocoderMatch
Property: State

Class: GeocoderMatch
Property: City

M [CityAliasAbbreviation, ]
6/12/2016 7:22:07 PM [CityAlias, PRATTVILLE]
6/12/2016 7:22:07 PM [CountyFIPS, 001]
6/12/2016 7:22:07 PM [TimeZone, CentralStandardTime]
6/12/2016 7:22:07 PM [StateFIPS, 01]
6/12/2016 7:22:08 PM [BoundingBox, POLYGON((-86.4840713195946 32.4725416622838, -86.4740713195946 32.4725416622838, -86.4740713195946 32.4625416622838, -86.4840713195946 32.4625416622838, -86.4840713195946 32.4725416622838))]
6/12/2016 7:22:08 PM [CentroidPoint, POINT(-86.4790713195946 32.4675416622838)]
6/12/2016 7:22:08 PM Matches Found - Starting Try …2a: 0::
6/12/2016 7:22:08 PM STATE NOT FOUND
6/12/2016 7:22:08 PM Matches Found - Starting Try …2a2
6/12/2016 7:22:08 PM CITY NOT FOUND
6/12/2016 7:22:09 PM Matches Found - Starting Try …2a3
6/12/2016 7:22:09 PM Matches Found - Starting Try …2a4
6/12/2016 7:22:09 PM Matches Found - Starting Try …2a5
6/12/2016 7:22:09 PM Matches Found - Starting Try …2a6

#6

Hi Kiffany,

This issue may be caused by the Geocoder files? Do you use “GeoCoderIndex 2015 v2” in the application? The release versions support the old Geocoder files, but not supports the “GeoCoderIndex 2015 v2”.

In order to support the “GeoCoderIndex 2015 v2” format files, we did many changes in development branch, but these changes are not merged into the release branch.

Attached shows the file information of Geocoder “GeoCoderIndex 2015 v2”.

Pasted image758×618 74.6 KB

If it’s not the point, could you please tell us how to reproduce this issue? Such as, the input address or lon/lat.

Thanks,
Peter

#7

We are using GeocoderIndex 2015. We got an updated dataset from sales on 2/25 and that is the index that came with it. We get a zip and address to come back, but no state or city.

Try the following:
BlockGroup Longitude Latitude
010010201001000 -86.480959 32.4696831
010010201001001 -86.4780003 32.4669232
010010201001002 -86.4869919 32.4709172
010010201001003 -86.4889319 32.4690894
010010201001004 -86.4792922 32.4635024
010030104001008 -87.6324489 30.8485663
040019426001000 -109.759147 36.9155339
040120202013007 -114.1757436 34.2433401
010379612002050 -86.0145625 32.8764692
010630602003004 -87.8372216 32.7419323
040050023001242 -112.5317889 35.8344561
040050023001243 -112.6265932 35.8138887
040050023001244 -112.6665843 35.8832762
040050023001245 -112.6575374 35.7856433
040050023001246 -112.6271121 35.808676
040050023001247 -112.6082772 35.8626847

#8

Hi Kiffany,

I guess the “GeocoderIndex 2015” used in your application is the same one as my mentioned “GeoCoderIndex 2015 v2”. Please try using development branch instead.

I got the news from our manager and these changes will be merged into Release branch in version 10.0 which will be published this year.

Sorry for any inconvenience.

Thanks,
Peter

#9

Based on the file sizes and dates, we think it might be V2. Do you see any issues with us using the development branch dll for our prod product? We did validate that it works.

#10

Hi Kiffany,

Just recreated your issue with our data in release branch and development branch works well.

Thanks,
Peter

#11

okay, so just to confirm. You don’t see any issues with us using the development version for our prod product. I think somewhere it cautions you on doing that. We are using it in development now to test it, but just want to make sure this is a good interim solution until release 10 comes out.

#12

Hi Kiffany,

It’s OK. Please wait for the release 10.0.

Thanks,
Peter