Locator Style for Apt or Units

Is there any plan to roll a unit locator style such as those posted here into the core product? We need to build something similar but I am not keen on using something that is not officially supported.

DanMcCoy

Is there any plan to roll a unit locator style such as those posted here into the core product? We need to build something similar but I am not keen on using something that is not officially supported.

You can vote for the idea to increase the chance of ESRI considering it...
http://ideas.arcgis.com/ideaView?id=08730000000by67

DarrochKaye

I have attached a locator style that fixes the issues that you are seeing.

I am still seeing the # marks as described above when using the second file provided. Do I need a service pack to sort this? I'm currently not running any service parks on ArcGIS 10 Desktop.

Thanks,
DK

JeffWard

I have been using this locator style for a while now, but I have run into a problem when a hyphen seperates a building and unit number. For example, in my reference data I have the unit numbers in the format of #6A (building 6 unit A), but the table I am trying to match uses a hyphen like #6-A. The score is dropped to 56.34 and and any unit with the same building number gets the same score (#6A and #6B etc get the same 56.34 score). What do I need to modify to get #6-A to match #6A without a score penalty?

Thanks

RoyJackson1

All,

I will throw my version into the ring. There is another thread on the forums that covers some of this, but in a nutshell the attached style handles addresses with fractional addresses as well as units. Full disclosure: I made my best attempt at customizing my own locator style but it ended up having some minor "quirks" that I simply could not resolve. Brad, from ESRI, made some edits to the style that resolved the quirks--at least in my case.

Tracy is correct that the white paper does not go quite far enough with information about customizing. And I echo the need for this style to be included in the core product. I just promoted the idea linked above.

This download link is dead...

US One Address with Units - Issaquah.zip.zip

Roy,

I just noticed your post, so I am attaching the file again.

Brian

Is this for 9.3? The file I found here is not xml.

Roy,

I just noticed your post, so I am attaching the file again.

Brian

Sorry but this link has the same problem as your older post (#10)... The attachment can't be downloaded.

Whoops! In my haste I grabbed the old style. Attached should be the latest. Apologies to all...

Brian

Bill,

I'm not sure why my attachment is not working correctly. Post #35 in the link below should be the same file after Brad from ESRI made some tweaks. There is a lot that the white paper fails to cover...

http://forums.arcgis.com/threads/28535-Geocoding-Addresses-with-Apartment-Units?p=128250&viewfull=1#post128250

I "re-zipped" the file and I am attaching it yet again, but I am guessing that it is a problem with the system and not the file specifically.

Brian

USAddressWithUnit.lot.zip

That did it. Thanks!

Bill,

I'm not sure why my attachment is not working correctly. Post #35 in the link below should be the same file after Brad from ESRI made some tweaks. There is a lot that the white paper fails to cover...

http://forums.arcgis.com/threads/28535-Geocoding-Addresses-with-Apartment-Units?p=128250&viewfull=1#post128250

I "re-zipped" the file and I am attaching it yet again, but I am guessing that it is a problem with the system and not the file specifically.

Brian

Bill,

I'm not sure what was wrong with the original zip file but I am glad it now works! Let me know how it works (if it works) for you.

Brian

I see many of the same parsing issues with this locator that Roy Jackson describes here: http://forums.arcgis.com/threads/28535-Geocoding-Addresses-with-Apartment-Units?p=208831&viewfull=1#post208831. For example, "999 Little Knoll Lane" is standardized as HN: "999", SN: "Little", ST: "Knl", UN: "Lane".

Bill,

...Let me know how it works (if it works) for you.

Brian

This is an old thread but 10.2 does not seem to support any of the locators provided here. Does anyone have a 10.2 version that supports units. How many more years are we going to have to chase these down in forum threads instead of this being a core locator in the product?

Thanks in advance for any help!

@Bill,

I got really busy with other stuff and failed to respond to your post from June. I suspect you are getting similar standardization issues as the other style because they are mostly the same style "under the hood". As I have mentioned in this and/or other similar posts, I simply modified esri's existing style to add fractionals and units (with some additional tweaking by Brad from esri because the white paper doesn't go into enough detail). So the modified style is just taking into account additional fields and retains whatever issues might exist in the original style from which it was based.

@Ronnie,
I haven't upgraded to 10.2 yet, so I have no idea if I will experience the same issue nor do I have any way to test. That the 10.1 locators do not work in 10.2 is very unsettling.

@All,
If you even remotely agree that these styles belong in the style list by default, please vote for the idea that is linked in response #8. It is likely the only way esri will listen to our pleas.

My apologies the custom locator for units is working in 10.2, after I completely removed it and recreated my locator tools. I think my problem was due to model builder keeping the names of the Locator Styles and not truely refreshing them based on the environment. Creating a new model to Rebuild the indexes seemed to resolve the issue.

Still I am tired of dealing with these customization's on 100+ workstations and server environments after every upgrade or installation.Please vote to make this a core locator style, it is time.

Also please update the locator whitepaper from 10.0 it is missing many important aspects that are important for Local Government use cases.

Thanks for the follow-up regarding 10.2. And also thanks for the Model Builder comment. I imagine I would be pulling my hair out over that one.

RussellProvost

Bill,

I'm not sure why my attachment is not working correctly. Post #35 in the link below should be the same file after Brad from ESRI made some tweaks. There is a lot that the white paper fails to cover...

http://forums.arcgis.com/threads/28535-Geocoding-Addresses-with-Apartment-Units?p=128250&viewfull=1#post128250

I "re-zipped" the file and I am attaching it yet again, but I am guessing that it is a problem with the system and not the file specifically.

Brian

Brian,

Thanks so much for sharing your locator. I too have taken the leap into the black box of customizing address locators for address units. I noticed that your locator style can differentiate between apartment numbers. However, if an address is being matched without an apartment number (123 Main Street), but the reference data contains unit information for this address (123 Main Street, Apt. 1 or 123 Main Street, Apt.2) the matching algorithm will return a score of 100 for each instance in the reference data with the same primary address. I cannot solve this behavior in my locator either. Ideally the scoring would be slightly penalized for the matches with unit information. Any suggestions?

I've noticed the "equal successful match" scoring as well. I think it is because the locator successfully matched all of the portions of the address you entered. All of individual units are technically 100% successful matches because you didn't differentiate the address with a unit.

I'm willing to bet that there is a technique to "float" the non-unit address to the top and "penalize" the matches that include a unit, as you describe. Unfortunately, the white paper is sorely lacking, and I have had no success digging anything up in online help (though I haven't tried lately, so maybe things have changed in that regard). I think Brad or another esri employee "in the know" might be able to provide more info.

RussellProvost

I have attached a locator style that fixes the issues that you are seeing.

Brad,

Thank you for your continued persistence with developing locators that will match at the subaddress level. I noticed that your locatorstyle can differentiate between apartment numbers. However, if an address is being matched without an apartment number (123 Main Street), but the reference data contains unit information for this address (123 Main Street, Apt. 1 or 123 Main Street, Apt.2) the matching algorithm will return a score of 100 for each instance in the reference data with the same primary address. I cannot solve this behavior in my locator either. Ideally the scoring would be slightly penalized for the matches with unit information. Any suggestions?

SteveGay3

My apologies the custom locator for units is working in 10.2, after I completely removed it and recreated my locator tools. I think my problem was due to model builder keeping the names of the Locator Styles and not truely refreshing them based on the environment. Creating a new model to Rebuild the indexes seemed to resolve the issue.

Still I am tired of dealing with these customization's on 100+ workstations and server environments after every upgrade or installation.Please vote to make this a core locator style, it is time.

Also please update the locator whitepaper from 10.0 it is missing many important aspects that are important for Local Government use cases.

Do you know if this one will also support units with a mixed alpha and numeric? IE 2a or 3c?

Bloper_0-1783362896194.jpeg

Steve,

It is unclear which locator style you are referring to when you say "this one". The included quote seems to imply my version but to be clear since there are two different unit-based locator styles circulating on this thread:

- Brad (esri) created a style that includes units, and...
- I created a style that includes units and also has a separate field for fractional portions of an address (my style was tweaked by Brad due to lack of info in the white paper)

Depending on the thread response (and link within), it can get a bit confusing which is which. The telling indicator is the inclusion of the fractional field in the style properties. Brad's will do fractionals but only if the fraction is part of the house number field. Our data is set up with the pieces separated, making the different style necessary.

While I cannot definitively say (since I don't use that version) that Brad's locator style will work with mixed alpha and numeric units, it should have no problem doing so. I CAN definitively say that my version does work with mixed alpha and numeric because our data contains such units (i.e. A-3, B101, 2-C, etc.) and matches them with no issues.

Thanks to everyone on this thread for some explanations and help with customizing locators for units. One problem we are having with this locator is in the candidate match it seeds in a # even though the incoming address did not contain a unit. Is there any way to remove the # in the event of a match without a unit?

The locator returns # characters in the match even if no unit supplied or returned in the candidates.
[ATTACH=CONFIG]30128[/ATTACH]

Thanks for any help in advance. ESRI it is time to fully document the new locator styles and scoring rules it has almost been 3 software versions since they were introduced in 10.0!!!

geocd_matches_#.PNG

Also wanted to add we are having a problem with scoring incoming records with matches against units. If an incoming record does not contain the unit value and the candidate does this should not be a 100% score in my opinion. I believe this was mentioned in some previous posts how do we add a rank to the unit so the score is reduced for the incoming record. It sounds like there were some suggestions but no enough documentation for me to follow or even attempt to modify.

Attached is a screen shot
[ATTACH=CONFIG]30129[/ATTACH]

geocd_match_score.PNG

RobertoFigueroa

Is there any update for an address style using Apt or Units for ArcGIS 10.1?
Thanks
Roberto-