Utah.govOnline ServicesAgency ListBusiness.Utah.gov

Home arrow GIS Resources arrow SGID, Utah GIS Data arrow Data Standards arrow Addressing arrow Carbon Co. Lat/Long Address Proposal
Carbon Co. Lat/Long Address Proposal PDF Print E-mail

Written by Benjamin Clement,

Proposal: Situs Addresses Based on Latitude and Longitude

Benjamin B. Clement, Carbon County GIS
April 30, 2008

 

According to Wikipedia, an address is “a code and abstract concept expressing a location on the earth’s surface.”  Typically, each local governmental jurisdiction will assign a situs or physical address based on some system (usually either a grid or a distance from the origin of each road) which radiates out from a point of origin which is arbitrarily set by said authority. While there have been attempts to unify addressing systems, there have been so many competing systems created over the years that often arguments, pro and con, degrade into bickering about the perception of advantage between the different abstractions. Although this system of addressing has served us for many years, I propose that the unification of situs addressing based on a universal system we recognize as Latitude and Longitude is becoming necessary.

The problem.

Right now there is an ever increasing need to translate a traditional situs address into a physical location. Perhaps the most obvious or well known need is correlating the phone number from an emergency phone call with the location of the emergency as in E-911. Therefore, let's use E-911 as a basis for the discussion and branch out from there.

In the state of Utah, E-911 calls originating from a landline are rerouted to a central switch where the appropriate Public Safety Answering Point is determined. Also from there, the phone number is looked up in a large database and matched to its address if one exits. Emergency Service Numbers (numbers that tell dispatch which police, fire, and ambulance services should respond) are also tied to the phone number and then the phone number with all of the additional information is sent to the responsible dispatch center. Once there, the information is fed to a computer system, the address is stripped off, and a process called geocoding is applied to the address in an attempt to tie the address to a latitude longitude pair so that the computer can map the location of the incident.

While it may not be obvious from the above description, the problem with the process is in the geocoding. Without going too far into the technical details, geocoding is a process whereby each length of road from one intersection to another is added to a GIS database. A range of appropriate house numbers is assigned and an offset assumed. For purposes of illustration, if a section of Main Street from 100 East to 200 East in Anytown, USA were to be selected, a range of house numbers from 100 to 200 would be appropriate to that section. However, only odd house numbers would appear on one side while even numbers would normally be found on the opposing side. Therefore, two ranges of numbers (100 - 198 and 101 - 199) would need to be added to the segment of road; one for the right side and one for the left.  

In practical use then, the GIS system knows the geographical location of the road centerline in question. So determining the latitude longitude pair for a given address along that road centerline involves the following steps:

  1. If the house number of 150 is supplied (for ease of explanation), the length of the road would be divided in half.
  2. Since the house number is even, the even side of the road would be ascertained.
  3. An offset distance from the road centerline would be applied.
  4. The GIS system would return the latitude longitude pair for the point located at the offset distance measured at right angles from the trend of the segment of road centerline at one half its length.

Most of the time, in town, this system works. But the keen-eyed will note that there are a few potential problems. First off, this system will match every number between 100 and 200 even though it is likely that there are at most four or five houses along each side of that particular segment of road. This greatly increases the chances of a false positive match. Next, there is the issue of the offset. In town, it usually works but if you are out in the country offsets could be a great deal longer, and the farther off the main road that a dwelling is, the more likely the entrance road is to meander instead of coming off at right angles. Now add to these issues the difficulties in dealing with mistakes made by the local officials when creating the address like odd-even transpositions, or in the case of offset intersections, 100 block addresses straight across the street from 200 block addresses, or even just skipping a block on a long country road such that you have an 800 block house number where a 900 one should be and the complexity of the geocoded addressing system grow quickly.

Additionally, with the advent of the cell phone, one can no longer make any assumptions about a call's point of origin as can be done with a land line. Geocoding is no longer applicable and so a new system had to be implemented. In this case, it is really two variations on one system. A cell phone either supplies its location directly from GPS, or its location is triangulated from multiple cell towers. In either case, the final location is delivered in terms of latitude and longitude.  

So if we must now deal with two systems and if geocoding is not able to deal with cell phones but latitude and longitude will work for both cell calls as well as landlines, the question that begs to be asked is, "Why not just unify on latitude and longitude?"  I submit that there is no reason not to and that there are many more reasons to switch.
  

The benefits to changing.

The first benefit that I find to using latitude longitude pairs is accuracy. They are unambiguous. That does not mean that using them will be a panacea, but each pair can be found repeatedly and reliably. And once the data entry is found to be correct, it does not have to be revisited.  

You might ask if that last point is not the same for the current geocoded system. To an extent, yes. But the current system is based on many separate addressing systems (eight systems in the case of Carbon County Utah for instance) which do not align with each other. So in the case of a city annexing from the county, all of those addresses within that annexation will have to be changed. Multiplied by the number of cities across the country one can quickly see that the problem is not trivial. Conversely, due to its universality, latitude longitude pairs would need no update regardless of changing boundaries.

Further, if the underpinnings of addresses themselves are based in a system that is intrinsically understood by the computer, no more interpretation. This would mean that location based services could be utilized directly.  

Imagine with me for a moment that you are a UPS delivery driver. Imagine also that this is your first day on the job in an unfamiliar area. Normally these facts could be a recipe for a long day. But if everyone's address were based on latitude and longitude, and if that address were embedded on a barcode or RFID tag, as the truck was loaded, the onboard computer could be assembling a list of deliveries. Further, if a web service were available to that computer, a route connecting each delivery could be computed such that by the time the driver was strapped in and the truck started, turn by turn instructions could have already been assembled awaiting use. This is but one example of many that could be illustrated and it opens up the possibility of a great many more that have yet to be devised.

Finally, everyone with a GPS would be able to both determine and find an address based on latitude and longitude. This would open the addressing system up to inspection by many people from homeowners to delivery people and utility workers. Mistakes would be very apparent and would be likely to be found and reported quickly.

What would such an address look like?

In trying to decide which format of latitude and longitude to use, I found that there is a possible benefit inherent in using decimal degrees (DD) over decimal minutes (DM) or decimal minutes seconds (DMS). That is that at least in this part of the world, four decimal places will give enough spatial resolution to use for addressing in most cases. This provides for the use of four digits, a directional, four more digits and another directional as an address. This has the benefit of looking very similar to a traditional address. So, for purposes of illustration, the address for the Carbon County Courthouse would be 8087 N 5994 W. But what of the degrees?  Well, if I tell you that the Courthouse is in Price, UT or even in the 84501 zip code, you can quickly find out which degrees to prepend to the address to make it work directly with either GPS or location-based web services. In this case, 39° and 110° respectively.


Why some will be against it.  

The most common complaint about this system that I have heard to date is, "I have had my current address for years and I do not want to change."  Changing an address system is a large undertaking. It will not happen overnight. The main benefits of changing the system will no doubt be realized by the generation growing up. To them, the changes that will confuse those established in the current system will become second nature. However, as that generation is in the minority right now, I believe that multiple systems will have to co-exist for some time into the future.  To ease the transition and to accommodate those who are resistant, a web service could be created to act as a lookup table or cross reference between types of addresses. Although it complicates the transition, I find it to be necessary both to gain acceptance and to effect the smoothest conversion. However, for the sake of clarity, I advocate the exclusive use of latitude longitude pairs for E-911 and for all official documents requiring a situs address (i.e. recorded documents such as deeds, etc).

In summary.

With the advent of location based/aware services, we are faced as a society with an ever broadening mandate to translate addresses into something that computer systems understand natively. The more we translate, the more we subject ourselves to error.  

Moving to a system that the computer understands directly would result in increased accuracy, constancy and simplicity and the ubiquity of navigational technology such as the GPS makes the move possible.

Even if everyone were to adopt latitude and longitude for addresses tomorrow, we would not be done. The system will still need to evolve just to keep up with changes that are on the horizon such as allowing the use of cell phones in flight. We will need to carefully consider how to move to a true three dimensional representation of everyday life, but I feel that using latitude and longitude will allow us the requisite flexibility.  


Users' Comments  
 

Display 5 of 5 comments

1. Wed, 05-21-2008 at 03:16 PM

This is a very functional proposal from a GPS viewpoint. I would worry about the casual bystander looking for an address along a given street, say Aspen Drive that meanders in a SE direction. Every part of the entire addresses would be different with no common "street name."  
I think an easier and more economical approach would be to hire an intern to geocode every address and give them your 2334 n 5667 w coordinate as well as physical address. BOTH of which would be availabe to emergency responders. 
 
Just a thought.....

2. Thu, 05-22-2008 at 12:25 PM

Nathan, 
Thank you for your comments. You bring up a very good point. Diagonal streets and streets that meander or worse, turn back on themselves in some type of loop, have always been the bane of addressing. 
 
Of course, if all roads were laid out on strict right-angled grids, we would have many fewer problems. But that does not reflect reality. Conceding that, the question then becomes, "What do we do with the grid-busters?" 
 
But the above viewpoint is biased towards areas in the West where the majority of towns are laid out on grids. I have spoken with folks from other areas of the country that have expressed having great difficulty with gridded addresses and prefer instead to use a set distance down a road as the measure of address with the road name in common to all the house numbers along its length. It is true that once you are on the correct street that you do not have to worry if it runs diagonal or meanders back on itself or even turns in a big loop. Well, at least you don't have to worry about it until it intersects another road. Or worse yet, intersects a gridded road. 
 
The reality, at least in Utah, is that since there are many developers from many schools of thought, we have to deal with both gridded and distance based systems simultaneously. That usually causes decisions that tend to complicate and obfuscate by "mixing" the two "pure" systems together. For instance, one who prefers the grid system over the road distance system will rightly argue that a road name tells one nothing about its location or its trend. One who prefers the road distance system will rightly point out that you cannot effectively "grid" a road that meanders. So to mitigate the first problem, we might do something like link a number to a named road so that we can have a clue as to where the road fits into the grid. But what number do you use if the road trends diagonally? The beginning? The end? The middle? To mitigate the second problem we might break the road at every turn in an attempt to grid it but then you lose the continuity of a common road name. 
 
What is the solution then? Do you use a road name or a number? Well, someone has to decide so one group steps up and makes a decision to use road names. Great! But now you move down the road a block and suddenly you are in another jurisdiction and they have decided to do things just the opposite. And to make matters worse, it all starts from a different addressing origin. 
 
Well, we can be flexible and do both right? Sure you can, but now pretend for a moment that you are at dispatch and there is a fire. Two neighbors call it in at the same time. One says that they live at 245 N 500 W and the other insists that they are at 230 Evergreen Dr. Do you have one fire or two? The house numbers are close together so you probably have just one, but are you willing to bet someone's life on it? What happens next is, to my way of thinking, telling. If you are the dispatcher, you are going to want to look it up. 
 
As a matter of fact, I am going to argue that in every exception to whichever rule discussed above, the only way to really know the answer is to look it up. If we can agree on that then the pertinent question becomes, "Look it up how or where?" If you look things up on a paper map, the answer is simple. Us map makers can start printing the graticule on all paper maps. If you are relying on some type of electronic personal navigational system, the answer will be similarly simple if it contains an accurate map. 
 
I think that the situation that gives us all pause is what do we do when we do not have either a GPS or a map? To my way of thinking, this is still not any different than it is right now. After a period of acclimation, one will be able to know instinctively that if you are here and the address you want to get to is 0327 further to the north and 5260 further west, you will start to look for a road that gets you in that direction. Is this really an different from what we are currently doing? Will there be places you cannot find without looking at a map or asking directions. Yes. But it is likely that you will not be able to find those places by their current address without looking them up or asking directions for the same reason. They are the exception to whatever rule you are using. However, a more important question needs to be asked. As long as you have a lat long address written down correctly, will there ever be an address that you cannot match and look up? Absolutely not! And that reason alone is the basis for my argument to move to latitude and longitude pairs for official situs addresses. Are there addresses now that do not come up with a correct match in any of the current geocoded databases? I don't suppose that question even needs to be asked. 
 
Now having said all of that, will there be need to use double addresses as you suggest? Reluctantly, I must concede your point. I say reluctantly not because I am disagreeable (all you folks out there who know me please stop laughing . . . you are disturbing your co-workers), but because your suggestion doubles the work load. I am therefore hoping for a real-world compromise whereby those who refuse to move to the new system can log into a web service and assign a "traditional" address to their lat long address, thereby putting the onus of work onto those who see the value in it. That same service would offer up those traditional address pairings to those who wish to look them up, but it is hoped that the incompleteness of those addresses would eventually encourage folks to use the new addresses where all of the address points would be represented. 
 
While I secretly hope that the transfer can be completed more quickly than most folks are predicting, it always takes time for people to adopt new standards. And while new standards are never painless, I believe there to be a large payoff in switching to this one and as you have suggested, double addresses may ease the pain along the way.
Benjamin Clement

3. Tue, 07-01-2008 at 03:11 PM

Ben, I thought I'd post my questions relating to your proposal and your responses as I thought there might be someone out there who would find this interesting. Here is question #1 with your response below. 
 
>>> Bert Granberg asked: 
------------------------------ ----- 
Quote
How will the national datasets, now almost exclusively based on centerline-based data, incorporate this style of address? It's easily translatable to a worldwide system but they'd have to keep track of a lot of variation in local-level systems?
 
 
>>>Ben Clement replied: 
------------------------------ - 
Quote
I would suggest that geocoding be used for the original migration should the decision be made to move to lat long. For say a county, all address list could be collected and run through the engine. Match stats could be used to identify addresses that need further interpretation. Visual confirmation could be done using aerial photography and statistical confirmation could be done with a simple spatial query that looks at the distance between the actual lat long of an address point and the lat long that is found in the attribute table. There is no doubt that such an undertaking would be difficult, but the payoff is in the fact that once it is verified, it is "done." 

4. Tue, 07-01-2008 at 03:13 PM

Ben, I thought I'd post my questions relating to your proposal and your responses as I thought there might be someone out there who would find this interesting. Here is question #2 with your response below. 
 
>>> Bert Granberg asked: 
------------------------------ ----- 
Quote
The four digits for Carbon Co. worked well in Carbon Co (much like UTM zone 12 just happens to be an almost perfect fit for Utah data), but what would you do if your area of interest is split by a whole number degree line of latitude or longitude or by the prime meridian? 
 
 
>>>Ben Clement replied: 
------------------------------ - 
Quote
While I first came up with this idea a few years ago, I have been hesitant to suggest it because it relies heavily on GPS technology that not everyone is willing to embrace. However, after making a few presentations, I realized that edges or seams between degrees are no different than the edges currently experienced by one reaching the edge of an addressing jurisdiction presently. When you get to the edge of town, the addressing grid breaks down and people realize that they have reached a line of demarcation. The main difference is that the degree lines of demarcation would no longer be coincident with municipal boundaries and that grid will continue on the other side in the same manner as currently does on your side. These things make it easier to my way of thinking. 
 
But be that as it may, if we were to sign the degree lines, people would adapt to that system as easily as they do now to the sign that notifies one that they are leaving town. In reality, we can navigate now because of a combination of street signs and maps. The combination of maps and degree signs should prove just as effective once a person acclimates. Two other points are that I think that tenths of a degree should be signed as well and degree by degree tiles are large enough that the pattern does not repeat for quite a distance. There should be little confusion.

5. Tue, 07-01-2008 at 03:19 PM

And one more Bert - Ben exchange on the Lat/Long Proposal... 
 
>>>Bert Granberg wrote: 
--------------------------- 
Quote
Maybe we should just paint the graticule on the ground? Up here in +40- 111 land (SL City) that would mean a huge n/s stripe just west of the slc airport. 
 
In general, i like the idea, the key for me was to see it in the context of the system of crutches (maps, signs, boundaries, addresses, etc) we're currently using. What I was trying to get at in question #1 is that it seems like an all or nothing situation...either everybody makes the conversion at once (at least in parallel to the existing system) or its potentially making the big picture that much more confusing. I know the national grid is doing just that (confusing folks) right now. My other minor concern is that 4 digits might not be enough specificity to give unique addresses to things like apartment or office bldg entrances that are less than 10 meters or so apart...but maybe that's not a big deal either. 
 
 
>>>Ben Clement replied: 
------------------------------ -- 
Quote
I like it! Cheap signage. 
 
I see what you mean about the added complexity. I don't know of a way around it. But based on the acceptance that the idea has enjoyed to date, the time spent with two concurrent systems may be short. I think that once it is pointed out that all the systems we use now are just another layer of useless (in the context of today's navigational technology) complexity, the speed of adoption will simply be increased. As for the national grid, it has no place in addressing in my estimation. I am not even convinced that it has much place in the military with the exception of the fact that it simplifies triangulation computations for munitions. Looking forward, I am not sure that even that reason has much place in the robotic wars of the future. 
 
As for the four digit thing, it is problematic but I think that five digits will really push most people, but you know, I was wrong once before (or was it that I was only mistaken?). In our part of the world, it narrows things down to about 1000 sq. ft. I have thought about either fudging the numbers which is what most folks do now when addressing, or better yet, adding five places to one directional. There should be very few times that five digits would be necessary for both. 

Display 5 of 5 comments

Add your comment

13, May. 2008
Last Updated ( 13, May. 2008 )
 

AGRC Contacts | UGIC Contacts

feed image feed image

Utah GIS Portal © 2008 AGRC

Optimized for