Latest Contributions by BradNiemand

First things first, you are correct, spelling tables only apply to street name.  We will work to apply these to more fields in SP3. Unfortunately, if you would like to do this to house number there are a few changes that will need to be made. First go here: <mapping_schema name="SingleAddress" geom_type="point"> Under this mapping_schema look for <field name="StreetName" grammar_ref="StName"> You will find the following section:             <scoring_method ref="calculate_score">               <init_properties>                 <prop name="CharacterTable">scoring</prop>               </init_properties>               <parameter>                 <input_value />               </parameter>               <parameter>                 <field_value ref="StreetName" />               </parameter>             </scoring_method> This is how you apply spelling to other components of the mapping_schema.  Something like this:           <field name="House" grammar_ref="House">             <desc>House number</desc>             <preferred_name>HN</preferred_name>             <preferred_name>ADDRESS</preferred_name>             <scoring_method ref="calculate_score">               <init_properties>                 <prop name="CharacterTable">scoring</prop>               </init_properties>               <parameter>                 <input_value />               </parameter>               <parameter>                 <field_value ref="House" />               </parameter>             </scoring_method>           </field> As for House Number though, it is indexed for the Single House Style so in addition to the changes above, you will need to change the reference in the reference_data_style section as well. This is the start of that section.  Search for  "Single House (Address Points)":     <ref_data_styles>       <!--Reference data style for Single House (Address Points)-->       <ref_data_style>         <name>Single House</name>         <desc>US Single House Addresses</desc>         <table_roles>           <table_role name="Primary">             <display_name>Primary Table</display_name>             <desc>Address feature class</desc>             <field_roles>               <field_role name="Primary.Shape" is_geometry="true">                 <display_name>Geometry</display_name>                 <preferred_name>Shape</preferred_name> Now you will need to change the mapping schema reference from SingleAddressSearch to SingleAddressPolygonCentroid.         <data_source type="indexed">           <mapping_schema ref="SingleAddressSearch" /> to         <data_source type="indexed">           <mapping_schema ref="SingleAddressPolygonCentroid" /> This should do it but I may have forgot something.  Let me know how it works. Brad ... View more

Do you have any of the Service Packs installed? Brad ... View more

What style are you trying to build a locator with?  Single House, Dual Ranges? Brad ... View more

I would suggest creating a support call about this. Brad ... View more

I will try to clarify some of the resent questions about place name alias table versus alias tables in the style in a couple quick sentences. Alias tables in the style should be used for "common abbreviated forms" of words (ie. first, 1st or MLK, Martin Luther King).  Place name alias tables should be used for mapping between two completely different street names (ie. w 58th ave is also ralston rd). I hope this gives some insight. Brad ... View more

You are correct.  This is your style. Brad ... View more

It should work but I have not tested it in 10.0 SP1 so I am not 100% sure.  If you have an issue though, let me know and I can take a closer look. Brad ... View more

It wasn't that you went astray, it was that the style that you were working with was not handling this yet.  I am not too sure I can clarify without writing a book but in short, it had to do with the way the address was getting parsed at build time.  I fixed that in the last style I posted. Brad ... View more

I have attached a Briano's style with some updates.  The only difference between the style that I posted before and the style that I am attaching now is that it contains an extra field for the fractional house number.  Other than that, I have just included some of the fixes that I found and that will correct the "w vs west" issue. As for the last question, you would need the house number and fractional house number in the same fields for the other style to work. Brad ... View more

This is a known issue and it does have a fix but the fix is not in released software.  It may make it into SP3 or SP4. Brad ... View more

Hello again, I'm still encountering this issue of the address locator / geocoding tool giving high scores (even 100) to addresses matched in the wrong zip code. If possible I would have these matches receive a score of zero as they are incorrect. I am running ArcGIS v10.0 (Build 3200) with SP2. All patches are installed including the "geocoding memory leak" patch. Also, when building an address locator from TeleAtlas street data, the geocoding service will use the zipcode field to some extent, but will still place very high scores (>95) for matches in the wrong postal boundary. I have to run a spatial join on a postal boundary layer and do a select by attributes to find the matches in the correct zip codes, which always eliminates over 95% of the matches. Also, the process seems to place low priority to Suffix and Prefix Type. An address of "12th St" will be matched with "12th Ave" and be given a very high score (>90). Also "N 12th St" will be matched with "S 12th St" with a high score (>90). Basically it seems the only field the address locator places any weight to is the street name and civic number. By the way I am not using composite locators of any kind. Has this issue been resolved? Is there a way to force the address locator to use these fields to validate a match? The geocoding functions worked wonderfully in 9.3.1 which makes this a real shame. *EDIT* I have imported the address locators from 9.3.1 and am experiencing the same issues. I guess I have a few questions and a couple comments. 1. You stated in the first paragraph above that zipcode did Not seem to have any influence in the score.  What locator were you using?  Was it one that you built yourself?  If so, you would need to rebuild the locator in order to get the benefits of the Service Pack improvements that were made to the locator styles. 2. At ArcGIS 10, we changed the way that we handle scoring.  We now use a weighted score to determine the total score of the geocoded address.  If you haven't see the PPT slides from the user conference, I would suggest you take some time to look at them because they go a bit deeper into the way that scoring works at ArcGIS 10(UC 2011 Geocoding Technical Workshop Presentations). This might explain why the weight of the PreDir and StreetType is less than you expect it to be. Possible Solutions: 1. Raise the minimum match score so that the geocodes don't return unless they have a much higher match score. 2. Customize the style to modify the weights to fit your needs.  You can take a look at the following document to get an idea of how you would approach doing this (Customizing ArcGIS 10 locators (An Esri Geocoding Technical Paper)). I hope this helps. Brad ... View more

It should support fractional house numbers.  Let me know if you have any issues with them once your data is ready. Brad ... View more

I am trying to use BrianO's USAddresswithUnit that he posted here. However , it is doing something strange on the West pre directional. If I use W in the search it gets a score of 68 if I use West it gets 100, even though our reference data is using W.  We only have West directional so I can't tell if it is the other directions too. I also created a locator with Brad's SingleHousewithUnits posted here and the W - West works fine as either gets 100% as it should. I am trying to get Brian's to work since we have fractional addresses. The xml looks the same in the Street Directions area for both, but they don't act the same. Any ideas what is wrong?  I am liking the 10 locators, no more alias table to manage. Just need to get the W alias working. Thanks Is the fraction in a separate field?  It looks like there are two reasons that BrianO needed to add fractional types of addresses. 1. It looks like there was a need to support house numbers like 100 A1/2 main st.  Do you also require support for alpha characters in front of the fraction?  If not, the style should handle addresses like 100 1/2 main st. 2. It looks like the reference data that was being used had the fractional house number in a separate field as well which needed to be added to the style OR concatenation to the house number before the locator is built. ... View more

What version of ArcGIS are you using? Brad ... View more

I created a new locator from the style just to double check.  It still returns the same problematic results.  If it makes any difference the locator is created in an SDE 10sp2 db and I'm using Desktop 10sp2. -chris You are correct.  I found another issue.  I have attached an update. ... View more