The City I work for (Roseville, California) is in the process of moving around the ownership of several data layers, so I've been asked to get involved with GIS addressing tasks. I have not done addressing before, so wanted to throw out a beginner question - are there standards commonly used for GIS addressing data? I've been told our data has to meet the needs of not just the folks tracking land development and assets, but also the 911 response community (it will eventually feed into a New World CAD system that is in the works).
I've heard in the past that the National Emergency Numbers Association (NENA) provides one of the major addressing standards:
Is this the predominant standard? Are there others? How does one start getting educated in the GIS side of the addressing standards world?
(I suspect this is the realmJoe Borgione lives in).
Chris Donohue, GISP
Chris- Can't remember where or from who I picked this up, but "The thing about standards is there are so many to choose from"....
Although I probably should, I don't keep tabs on NENA, so I'm not sure if they've finally nailed down a standard or not. They've had one in the works for quite some time for the up coming deployment of of the so-called 'Next-Gen 9-1-1'.
Most of my work is done in Salt Lake County, Utah, USA and they have what I consider a rigorous addressing ordinance. I work in a few other areas, and none of them seem to take addressing seriously; I'm strictly 9-1-1 so for me there is this underlying sense of urgency to have good addressing for dispatch.
Search around a bit in the ESRi pages; they have done considerable work for addressing models. You might also take a look at the Utah Automated Geographic Resource Center they may use the ESRI data model. (You'd think I would know as they are a former employer of mine)
I don't don't know that you can create data that fits the needs precisely of every single end-user. So my advice (and remember with free advice you get what you pay for) is to follow the money; who ever funds the endeavor the most, gets to set the standards for their needs....
Thanks for the insight Joe. My first thought as other groups within the City discussed what they use the address data for was "are we all talking about the same data set?", as there are a wide variety of uses and expectations, and there is no immediate way to meet all of them.
Chris Donohue, GISP
Here are all the NENA documents about the 911 standards for addressing (as well as all the other layers for NG911).
The GIS Data model has been in draft form for a long time and has been released for public comment.
Kansas has adopted a version of the NG911 standard which you can find here:
As for other areas, I am not quite sure what addressing entails.
Just took a look at the Kansas model document Steven provided; A lot of it looks very similar to what I use. The way I see it, the basic structure needs prefix, street name, suffix, type, and range info along with some way to uniquely identify each segment. ( I avoid using OIDs or even GUIDs as unique identifiers; they can mess things up.) Maybe city codes side to side, and maybe zip codes. Anything after that is icing on the cake. As mentioned, I use the data for 9-1-1 dispatch, but I have several different city GIS people maintain the data in a central SDE database that I manage.
Something I really like to take advantage of is database replication. Consider this scenario: while 9-1-1 needs accurate address ranges I'm not really keen on what type pavement or when the last time a particular street was striped. The road guys probably can live some address issues, but pavement and paint is really important to them.
In steps database replication.
I can manage the elemental data that pretty much everyone can use, stated above along with geometry. The roads guys can replicate that data to a feature class that contains what ever additional fields that are important to them. Everybody wins. Minimizing efforts for data maintenance goes a long ways, and at the same time specific needs can be met with a little ingenuity.
The same goes for the traffic guys, the utility guys etc etc etc.
If replication isn't a viable solution, perhaps related tables through the unique identifier could be used...
In addition to NENA, you should look at the relatively new federal address standard at this link: United States Thoroughfare, Landmark, and Postal Address Data Standard — Federal Geographic Data Com... scroll down to where it says Final draft under Project History. This standard will probably be (if it already hasn't been) adopted by most federal agencies for the transfer of address information. Many state and local governments are also looking at it very closely to determine if it affects how they should structure their data. It is a detailed document - not necessarily light reading, but very understandable.
- Rick I.
The best one is the one that fits your region best. Sooner or later everyone will have to conform to some standard. Kansas' model is developed from the NG911 model but has been modified to fit the needs of the counties and cities in Kansas.