We have built a locator in ArcGIS 10 SP5 which is based on the US Street - Single Address style.We have been able to tweak most other settings but are still having issues with street number scoring.Basically, we would like the locator to rank similar house numbers on the same street/town with a high score.The default action (from my testing and based on one other forum thread) seems to indicate that the locator is VERY strict about the house number matching - to the point that it will give a high ranking to an address that matches the house number and street in a town hundreds of miles away, but fail to even score the address 100' away.We have tried playing with the scoring of the FullNormalAddress, NormalAddress and House components but nothing seems to allow addresses with close house numbers in the desired city to be ranked higher than exact house number matches in a different city.For example:Search for 100 Main Street, MytownGeocoder responds with:Score: 90, Address: 100 Main Street, Yourtown (could be large distance away from Mytown and therefore totally wrong location).Yet 98 Main Street, Mytown is only two house numbers away from the desired address. I would like the locator to return something like:Score: 98, Address: 98 Main Street, MyTownScore: 50, Address: 100 Main Street, YourtownHas anyone found a solution for this? Any workarounds? Apparently this worked as desired in 9.3.1 but was "improved" in 10.0?
Phew... Thought I was having a flash back from the 60s... Again...All seriousness aside: do both the address data and the parcel data have the correct city identifier?
Yes,The city is correct in both the input address and the data from which the locator was generated.We also use an extensive alias list for city names which is working just fine.Here's a specific example:The source data has a polygon for house_number = 15, street = Barwick, street_type = road, city = TOWNSHIP OF CHAPPLEIf you query for 15 Barwick Road, Chapple you get a score of 100, which is correct (first attached image)If you query for 13 Barwick Road, Chapple you get a score of 43, matched to 13 Barwick Drive, Barrie (second attached image)Ideally, I would have gotten a hit on 15 Barwick Road, Chapple with a score close to 100 because it's at least on the right street in the right town and close to the right house number, but it fails to get any kind of score at all. Instead I get a match (albeit lower score) to the right house number but with a different street type and a totally different city.It seems that for Single House locators, the house number trumps all other address components - meaning it will force matches to the requested house number even if it has to pick the wrong street/town.
You're correct - there is no 13 Barwick Road...... but 15 is RIGHT THERE.... I can see it 😉I'm not as concerned about the 'double ding' for street type and city - we actually prefer that since it makes it more obvious that those candidates are not very similar to what was requested. The first ding on the house number is a bit of a show stopper though. It's especially annoying that it worked as desired in 9.3.1 and now it's 'broken' in 10.
For example if you have an address of 1234 Main St, but the range only goes to 1230, you'll get a partial hit at 1230. I look at that as suggestion. It's almost like the locator is saying 'Hey, I don't have exactly what you entered, but I do have this. Will it do?'
Peter,
I agree with you.... It would make sense to me that you should be able to get a partial match to an address with a similar street number (13 -> 15), but I don't know if it's possible with ArcGIS locators.
Were you ever able to find any way of tweaking the scoring or match rules?
Dan
Please vote for this idea:
ArcGIS Idea - Candidates for point address locators
The reason we don't allow incorrect house number is because this locator type is supposed to be the most accurate type of match that you can obtain. Generally we would suggest that you create a Dual Ranges locator as well and add the 2 locators to a composite locator instead. If you don't have this data, there is a way to customize the locator style template file to build a locator without requiring the house number to be correct.
What you would do is the following.
1. Open the USAddress.lot.xml file with a XML editor or text editor like Notpad++.
2. Search for "<mapping_schema ref="SingleAddressSearch" />"
3. Replace with "<mapping_schema ref="SingleAddressPolygonCentroid" />".
4. Build the locator again.
Let me know if you have any questions.
Brad
Gotta go with Brad on this one: A single address locator is just that. I have address points that I am now incorporating into my 9-1-1 dispatch locators. Sometimes a parcel or other physical address is not right along the street it is addressed to; a point is absolute.
Consequently, I'm big fan of address points for my use in geocoding and single address locators for them. I composite them with a US Streets locator so if I don't have a point or the incident is in an intersection, I'm good to go.
(Between the two 9-1-1 call centers I contract to, I'm responsible for addressing about 3,000 9-1-1 calls a day, every day. Probably a bunch more this holiday weekend. Please stay safe out there!)
Brad Niemand:there is a way to customize the locator style template file to build a locator without requiring the house number to be correct.What you would do is the following.1. Open the USAddress.lot.xml file with a XML editor or text editor like Notpad++.2. Search for "<mapping_schema ref="SingleAddressSearch" />"3. Replace with "<mapping_schema ref="SingleAddressPolygonCentroid" />".4. Build the locator again.
Brad Niemand:
there is a way to customize the locator style template file to build a locator without requiring the house number to be correct.
We tried changing the mapping_schema ref and rebuilding the locator, but did not see any change. Are there any addtional steps needed to change the scoring weight of the house number component?
Thanks,
You might need to reduce the MinimumMatchScore and/or MinimumCandidateScore for the locator.
Peter Hanmore:It's especially annoying that it worked as desired in 9.3.1 and now it's 'broken' in 10.
Peter Hanmore:
I just wanted to confirm that 9.x style locators using "one address" behave as Peter mentions. It will match to a house number that is close, but it does drop the score.
Brad Niemand I am having several issue going from 9.3 to 10 in some areas. First my locator doesn't seem to want to match in my code, but matches perfectly in ArcMap 10.7. Worked perfectly in 9.3. I am using a Single Address locator Style for this locator because the shp file I was given for this client only has the address (611 N CLAY ST) and City (NEVADA).
Also, seem to be having a huge issue with trying to open my CSV file, that worked perfectly in 9.3, but fails in 10.7.
// Create pTable from .csv file... IWorkspaceFactory pFact = new TextFileWorkspaceFactory(); IWorkspace pWorkspace = pFact.OpenFromFile(LocalFolder, 0);
IFeatureWorkspace pFeatws = (IFeatureWorkspace)pWorkspace; ITable pTable = pFeatws.OpenTable(CSVFile); //open the .csv file... -- FAILS
Could you please help me with this. I have been posting the last issue, but nobody is answering and I have a huge time constraint on this.
Thanks
Elizabeth
Elizabeth- where have you posted your questions? I try to stay on top of geocoding problems too.
Locators took a quantum leap from 9.3 to 10.3 and there are a number of changes since then too. I'd like to see your other posts; Brad has been responsive to mine, and I'll loop in Eric Anderson ; he's another great resource..
Edtied moments later: Elizabeth, I found your arcobjects sdk post; sounds like you have two issues, right? The csv errors along with geocoding results?
Joe, I have replied to this one: OpenTable
Created this one: Can't open CSV File in 10.7
And I think one other, but I can't remember.
I sure hope you can help me with this. On a really big time crunch.
Yes so far those two are crucial. I am sure there will be others as I move through this.
Elizabeth,
What are you trying to do with your code above? I know you are trying to open a CSV file via ArcObjects but what will that be fed into? Will you be geocoding it?
The reason I ask is that there might be an easier way to do this with geoprocessing.
What is happening, is CAD/Mobile creates a call. The list of active calls are then put into a csv file where it is created into a shape file and added to the map.
When you say created into a shape file do you mean that the CSV file is geocoded with the locator to create the shape file?
I am not an ArcObjects expert but can get my way around the geocoding ArcObjects code. If the CSV is getting geocoded, I would be curious as to how it is getting done right now because I might have an easier way to do it with geoprocessing in C#.
Set that property to 1 or set it in the .loc file.
Yeah it is. I am not sure what is throwing the error and why it can't access it. I am loading from an MXD file, but it has already loaded at this point. So don't think that is it. We can discuss more tomorrow, if possible. I probably have a lot of code that is way more work than it needs to be. And I am sure we will be upgrading to Pro at some point, which is different as well.
Brad Niemand This is the full message I am getting when the GP.Execute fails:
I have attached my csv file I am trying to work with. I am wondering if there might be something wrong in the formatting? Since things have changed.
Elizabeth- just curious as to what CAD/Moblie app you are using....
Well right now, this is just a testing app. But we have our own CAD/Mobile solutions in house.
Are your locator fields StreetName and City? StreetName doesn't sound like an out of the box locator field name. You can run the table through the GeocodeAddresses GP tool in ArcMap and then look at the GP result to see what the field mapping was to confirm. You may have done this already because you have the "VISIBLE NONE" as part of the string that isn't really needed but it part of the output from the tool.
Is your locator just one USAddress - Single House locator or is it part of a composite or anything else that can give me some additional clues? Just to confirm, were you able to geocode the CSV with the GeocodeAddresses GP tool in ArcMap with no issue?
Actually I am using Single Field because my address is all in one field (611 N CLAY ST). I have tried one address too, but wasn't getting anywhere with that either.
StreetName is what came in the VernonCountyMO_Addresses.shp file I was given.
Do I need to run GeoCode against this, because I have. And I was going to use it on the map, but my points were no longer showing up.
UPDATE: I did run Geocoding against the shapefile and did get my points to show up. So I must have fixed something. LOL. But still getting an error either trying to open the csv file or using the GP.Execute. Seems to be the same error. I was able to GeoCode that csv file as well. I am using windows 10, which I hope doesn't make a difference.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
