|
POST
|
The table inputs seem fine. Did you have any luck figuring out what the issue was with your addresses?
... View more
04-28-2011
09:29 AM
|
0
|
0
|
975
|
|
POST
|
The score should be lowered. In this case I am trying to teach how to find the errors and evaluate them plus how to use the geolocator. Although I think the way the zipcode is ignored is an error. You cannot assume that the address you are trying to locate is in the range of the geolocator. For instance if you were trying to geolocate participants at a local event, you could get participants from out of state thus with a valid zipcode that should not match to your locator. A correction to your statement above. The problem isn't that the zipcode is ignored, it is that the city and state are not ignored. Let me clarify. With zones (city, state, and zip), the locator tries first to search for the zip in the dictionary (think of the dictionary as exact match even though that is not exactly true). If the zip is found, then it uses city and state ONLY for scoring, not for restricting search. It then tries to find the street in this zipcode. If the final score of the search is higher than the minimum match score, then it will stop and return the matched address. If not, it will try to search for the city and state in the dictionary and use zipcode only for scoring. So what happens is that the first search fails because there is no street in that zipcode that matches higher than the minimum match score. Therefore the locator "falls back" to the city and state. What happens is the locator compares "empty city" and "empty state" to empty dictionary and therefore matches. It then reduces the score because the zipcode is wrong but the score is not reduced by very much because it thinks that the city and state are correct in this case and gives them both a score of 100. I have attached a style that does not include city and state that will give you some better results for now.
... View more
04-26-2011
10:49 AM
|
0
|
0
|
1714
|
|
POST
|
I can update the style for you. Would you like the score to be much lower or not return anything at all? Brad
... View more
04-25-2011
02:06 PM
|
0
|
0
|
1714
|
|
POST
|
I have attached a locator style that fixes the issues that you are seeing.
... View more
04-25-2011
02:00 PM
|
0
|
0
|
2626
|
|
POST
|
I have attached a style that will work with Apartment Units. Let me know if you have any issues. Brad
... View more
04-25-2011
01:58 PM
|
0
|
0
|
3977
|
|
POST
|
Yes you are correct. The minimum match score out of the box is set to 85 so because of the issue of the unmapped fields, in your case city and state, you will get matches for 5 digit zip codes entered that are incorrect. One work-around is setting the minimum match score of the locator to a higher value like 96. The other would be to modify style to help alleviate the issue. Brad
... View more
04-25-2011
01:09 PM
|
0
|
0
|
1714
|
|
POST
|
My first thought would be that you don't have access to the location that you are trying to create the locator in. Brad
... View more
04-25-2011
12:33 PM
|
0
|
0
|
1691
|
|
POST
|
I would first recommend installing 10.0 SP1 and see if that solves your issues. Brad
... View more
04-25-2011
12:27 PM
|
0
|
0
|
1151
|
|
POST
|
NIM055232 fixes the opposite of the issue that you are having, no matches would occur if the locator is built without all of the zone fields mapped. There is an issue where the score is higher than expected when a locator is built with not all of the zone fields mapped. Essentially, the locator assumes that, in your case, the city and the state field have a score of 100 and the zip has a score of 0. This increases the total score of the address and therefore can be a bit confusing. There are a couple work-arounds that we can try and use if you would like. The first would just be to increase the minimum match score to something like 96. Another option would be for me to provide an updated style for you in which you could build your locator from. Just let me know what works best for you and sorry for the inconvenience. Brad
... View more
04-25-2011
12:12 PM
|
0
|
0
|
1714
|
|
POST
|
What locator are you using? Also, what version of ArcGIS are you using and can you provide some more detail to your question? I am not too sure what you are looking for. Brad
... View more
04-25-2011
12:04 PM
|
0
|
0
|
975
|
|
POST
|
I am not too sure why it fails but I built you a locator that fixes the issue. I had to use SP2 RC to get it to work. Unfortunately, SP2 is not released yet and just updating the locator style for SP1 wont work either. The zip file is too large to post but I can send it to you if you would like. Just email me. Brad bniemand@esri.com
... View more
04-15-2011
01:45 PM
|
0
|
0
|
2281
|
|
POST
|
If you have 10.0 without SP1, I would try to apply SP1. See the following link. http://resources.arcgis.com/content/kbase?fa=articleShow&d=38314 Brad
... View more
04-14-2011
02:11 PM
|
0
|
0
|
2281
|
|
POST
|
Were your locators built with no city and zip fields? Brad
... View more
04-11-2011
12:02 PM
|
0
|
0
|
994
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 04-25-2014 08:21 AM | |
| 1 | 07-31-2025 10:52 AM | |
| 1 | 11-15-2024 09:08 AM | |
| 1 | 07-15-2022 02:04 PM | |
| 1 | 09-24-2021 03:08 PM |
| Online Status |
Offline
|
| Date Last Visited |
08-13-2025
11:50 AM
|