Latest Contributions by BradNiemand

I forgot to answer one of your questions: We don't have any official documentation on this as of right now but we will definately add it for the next release.  Here are some forum posts that suggest the same thing. http://forums.arcgis.com/threads/92913-slow-geocoding-on-locator-stored-in-sde http://forums.esri.com/thread.asp?c=93&f=1113&t=269905 Brad ... View more

Anthony, You can think of a locator as a database in itself.  It contains data records and indexes that are all within the locator (.lox file).  When storing it in a GDB, the .lox file is stored as a blob in the database with a field in another database table that links to that blob.  So essentially you have a database that is stored in another database.  As you can see, there is really no use for that locator to be in the database because it is already optimized with indexes and therefor it doesn't need to use the benefits of a database, it's own indexes. Now to address your other comments which are valid: a) it will be backed up along with the source data     - This can be useful but is it worth the performance hit? b) one less data store to register with ArcGIS server (including security credentials)     - You are correct but this is a one time thing c) security of the locator data is controlled through the database, rather than separate file level security, so one less thing to manage/debug     - Once again you are correct.  The security can be managed at the database level as opposed to having to manage it at the OS level as well. Let me also state that there is no restriction, at this time, to storing locators in GDBs but we just suggest, for performance reasons, not to do it. Hopefully I have clarified some of your concerns but feel free to respond with any others. Brad ... View more

Anthony, There is really no benefit with storing a locator in a geodatabase because a locator is all inclusive (it is a snapshot of the data). Also, the database overhead with storing it there has no benefits and will also cause a significant performance slowdown. Brad ... View more

Jamal, Please see the attached image and let me know if you are still confused. The first segment shows where the points would be if there was no End Offset and the second segment shows where the points would be if there was End Offset of 3%. Brad ... View more

Jamal, What you describe below is incorrect.  With the Dual Ranges style the first address in the range is right at the beginning of the street segment and the last address in the range is at the very end of the segment.  The points will not be at the very beginning and the very end of the segment because of the property "EndOffset" which will offset the matches on the beginning and end of the street segment by a certain skew factor (3% by default). Brad ... View more

When you geocode a table of addresses, after the operation is complete, a reference to the locator used to do the geocoding is stored as metadata in the geocoded result.  When you right click on the address table in Catalog, "Review/Rematch" should be enabled.  You don't need to have the locator loaded in the locator manager.  The only requirement is that the locator is in the same location that it was when the table was geocoded. Brad ... View more

You are unable to open it from where?  Can you please give some more details? ArcGIS version Repro Steps etc... I would also suggest contacting Support if you are having an issue. Brad ... View more

Jamal, The "Dual Ranges" style uses interpolation as an approximation of the position along the street that an address should be.  The only style that would be more precise would be the "Single House" style which would require an address point for each house.  Is there a reason that the exact location is needed for the geocode?  If so, the "Single House" style is your only option and will require a lot of work to add every house to the dataset. Brad ... View more

What problems are you seeing? Brad ... View more

You can try to use the Standardize addresses tool to split your address data into multiple fields. Brad ... View more

What locator are you using?  Is this something you built with a specific version of ArcGIS or are you using the Online Service? Brad ... View more

Here is a link to the plans available for ArcGIS Online. http://www.arcgis.com/features/plans/pricing.html Brad ... View more

Hi folks, I am having trouble finding the "correct" address locator style to use with the TIGER 2013 addrfeat shapefile for my county in NJ. I am wondering if I'm doing anything "wrong" in terms of saving or storing data. I have the addrfeat shapefile in a GDB, and I have directed Arcmap to save the address locator in the GDB. The problem is the dreaded RED X on the LH side of the screen after I select the addrfeat file as the Primary Table. Is there anything I may be mssing in terms of storing data? I am an old dog (literally) who is finally trying to update my course directions to Arc10, including the use of file GDB for storage (vs conventional folders). Thanks for any help anyone can provide. bill in nj Hover over the RED X and reply with what the error is. Brad ... View more

I'm not understanding the problem, how can I clarify that more, no matches are being returned when I use the new address locator, see the above post. Can you give me an example address you are trying to enter? Brad ... View more