Select to view content in your preferred language

Custom Locator Styles: Parity Values (ArcGIS 10)

910
2
06-21-2011 01:04 PM
JacksonGilman1
Occasional Contributor
Hello,

I am building a custom locator style for a project, and one of the mapping schemas is using a single-range matching method.  The trick is that this locator doesn't deal with "street" sides, or to put it another way, parity needs to be ignored.  So I'm wanting all interpolated points to fall on the center of the centerline.  I have two questions:

1. Are the "Side" and "Parity" fields required for the reference data?
2. For PARITY, are there (default) values other than D?  See code paste below (I'm assuming this refers to D_INT for Left/Right intervals per the older 9.x rule base)
<field name="Parity" required="false">
            <desc>Range parity (used primaily for indicating non-trivial parity cases)</desc>
            <preferred_name>PARITY</preferred_name>
            <default_value>D</default_value>
          </field>


Has anyone else tried to do this?

ESRI: Are there any plans to expand on the documentation available for custom address locator style development?

Thanks all!
-Jackson
Tags (2)
0 Kudos
2 Replies
ThibautDelaere1
Regular Contributor
1. The side and parity fields are not required.

2. I also like to know this.

And I have the same question to Esri.
0 Kudos
KimOllivier
Honored Contributor

The SIDE is required.

It would help if there was a sample reference dataset or at least some documentation of the allowable flags for these codes. I doubt if it will appear, so us users will just have to reverse engineer the options and document them here and on Stack Exchange. The SIDE field is REQUIRED in the locator builder, so something has to be populated. They are not intuitive. I had a fruitless search in the help for a list of codes. I then searched the configuration file and can guess that Parity can be L, R, M for perhaps Left, Right, Mixed. So what would SIDE use? Maybe the same but a D(ual) might be an option. Perhaps BLANK is allowed, but never NULLS I suppose that is because someone might be using a shapefile still where nulls are not supported. The default output of a locator is still set to shapefile.

0 Kudos