topic Re: �??US Dual Range Addresses�?� style issue, in Data Management Questions

�??US Dual Range Addresses�?� style issue,

JamalNUMAN — Sun, 06 Apr 2014 16:18:10 GMT

�??US Dual Range Addresses�?� style issue,

I wanted to apply the �??US Dual Range Addresses�?� style but it appears that the searched addresses don�??t match the exact location of the target building.

For example, in the screenshot below, I wanted to search the �??5 peace street, Ramallah�?�. The result doesn�??t match the precise physical location of the building. In other words, how to have the location of the found building just precisely in front of the building. The schema is also shown in the screenshot.

[ATTACH=CONFIG]32846[/ATTACH]

I still need to use the �??Street�?� layer as REFERENCE DATA but I�??m looking for having the precise location of the searched building.

What other options I might still have?

Thank you

Best

Jamal

Re: �??US Dual Range Addresses�?� style issue,

JamalNUMAN — Sun, 06 Apr 2014 17:13:07 GMT

�??US Dual Range Addresses�?� style issue,

I wanted to apply the �??US Dual Range Addresses�?� style but it appears that the searched addresses don�??t match the exact location of the target building.

For example, in the screenshot below, I wanted to search the �??5 peace street, Ramallah�?�. The result doesn�??t match the precise physical location of the building. In other words, how to have the location of the found building just precisely in front of the building. The schema is also shown in the screenshot.

[ATTACH=CONFIG]32846[/ATTACH]

I still need to use the �??Street�?� layer as REFERENCE DATA but I�??m looking for having the precise location of the searched building.

What other options I might still have?

Thank you

Best

Jamal

Cont.

In return, I we apply the �??US Single House Addresses�?� style, we can ending up by finding the exact location of each address. But in this case, we need the data at the level of buildings:

1. This data is expected to be massive and �??bigger�?� than the data of streets (number of features)
2. The level of update is very extensive. Each new constructed building must be added to the building layer.

What I�??m looking for is to keep the reference data to be the street to find a way to have exact location as in the case of �??US Single House Addresses�?� style as shown in the screenshot below:

[ATTACH=CONFIG]32848[/ATTACH]

Is that possible?

Re: �??US Dual Range Addresses�?� style issue,

TimWitt — Mon, 07 Apr 2014 11:34:05 GMT

Jamal,

With a locator based on street ranges, it will never plot exactly on buildings, unless the buildings are right on the street and your ranges are setup perfect.

The closest to perfect you can get is using a composite address locator.

If you use your building layer first and street second. It should first look at your building layer, if an address is found you will get the exact location, if not you will at least get an approximate location by using your street address locator.

Hope this helps!

Tim

Re: �??US Dual Range Addresses�?� style issue,

JamalNUMAN — Mon, 07 Apr 2014 19:31:41 GMT

Jamal,

With a locator based on street ranges, it will never plot exactly on buildings, unless the buildings are right on the street and your ranges are setup perfect.

The closest to perfect you can get is using a composite address locator.

If you use your building layer first and street second. It should first look at your building layer, if an address is found you will get the exact location, if not you will at least get an approximate location by using your street address locator.

Hope this helps!

Tim

Thanks Tim.

I couldn�??t understand the assumption of the �??Dual Range�?� style. How come does it assume that buildings are equally paced on the left\right of a street? Does this model the real life?

For example, if we apply the �??Dual Range�?� in �??Peace Street�?� (as shown in the screenshot below) then the location identified by the �??Dual Range�?� style is not in the actual location of the building.

[ATTACH=CONFIG]32886[/ATTACH]

In my country, it never happens that buildings are equally paced on the left\right of streets. Then which style should I use?

I don�??t need to go for the �??Single House�?� style as it requires digitizing all the houses (at least as points) in a particular area to apply this style.

Two options:
�?� �??Dual Range�?�: doesn�??t locate the precise location of the address due to the fact that the buildings are not equally paced in the real life.

�?� �??Single House�?�: requires a data entry at the level of buildings (at least as points) to be able to locate their addresses. Each new building must be added to the reference data and thus extensive work is a must if the �??Single House�?� is applied

Which style can replace these two considering only their advantages?

Applying the �??composite address locator�?� doesn�??t solve the issue as it will be finally using the two styles �??Dual Range�?� and �??Single House�?� with their exact behavior.

[ATTACH=CONFIG]32887[/ATTACH], [ATTACH=CONFIG]32888[/ATTACH]

Re: �??US Dual Range Addresses�?� style issue,

BradNiemand — Mon, 07 Apr 2014 19:52:46 GMT

Jamal,

The "Dual Ranges" style uses interpolation as an approximation of the position along the street that an address should be. The only style that would be more precise would be the "Single House" style which would require an address point for each house. Is there a reason that the exact location is needed for the geocode? If so, the "Single House" style is your only option and will require a lot of work to add every house to the dataset.

Brad

Re: �??US Dual Range Addresses�?� style issue,

JamalNUMAN — Tue, 08 Apr 2014 05:09:09 GMT

Jamal,

The "Dual Ranges" style uses interpolation as an approximation of the position along the street that an address should be. The only style that would be more precise would be the "Single House" style which would require an address point for each house. Is there a reason that the exact location is needed for the geocode? If so, the "Single House" style is your only option and will require a lot of work to add every house to the dataset.

Brad

Thank you very much Brad for the input.

Sure, end users prefer to see geocoded address in the precise place.

[ATTACH=CONFIG]32897[/ATTACH]

Do you mean that the Google database of addresses, for example, is collected at the level of each building as the found addresses match the precise location of the target?

[ATTACH=CONFIG]32898[/ATTACH]

Re: �??US Dual Range Addresses�?� style issue,

JoeBorgione — Tue, 08 Apr 2014 18:34:15 GMT

Thank you very much Brad for the input.

Sure, end users prefer to see geocoded address in the precise place.

[ATTACH=CONFIG]32897[/ATTACH]

Do you mean that the Google database of addresses, for example, is collected at the level of each building as the found addresses match the precise location of the target?

[ATTACH=CONFIG]32898[/ATTACH]

It boils down to what your use is and what your budget is, and how they balance each other: As has been described, anytime you interpolate an address based on a linear feature, you accuracy is okay, but your precision suffers. That's just the name of the beast. Lets say you have a street that is ranged from 100-198 and 101-199 on the even and odd sides respectively. That locator will interpolate house number 150 right in the middle of the block on the even side; the reality might be that its really on the odd side and at the 199 end of the block.

If block level accuracy is 'good enough' then your are good to go. However, if you need better precision than that (like the actual location of house #150) you'll need different data with which to match. Accuracy might cost you $X, while Precision might cost you $X * 5. However, what is the result of an accurate location versus a precise location? That's something only you can answer.

Re: �??US Dual Range Addresses�?� style issue,

JamalNUMAN — Tue, 08 Apr 2014 19:09:33 GMT

It boils down to what your use is and what your budget is, and how they balance each other: As has been described, anytime you interpolate an address based on a linear feature, you accuracy is okay, but your precision suffers. That's just the name of the beast. Lets say you have a street that is ranged from 100-198 and 101-199 on the even and odd sides respectively. That locator will interpolate house number 150 right in the middle of the block on the even side; the reality might be that its really on the odd side and at the 199 end of the block.

If block level accuracy is 'good enough' then your are good to go. However, if you need better precision than that (like the actual location of house #150) you'll need different data with which to match. Accuracy might cost you $X, while Precision might cost you $X * 5. However, what is the result of an accurate location versus a precise location? That's something only you can answer.

Thank you Joe for the useful answer.

In my case, I wanted to explore if there is a more innovative approach to use the �??Dual Range�?� style but at the same time to find the EXACT location of the geocoded address.

Re: �??US Dual Range Addresses�?� style issue,

JoeBorgione — Tue, 08 Apr 2014 23:58:35 GMT

Thank you Joe for the useful answer.

In my case, I wanted to explore if there is a more innovative approach to use the �??Dual Range�?� style but at the same time to find the EXACT location of the geocoded address.

I've known people to address range their streets to the actual physical addresses. Personally I think that's a complete waste of time and energy. I mean, if you have the actual physical addresses, why not create and use points?

The thing is, using a linear feature is always going to be using a linear feature. It's cheap and easy and there's lots of data out there to use. But it has it's limitations and no matter how hard you try, those limitations will prevail.

I have a colleague who made a great comment in a similar discussion: "What if the Census Bureau /Tiger/DIME files started as points instead of lines? Do you think things would be different today?" Jamal I know you are not in the US but way way way back in the day, Tiger files were all we had to work with. We've come a long way in data quality, but a line is still a line.

Re: �??US Dual Range Addresses�?� style issue,

JamalNUMAN — Wed, 09 Apr 2014 07:53:56 GMT

I've known people to address range their streets to the actual physical addresses. Personally I think that's a complete waste of time and energy. I mean, if you have the actual physical addresses, why not create and use points?

The thing is, using a linear feature is always going to be using a linear feature. It's cheap and easy and there's lots of data out there to use. But it has it's limitations and no matter how hard you try, those limitations will prevail.

I have a colleague who made a great comment in a similar discussion: "What if the Census Bureau /Tiger/DIME files started as points instead of lines? Do you think things would be different today?" Jamal I know you are not in the US but way way way back in the day, Tiger files were all we had to work with. We've come a long way in data quality, but a line is still a line.

Thanks Joe,

Then there is no option but to use �??Single House�?� style if I need to find the exact location of the target building.

Best

Jamal

Re: �??US Dual Range Addresses�?� style issue,

TimWitt — Wed, 09 Apr 2014 11:07:28 GMT

Thats right, this is your only option, since you can place those points directly on structures.

I work in 911 and our mapping system works with about 8 different locators. The first locator we are looking in is the Single House locator, to get the most precise location. If no point is found it defaults to our dual range locator. As long as the ranges are correct, it will at least gets you as close as possible to the real address.

Re: �??US Dual Range Addresses�?� style issue,

JamalNUMAN — Thu, 10 Apr 2014 10:27:41 GMT

Thats right, this is your only option, since you can place those points directly on structures.

I work in 911 and our mapping system works with about 8 different locators. The first locator we are looking in is the Single House locator, to get the most precise location. If no point is found it defaults to our dual range locator. As long as the ranges are correct, it will at least gets you as close as possible to the real address.

Thank you Tim for the valuable input.

It is clear now that we need to create more than one locater (as you did guys) and basically Single House and Dual Range, and next to apply the composite geocoding of the ArcGIS.

Best

Jamal

Re: �??US Dual Range Addresses�?� style issue,

JamalNUMAN — Fri, 18 Apr 2014 18:59:09 GMT

Jamal,

The "Dual Ranges" style uses interpolation as an approximation of the position along the street that an address should be. The only style that would be more precise would be the "Single House" style which would require an address point for each house. Is there a reason that the exact location is needed for the geocode? If so, the "Single House" style is your only option and will require a lot of work to add every house to the dataset.

Brad

Hi Brad,

I couldn�??t precisely figure out how the interpolation works in the �??Dual Range�?� style.

For example, in the screenshot below, the length of the �??peace street�?� is 584 meters. The �??From_Left�?� value is 1
and the �??To_Left�?� is 7.

[ATTACH=CONFIG]33204[/ATTACH]

This means that we have 4 buildings in the Left: 1, 3, 5 and 7. In my understanding, the �??peace street�?� is divided into 4 equal segments and the address of these 4 building is centered at the middle of these segments as shown below:

[ATTACH=CONFIG]33205[/ATTACH]

When the �??Dual Range�?� style is applied, the 4 addresses that are located on the left of peace street are displayed as shown in the screenshot below:

[ATTACH=CONFIG]33206[/ATTACH]

This reveals the first address (1 peace street) and last address (7 peace street) are NOT located at the middle of the first and fourth segments according the �??Dual Range�?� style

What might explain this issue?

Re: �??US Dual Range Addresses�?� style issue,

BradNiemand — Fri, 18 Apr 2014 19:27:22 GMT

Jamal,

What you describe below is incorrect. With the Dual Ranges style the first address in the range is right at the beginning of the street segment and the last address in the range is at the very end of the segment. The points will not be at the very beginning and the very end of the segment because of the property "EndOffset" which will offset the matches on the beginning and end of the street segment by a certain skew factor (3% by default).

Brad

Re: �??US Dual Range Addresses�?� style issue,

JamalNUMAN — Fri, 18 Apr 2014 21:07:42 GMT

Jamal,

What you describe below is incorrect. With the Dual Ranges style the first address in the range is right at the beginning of the street segment and the last address in the range is at the very end of the segment. The points will not be at the very beginning and the very end of the segment because of the property "EndOffset" which will offset the matches on the beginning and end of the street segment by a certain skew factor (3% by default).

Brad

Sorry for the confusion.

What I wanted to say is that I couldn�??t figure out how the interpolation of the Geocoding works.

In case of having From_Left is 1 and To_Left is 7, then does the �??Dual Range�?� style divide the "left" streets into 4 equal segments (1, 3, 5 and 7) and locate the geocoded address at the middle of each segment? If not, what does it do with these 4 equal segments? Where the geocoded addresses are �??plotted�?� in relation to these 4 segments?

Re: �??US Dual Range Addresses�?� style issue,

BradNiemand — Fri, 18 Apr 2014 21:22:05 GMT

Jamal,

Please see the attached image and let me know if you are still confused.

The first segment shows where the points would be if there was no End Offset and the second segment shows where the points would be if there was End Offset of 3%.

Brad

Re: �??US Dual Range Addresses�?� style issue,

JamalNUMAN — Sat, 19 Apr 2014 05:26:11 GMT

Jamal,

Please see the attached image and let me know if you are still confused.

The first segment shows where the points would be if there was no End Offset and the second segment shows where the points would be if there was End Offset of 3%.

Brad

It appears that my idea is not arrived.

What I meant is that the approach used in the Geocoding with the �??dual range�?� style is not logic. What I�??m proposing is that the geocoding �??algorithm�?� should be re-structured to match the reality when addresses are geocoded.

Suggestions

Suppose we have 4 buildings at the Left of the street (1, 3, 5 and 7), then

1. The Left street should be virtually divided into 4 equal segments

[ATTACH=CONFIG]33213[/ATTACH]

2. The address should be located at the midpoint of these 4 segment when geocoded

[ATTACH=CONFIG]33214[/ATTACH]

By logic, the address is better to be �??plotted�?� at the MIDDLE but not at the start or end of each building\parcel\segment.