I have no explanation (yet), but have you tried the "Show all candidates" option on the Find dialog, and does it also fail to show any "candidate" address locations?
[ATTACH=CONFIG]29061[/ATTACH]
Please, consider that I�??m planning to publish the geocoding service by the ArcGIS server and then to plug it in my web application. The end user is assumed to provide the distance and street name and then the system is expected to zoom to that location.
So for example, if the end user provides �??130 Al Irsal St�?� then the web application is supposed to zoom to that particular location as I have already illustrated.
�?� I search some addresses in the �??Al Irsal Street�?� and it works fine for the �??even�?� numbers and fails to find addresses with �??odd�?� numbers!
What might be the issue here?
...
�?� In return, in case of �??Al Sharafa Street�?� the system could search for both even and odd numbers.
What might be the explanation?
I have created original data that fits the �??US Address �??One Range�?� address locator style that includes compulsorily fields for
From Addr
To Addr
Side of the segment
Street name
1. I couldn�??t figure out which data must be stored in the �??Side of the segment�?� field?
You can achieve what you are looking for if you synthesize single-address ranges for your data. First unsplit the roads based on street name and connectivity (Unsplit Line tool) then calculate start (0) and end (integer value of length in metres) 'address' fields onto the lines and use them as from and to address ranges. Geocodes will land on the lines, not to each side.
Jamal, just on a side note, but why are you using the Line option in the Linear Referencing tab in the dialog visible in the attachement / screenshot in above excerpt from one of your posts? Considering your requirement, that is, just one point location for a given address, you should be using the Point option. Line will return a line element, or zoom to the line as defined by the From and To M values, instead of the point address location (just M).
Jamal, I am beginning to think that the issue with the non-matching might be related to the "Side of the segment" field you referenced in the quote below. You are right it is not well documented what this actually is supposed to do. The one section in the Help describing it, leaves a lot to desire...
However, I noticed you filled in "L" in the field for all records, and that seems to place the addresses next to the line. This is not the way Bruce described it, see the next quote below, where he talks of "Geocodes will land on the lines, not to each side." This may suggest that you need to leave the field "Side of the segment" empty, instead of filling in L.
This is all a lot of speculation though, I hope Bruce can answer your question. It wouldn't hurt though, to try and leave the field "Side of the segment" entirely empty, instead of filled with "L's".
This is very useful Marco. The addresses are located now on the street but not on the sides.
The issue of not finding the addresses of �??odd�?� numbers persist to exist.
It works fine. The linear reference can find the �??130 Friends�?� and �??175 Friends�?� streets
...
For the time being, we are using the Geocortex as web mapping application. I�??m not sure how the linear reference SEARCH can be integrated in the Geocortex such that end users can type �??130 Friends�?� to find the location.
I can't answer why the "odd" numbers aren't found, it is starting to look like some kind of bug. If you really want this answered, it seems about time to contact your local ESRI distributor for an official support call. Unfortunately, Bruce Harold hasn't yet joined us again here, so I don't know if he could give some more feedback from the ESRI side on this issue.
According to this Geocortex blog page from 2012, Linear Referencing is supported as a workflow from version 3.8 onwards. So I guess setting it up is just a matter of some configuration in Geocortex. Since your required workflow is actually more in the direction of Linear Referencing than Geocoding, it is not even a bad alternative.