Latest Contributions by BradNiemand

That is correct, it will be fixed in 10.1 as well. Brad ... View more

This should work in 10.0 SP4.  You will need to set the WriteAdditionalOutputFields to "True" though in order to see them though. Brad ... View more

We don't ship any styles other than US styles.  You would need to contact ESRI Canada about getting either the Canada locator style or a Canada locator. You could also create a custom style just the way you did.  There are no longer "Rules" for the locators, you create the "Rules" by defining them in the grammar of the locator style XML. Brad ... View more

The Dual Ranges locator style is the one you want if you have Left from - to and Right from - to address ranges.  You would just map the Zone that is appropriate to your reference data (City, State or Zip) and leave the other fields mapped to <None>. Brad ... View more

It didn't make SP4 but we have a fix for it and it will be in 10.0 SP5. Brad ... View more

What locator style are you using? Brad ... View more

I have reproduced this issue and I have logged it.  We will try to get it in the next 10.0 Service Pack. Brad ... View more

I am not sure what the issue is but I can take a look.  Do you have the ability to share the data?  If so, send it to me at the email below. Brad [email protected] ... View more

This was a locator change.  We now require a "CoordSeparator" between the two coordinates and we allow for the space between the "CoordSeparator" and the second coordinate to be optional (before it was required and that is why it doesn't match with the 10.0.2 locator). Valid inputs (comma below can be replaced with ";" or "|" as well): coord,coord coord , coord coord, coord coord ,coord Locator definition in the XML file is below. If needed, line 10 below can be uncommented to allow for no separator but if that is done, also change the pre_separator to "required" for the "latitudePrefix" element below.  We won't ship any locators this way because we saw some strange address parsing but if it is a necessity, proceed with caution.  If not, I would suggest to require the "CoordSeparator" and edit the 10.0.2 locator to have pre_separator "optional" for the "CoordSeparator" or just use the 10.0.3 locator.       <section desc="Coordinates">         <def name="OptCoordsysID">           <alt>WGS_1984</alt>           <alt/>         </def>         <def name="CoordSeparator">           <alt>,</alt>           <alt>;</alt>           <alt>|</alt>           <!--<alt/>-->         </def>         <def name="Coordinates">           <alt>             <elt ref="longitudePrefix"/>             <elt ref="positiveRealNumber" pre_separator="optional"/>             <elt ref="CoordSeparator" pre_separator="optional"/>             <elt ref="latitudePrefix" pre_separator="optional"/>             <elt ref="positiveRealNumber" pre_separator="optional"/>             <elt ref="OptCoordsysID"/>             <result tag="Coordinates">               <method ref="create_point">                 <init_properties>                   <prop name="CoordinateSystem">WGS_1984</prop>                 </init_properties>                 <parameter>                   <component_value component="_1"/>                 </parameter>                 <parameter>                   <component_value component="_2"/>                 </parameter>                 <parameter>                   <component_value component="_4"/>                 </parameter>                 <parameter>                   <component_value component="_5"/>                 </parameter>                 <parameter>                   <component_value component="_6"/>                 </parameter>               </method>             </result>           </alt>         </def>         <def name="longitudePrefix">           <alt>w</alt>           <alt>e</alt>           <alt>-</alt>           <alt>+</alt>           <alt/>         </def>         <def name="latitudePrefix">           <alt>n</alt>           <alt>s</alt>           <alt>-</alt>           <alt>+</alt>           <alt/>         </def>       </section> Brad ... View more

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

What locators are you trying to add?  Are they the ArcGIS Online locators that come out of the box? Brad ... View more

I will let you know. Guess what .... I just got back into work today and it is available. The ArcGIS 10 SP3 (Desktop, Engine, Server) Geocoding General Maintenance Patch is now live on the ArcGIS Resource Center. http://resources.arcgis.com/content/patches-and-service-packs?fa=viewPatch&PID=66&MetaID=1831 Thanks for your patience. Brad ... View more

You are correct.  This issue only affects 10.0 locators. Brad ... View more

We don't have an exact date yet but we are hoping to get it out no later than the first week of 2012. Brad ... View more