nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"US Streets" Style Locator in 10?

KevinHigh

Hello all,

I used a "US Streets" style locator in 9.3 that is pretty much the "US Address - Dual Ranges" style in 10, except "US Streets" has only 9 mapped fields for the primary table instead of 21 for "US Address - Dual Ranges."

My problem: With the old "US Streets" styles, candidates could be generated by typing in just a street name. A list of address ranges along the street would come up without you typing in an address number. This doesn't work with the "US Address - Dual Ranges" style in 10. The same five fields (attached image) - and only these five - are mapped in both locators, but "US Address - Dual Ranges" seems a lot stricter. Dropping down spelling sensitivity and minimum candidate score doesn't help.

I tried modifying the USAddress.lot file to include a "US Streets" locator, but it fails to create a locator of this custom style.

Does anyone have code for the "US Streets" style that I can drop into USAddress.lot? Or does anyone have any recommendations for getting the "US Address - Dual Ranges" style to yield candidates without an address number being included?

Thanks in advance,
Kevin

Address Locator Properties.jpg

JanSouek_0-1756206175305.png

Finde mehr Beiträge mit dem Tag

Accepted answers

BradNiemand

If you go into the locator loc file, you can change the property "supportsEmptyHouseNumber" to true and this should work.

Brad

All comments

BradNiemand

If you go into the locator loc file, you can change the property "supportsEmptyHouseNumber" to true and this should work.

Brad

KevinHigh

Did not know that property existed. Seems to have done the trick.

Thanks!

BradNiemand

These properties will be exposed through the UI at 10.1 but for the time being, they have to be modified through the loc file.

Brad

JoeBorgione

These properties will be exposed through the UI at 10.1 but for the time being, they have to be modified through the loc file.

Brad

That sounds really cool....

KevinHigh

bwragg-

I ended up reverting back to the standard streets locator setup. supportsEmptyHouseNumber broke the results for specific locations on a street range. So "5 st name" would return the same results as "st name."

What we told users who wanted to find the beginning of a street with just "st name" is to enter in the single street name twice, as if it's intersecting itself (which every segment actually is doing). For example "Encinitas Blvd & Encinitas Blvd" takes you to the beginning of the lowest range for Encinitas Blvd. This is my desired result for "Encinitas Blvd" when using supportsEmptyHouseNumber. Our users (not GIS-savvy) have seemed to grasp this "intersecting itself" concept and we no longer have the need for supportsEmptyHouseNumber.

I hope this helps.
Kevin

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Anmelden
Registrieren

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.