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; } } }

Standortadresse - Apartment-/Suite-Nummern

RichardLittlefield

<\/HEAD>

Ich erstelle unseren Standortadresse-Punkt FC aus dem LGIM. Mir ist bei den Beispieldaten aufgefallen, dass das Feld Vollständige Adresse die Suite-/Apartmentnummer nicht enthält. Ich folge dieser Regel, aber ich frage mich nur, warum das so ist? Sollte die vollständige Adresse nicht die Apartmentnummer enthalten?<\/P><\/BODY><\/HTML>

Finde mehr Beiträge mit dem Tag

Disaster- Emergency Management

Emergency Communications

Fire-Rescue-EMS

Law Enforcement

Accepted answers

All comments

JoeBorgione

Not sure what LGIM is, however here is my perspective on apartments within the context of public safety:

I have point data for apartments and condos that we use for 9-1-1 dispatch. I'm of the opinion that apartment numbers should be part of the call comments and get transmitted on air to the responding units. In fact, several years ago I meat with the fire chiefs that we dispatch and they all agreed: "Get us to the front gate, and we'll take it from there..."

TimWitt2

Joe,

I think he refers to this Local Government Information Model | ArcGIS for Local Government

Tim

JeffWard

The Attribute Assistant is set up to concatenate all of the elements of the address in the FULLADDR. If you open the DynamicValue table in the AddressDataManagement map, there is an entry for the FULLADDR field that uses an expression to put all of the elements together and then trim any extra spaces.

How are you entering your unit numbers?

RichardLittlefield

I've been building it with Load Objects, so far. My apartment/suite numbers are in the UNITID (Address Unit Number) field. The only reason, I'm not including the suite numbers in the FULLADDR field, is because I saw in the sample data like that.

I'll have to check out the Attribute Assistant and maybe re-calculate the FULLADDR field. Is that possible? It didn't make sense to me to not include the suite numbers, but I was just following the example.

JeffWard

I will track unit/apt numbers if they are addressed in a way that requires it. If all of the units are in one building, I will have one point. If the units are spread out in several buildings, I put one dot per building with the unit number.

You can actually select several points and have the Attribute Assistant fill in the FULLADDR using the run manual rules button. You would have to change the On_Manual field to true in the DynamicValue table for the SiteAddPoint-FULLADDR entry.

RichardLittlefield

I'm curious what format do you use with an address that has a apartment or suite number. Some addresses are apartments while others are suites. Do you use the word or abbreviation for "apartment" or "suite" in the address? So 123 Main St. Apt. 100? In that case then what would you use for suites? 456 1st St. Ste. 200? Or do you use more of a universal format and go with 123 Main St # 100 and 456 1st St. # 200?

JustinWest

Good afternoon,

We are also using the LGIM and I have been working on entering addresses into the database for some of the other features. Whenever I use the FULLADDR field I make sure to treat it exactly like I would be sending mail to that address. It seems to be working for us and I have had no issues when pulling information up by that field. Additionally some of the other features only have a FULLADDR field and not a breakout of the field sections like is in the Site Address Point feature class.

Hope this helps,

Justin West

GIS Analyst

E-911/Emergency Management Department

Dorchester County, SC

RichardLittlefield

That's interesting. So you include City, State, and zip in that field also? I didn't think about it that way. We ended up adding some fields for city state and zip.

Also here is an update. I include the suite/apartment numbers in that full address field now.

JustinWest

I do, the description for the field states "Address information combined into one text field. In your community, this may include the following fields: PREADDRNUM, ADDRNUM, ADDRNUMSUF, FULLNAME, UNITTYPE, UNITID, ALTUNITTYPE, and ALTUNITID." With the Site Address Points it gives the Primary and Alternate address names which would look a bit strange in the field together.

As an example we have Highway 78 which is also known as East 5th North Street (E 5th N St) so if I were entering it all into that field there may be some confusion. We use the common name in the FULLADDR field with the entire postal address just like in the other feature classes. In the Facility Site Point feature it also has the FULLADDR field so we would want these to match so that if there ever needed to be a join by an address we have those to match up as we have several Main St, Broad St, Frontage Rd, etc addresses that are identical without the city information.

ScottOppmann

Justin's note is right on. You can use the UNITTYPE, UNITID, ALTUNITTYPE, and ALTUNITID to track Apt and Suite numbers. If you are using the Address Data Management solution and the Attribute Assistant Add-in, the unit designations will be concatenated in the full address field.

In Justin's example, you could add 5th North St in the FULLADDR and Highway 78 could be added in State Highway designation.

A few years ago, we highlighted these workflows during an ArcGIS for Local Government Meetup on our Address solutions. Here is a link - http://help.arcgis.com/en/localgovernment/meetup/MayMeetup2013.zip

Nimm an der Diskussion teil

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

Schnellzugriffe

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