Latest Contributions by Kazi_IshtiakAhmed

Hi Agatha, Thank you and an email has been sent your way. Cheers Kazi Kazi, The way presenting apartment addresses in a hyphenated number is unusual. I believe the number may have been parsed as a hyphenated house number as designed by the style. If you send me your locator style and a small reference dataset, I can look at it and find a solution for you. My email address is awong@esri.com. Regards, Agatha Wong Esri 380 New York St Redlands, CA 92373 ... View more

No one has any ideas?:( ..All I need is to include something that geocodes the following address format (2009-121 Davisville avenue...here 2009 is the apt number)...the other types are working fine... ... View more

For anyone wondering, in order for the Rematch tool to work, the output feature class and the Geolocator have to be in the same database. Not necessarily..I have all my custom locators in one folder and output feature classes in another. Just to test what you have just said, I just created two databases. One contained a locator I created using a custom style and the other database contained the output feature class. My Review/Rematch was working just fine (using ArcGIS 10.2). As far as I knew, for the Review/Rematch to be active and working properly, you need to make sure that you have the correct locator is selected from the "Select Address Locator" drop down list (click "Manage Address Locator">Add if it isn't there) and the output feature class is highlighted. Hope it was helpful. Cheers Kazi ... View more

Hi Carma, I have advanced quite far since my last post (I thank myself only as I didn't get any help from here). I have finished developing my custom Canadian dual ranges and it works well! To customize it is better to work with a sample. I used the 'USAddress.lot' file that you can find in the 'C:\Program Files (x86)\ArcGIS\Desktop10.0\Locators' and worked my way from there. I would suggest (and this only applies for Canadian or US addresses) you go through the XMl codes. The changes I needed to make and probably you will too are as below: -First, I copied the .lot file in another directory and renamed it. Once all the changes were made, I put it back in the same place where I found it and voila...when you create a address locator, your style will be shown in the default styles... 1. Change the 'Input' section to meet your needs [I had to change state to province, zip to Canadian postal code] 2. Next I changed the 'Grammer' section to include some characters (not many and left the scoring values, 'spell', and cost similar to the others) 3. Build the 'Street name', 'city', and 'province' Aliases [this took most of my time as I had to remove the Spanish stuff from the US style with French ones] 4. CAREFULLY changed the grammer for the 'top level elements' to include province and postal code information 5. CAREFULLY changed the 'Nikel' and 'Dime' mapping schema to make sure that they conform to the previous changes I made 6. Lastly made some changes to the primary table definition so that they match the reference table I have (not really necessary but if you do so, the locator automatically detetcs the mandatory fields) Above are the major changes I made. There are some smaller steps but it too many to list here. I'm sure you'll figure it out. When I started customizing it in January, I knew nothing...absolutely nothing about geocoders. I ran the first successfull locator in March. So you see it is quite time consuming.... Hi Ishtiak, I've come across your post in my search for some insight into custom locator styles and how to customise these from the default. Did you have any luck here? What I am trying to achieve is a single field locator style to use for linear features. Look forward to hearing from you Cheers Carma ... View more