Step 1.
POI layer used for those place only have common name, without address.
For example, a cell phone tower, a traffic light pole, a camera, ... these location don't have a address, but have a pole number or camera name, tower number.
This is standard fields.
Step 2.
comman place layer used for those place have both common name and address.
For example, home depot, target, McDonald, staples, they have both common name and valid address.
Here is standard fields
Step 3.
What happen with POI(no adddress) layer?
what happen with common place(valid address) layer?
here is down stream processing with 2 layers.
but why we process it like this?
Because our goal is generate a locator, a locator need 3 role, poi role, address role, street role.
we were preparing these 2 layers, let them fit into poi-role, and address-role.
Step 4.
To create a locator, I need a layer used as POI-role.
POI_Merge layer is the final item I will use as POI-role.
How POI_Merge layer created?
Exactly by merge POI(no address) + common place(valid address)
POI_AN is alternative name table, in this case, I don't use it. It is empty.
POI_Merge = POI(no address) + common place(valid address)
Step 5.
To create a locator, I need a layer used as address-role.
AddressPoint_Merge is the final item I will use as address-role
how it created?
by merge 2 layers.
AddressPoint_Merge = AddressPoint(valid address) + common place(valid address)
_ is alternative name table, I don't use it this time, it is empty.
Step 6.
In real world, so far I had 2 problem, that above standard fields does not cover.
Step 7.
POI and common place are not only within city's limit.
read this, you will find different kind of POI collect by different methods with different time.
how to find night club, inn, motel, hospital, emergency room (911 dispatch)
https://transparentgov.net/cleargov1/1922/how-find-night-club-motel-hospital-emergency-room-dispatch
For example, originally 2025 Aug I collect a set of hospitals in socal.
2026 Nov I collect a new set of hospitals just try to update existing POI+Commonplace layer.
But how?
First step, I need to remove all the old hospitals(2025).
Step 2, add new hospital(2026) to it.
Step 8.
How to remove old hospital?
with standard field, there is no field tells you that this point source is from 2025-hospital.
The solution is obvious by add one more field named "source"
Step 9.
For example, in the new source field, I will say 2025-Aug-hospital
When I want to delete old 2025 hospital, I can select all point that it's source = "2025-Aug-hospital"
Step 10.
Another real world problem 911 dispatch has is
for example, target plaza have 9 other small business inside of it. tesla charging station, CVS phamarcy, starbuck, ... all inside or on target plaza.
Step 11.
when 911 dispatch search for target, by typing 5731,
they hope to see only one item, which is "target",
their idea is simple is best,
simple means not easy to go wrong,
simple means not easy to select the wrong one.
simple means saving their time in split of second.
Step 12.
However, they see 9 of items, 8 of them are useless for them
They have to wast split of second to select the right one from 9 items.
Sometimes, they could select the wrong one.
easy to go wrong, wast time to select.
Step 13.
The problem so far is all POI are equal important in standard fields setup.
There is no field tells me, which POI is 1st class citizen, which POI is 2nd class, 3rd class
Not all POI are equal important,
obviously Target is 1st class citizen,
starbucks inside of target is 2nd class
Tesla super charging station on target plaza is 3rd class.
Another example is
Home depot is 1st class citizen, vendors saling hot dogs in front of home depot door is 3rd class.
Step 14.
standard field does not think about this issue, does not have a class field.
So add class field on both common place + poi layer
Step 15.
each POI point has different importance level.
when create locator,
for 1st class POI should promote
2nd, 3rd class should subside
Step 16.
Step 17.
Step 18.
Step 19.
Step 20.