Hi Cory,
The locator I've created is based on the US Address street (the file USAddress.lot), so I think the postal code is not required.
In the properties of the locator, in geocoding options, I tried with "Match with no zones" value set to "No" (default value).
I've published this locator as a geocode service.
I used this service in a web app with the locator widget and the suggestions works fine.
When I'm typipng "rue jean Jaures, wattre", I get the suggestion "Rue Jean Jaures, Wattrelos", when I'm cliking on hit, I get no results found.
When I'm typipng "rue jean Jaures, wattrelos, 5965", I get the suggestion "Rue Jean Jaures, Wattrelos, 59650", when I'm cliking on it, I get a hit and the map zoom to the street.
I tried with "Match with no zones" value set to "Yes".
In this case, I've the same beahavior in the two previous example, but I've one more case:
When I'm typing "Rue jean Jaur", I get the suggesion "Rue Jean Jaures" and when I'm cliking on it, I get a hit and the map zoom to the street.
So I tried the same examples with rest api directly (/rest/services/wattrelos_routes_CreateAddre/GeocodeServer/findAddressCandidates, in the field "singleline"), and I get the same results as with the widget:
- a hit when typing the street name (with "Match with no zones" value set to "Yes")
- no results when typing the street name and city name (with either "Match with no zones" values)
- a hit when typing the street name, city name and postal code (with either "Match with no zones" values)
I find this behavior weird and I've no clue to solve it?
Thanks