Author: Eric Gakstatter

  • As Loran Fades, Attention Shifts to DGPS and SBAS

    Few precise-positioning users have employed Loran in a professional sense, although maybe you have in your personal life if you’re a airplane pilot or a mariner. Then again, if you’ve flown as an airline passenger or cruised onboard a ship, you’ve benefited from the back-up to GPS that Loran provides. Similarly, if you’ve used a mobile phone recently; you don’t see it, but the wireless carriers all use Loran as a back-up. That back-up is about to go away.

    Loran was developed initially for marine navigation and then adopted for aviation navigation. I used Loran-C for aviation navigation in the early 90’s after I earned my private pilot’s license. It was much easier than triangulating off of VORs and NDBs. Yes, GPS receivers for aviation were starting to emerge at that time but flying is expensive so a hand-held GPS was an out-of-reach luxury for a newlywed who just bought his first house and was preparing to start a family.

    Loran is a terrestrial (ground-based) system of broadcasting towers, somewhat synonymous with NDGPS. You can read details about the system in the link I provided, but essentially it’s a line-of-sight system in which the Loran receiver antenna needs a direct path to the tower to utilize the signal. Coverage depends on the density of the broadcasting towers. Some regions are covered better than others and when I was using it, there were many areas that were not covered. Accuracy is always an ambiguous subject with respect to navigation technologies, so I’ll go out on a limb and say that Loran-C accuracy is repeatable to about 20 meters. A proposal was floated to upgrade Loran to a system called e-Loran which is reportedly accurate to about 9 meters.

    Anyway, over the past several years there’s been a discussion about what to do with the Loran system because it’s clear that GPS has supplanted Loran as the primary navigation system for marine and aviation. Several articles have been published in GPS World by industry experts with most being in favor of maintaining Loran. The primary argument is that we need a back-up system for GPS, not only for navigation, but for the many invisible ways that GPS supports the national infrastructure (financial networks, wireless communications, transportation).

    Here are several relevant articles, from most recent to further back:

    New Backward-Compatible Technique to Develop GPS+eLORAN User Base

    Coast Guard Jettisons Loran

    LORAN: What the President Meant to Say Was…

    Loran Study Finally Unleashed: Says Keep It, Best Option

    eLoran, Superhero Sidekick

    Loran Gets a Witness

    The Case for eLoran

    In addition to these articles , the U.S. government publishes the Federal Radionavigation Plan (FRP) roughly on a biennial basis. There was one published in 2001, then 2005 and the last one was published in 2008/early 2009. It is the official policy document in which all US navigation systems are planned. According to the FRP, it is prepared jointly by the Department of Defense, Department of Homeland Security, the Department of Transportation and a number of other contributing government agencies.

    If you don’t have time to read the 2008 FRP, following is a telling statement from the document:

    “In March 2007, the DOT Pos/Nav Executive Committee and the DHS Geospatial/PNT Executive Committee accepted the findings of the Institute for Defense Analysis’ Independent Assessment Team and approved to pursue the designation of Enhanced-Loran, commonly referred as eLoran, as a national PNT backup for the U.S. homeland.

    At its March 2007 meeting, the National Space-based PNT ExComm supported this approach and tasked DOT and DHS to complete an action plan that includes identifying an executive agent, developing a transition plan to address funding and operations and requesting the approval by the DOT and DHS Secretaries resulting in a final decision. DoD has not approved eLoran as a GPS backup for military applications.

    In March 2008, the National Space-based PNT ExComm endorsed the DOT/DHS decision to transition the LORAN system to eLoran.

    With respect to transportation to include aviation, commercial maritime, rail, and highway, the DOT has determined that sufficient alternative navigation aids currently exist in the event of a loss of GPS-based services, and therefore Loran currently is not needed as a back-up navigation aid for transportation safety-of-life users. However, many transportation safety-of-life applications depend on commercial communication systems and DOT recognizes the importance of the Loran system as a backup to GPS for critical infrastructure applications requiring precise time and frequency.

    Currently, DHS is determining whether alternative backups or contingency plans exist across the critical infrastructure and key resource sectors identified in the National Infrastructure Protection Plan in the event of a loss of GPS-based services. An initial survey of the Federal critical infrastructure partners indicates wide variance in backup system requirements. Therefore, DHS is working with Federal partners to clarify the operational requirements.”

    By the way, that Independent Assessment Team mentioned in the first paragraph was led by Brad Parkinson, who knows someting about GPS. Further, the government read the report behind closed doors but refused to release it, until forced to do so nearly two years later, by public information access filings.

    There still aren’t any answers to the question about a real back-up to GPS. No doubt it’s a vulnerable system. But that’s a subject for another day.

    What’s Loran got to do with us?

    The reason I’m writing about this is because as support for Loran wanes, attention (resources and focus) shifts away from Loran, it comes to bear more intensely on GPS navigation and its augmentations for marine and aviation; specifically DGPS and SBAS (WAAS/EGNOS/MSAS).

    With a significant policy shift such as this (albeit it has been in the cards), manufacturers stop allocating engineering development resources to the products/technologies with a dim future and shift those resources to products/technologies with a bright future. True, DGPS has been around for better than a decade and SBAS for about half that time so there’s been plenty of time for manufacturer’s to exploit those technologies, but there is still a lot that can be done.

    Engineers are experimenting with and implementing technologies in some interesting areas.

    HA-NDGPS. High accuracy NDGPS. Currently with a high performance DGPS receive
    r, one can attain about meter-level accuracy. Testing with HA-NDGPS, using a dual frequency GPS receiver shows that accuracies in the 10cm (95%) horizontal and 20cm (95%) vertical range are achievable within a 100 mile baseline according to the US DOT Federal Highway Administration Turner-Fairbank Research Center. Test broadcasts are being sent from a site in Hagerstown, MD.

    Broadcasting DGPS/SBAS corrections via NTRIP. The emergence of RTK Networks has spurred the popularity of using the internet to deliver GPS corrections. NTRIP has become a commonly used method of accomplishing this. One of the weak points of DGPS technology has been the reliability and expense of broadcasting DGPS corrections via the 283-325kHz band. Of course, with NTRIP one must have internet access somehow and that typically happens via WiFi or GSM/CDMA mobile phone network. But it’s not that complicated. I’ve been with a GPS user who has pulled the SIM card from their iPhone, plugged it into a GPS receiver, and begin receiving DGPS corrections immediately.

    During my last webinar, someone had posed the question if receiving SBAS corrections is possible via the internet in order to bypass the requirement to maintain visibility of the SBAS geostationary satellite. Streaming SBAS corrections via the internet is already happening in Europe. Users can access EGNOS corrections and bypass the EGNOS geostationary satellites by using SISNeT. A similar type of system could be implemented for any SBAS and not necessarily by the SBAS service provider. It could be a commercial entity.

    I think the internet and GSM/CDMA mobile phone networks are really going to transform the way we transport data from reference stations to our receivers in the field. We’ve been fighting this battle of delivering GPS corrections for better than a decade. In the past, we’ve experimented with FM pagers and landline modems and now we’ve settled on low frequency radiobeacon, VHF/UHF/Spread spectrum and geostationary satellites but none are close to the perfect solution. GSM/CDMA mobile phone networks may be the final solution as the networks continue to build-out towards complete geographic coverage. Of course, we are helped immensely by the mobile phone industry whose focus on data for the many new social networking applications will drive the price of data plans downward.

    By the way, almost all wireless carriers use Loran as a back-up technology; highly precise timing is a key aspect of how wireless communication works. The carriers use GPS for that, but if GPS goes down — as it did in San Diego during a memorable jamming episode a few years ago — so do all cell phones, if the carriers don’t have a timing back-up. In San Diego, they didn’t. Just something to think about, if you are using your mobile phone network to transport data or receive corrections.

  • A Little Q&A Follow-up and Feedback on My Last Column

    I received some feedback on my last column entitled “What’s the Difference Between a Used Car Salesman and a GPS Salesman?” Most of the comments were positive in that the technical content was reasonably deep and thorough. However, I did receive a couple of e-mails from folks who were offended by the comparison.

    The joke has been around for a long time. As I mentioned, I recall hearing it in the early ’90s. I believe it was while I was at a conference somewhere in British Columbia, Canada. Anyway, I used to be a GPS salesman of sorts and I never took offense to it. I figured if I was doing my job correctly, there was nothing to be offended by. But, the fact is the joke has maintained staying power because a number of people do exist who fit that description. Fortunately, they don’t seem to hang around very long in the industry. On the flip side, over the years I’ve met many competent GPS sales professionals that have earned my trust. Many of whom I consider my friends.

    Leftover Webinar Q&A

    There are some lingering questions left over from the last webinar (September). There are still a few questions left after this that I’ll post in future newsletters.

    Question #1: If GLONASS has a full constellation by 2020, would it be fair to say a L1, L2, and GLONASS receiver would be fine because you would really only have a L1 and
    GLONASS receiver thus therefore enough sats?

    Gakstatter: The question is referring to the semicodeless sunset I’ve written about in the past. You can read about it here.

    Back to the question. Generally speaking, I would say yes but it’s going to depend on the receiver firmware design. If the receiver is optimized to depend on L2, then the firmware would have to be altered. Then, the question is whether the manufacturer is willing to update the firmware.

    Question #2: If SBAS is made for aviation safety purposes, why it does not cover all of the world? Will the coverage expand in the future?

    Gakstatter: Building an SBAS is very expensive and time-consuming project. If I recall correctly, the US WAAS total expenditure to date is well into several billion dollars. The FY2010 annual budget for WAAS is just under US$100M.

    The nature of SBAS is that they are regional systems. Currently, there are three. WAAS covers most of North America. EGNOS covers most of Western Europe and North Africa. MSAS covers the region around Japan. GAGAN is still in the planning stage and will cover India and surrounding areas.

    This still leaves South America, Australia, and Africa as major land masses not covered by SBAS.

    MSAS has the potential to cover Australia and EGNOS has the potential to cover Africa. Whether that happens or not is more political and financial than technical issues.

    Also, once GPS L5 is broadcast by a full constellation, the requirement for SBAS for aviation will diminish because GPS in aviation will transition to dual frequency (L1/L5) thus mitigating the effects of the ionosphere.  However, there would still be a question about position integrity, which is a central function of SBAS. The debate within some countries that do not currently have SBAS coverage is whether to invest in a SBAS or hold out for GPS L5. However, a full satellite constellation broadcasting GPS L5 will not be operational until ~15 years from now.

    Question #3: Can we obtain SBAS in other regions in the future?

    Gakstatter: India is far along with their GAGAN SBAS. At one point, a test signal was being broadcast. Within the next few months, India reportedly will be launching a geostationary satellite for GAGAN.

    Russia is reportedly in the early stages of developing their SBAS called SDCM (System of Differential Correction and Monitoring).

    The interoperability among SBAS is virtually seamless. A GPS receiver utilizing WAAS in North America is able to use EGNOS in Europe and MSAS in the Japanese region. Most receivers will automatically tune to the local SBAS given the SBAS satellites in view. However, some must be manually set to “look” for the SBAS satellite(s) of that region.

    Question #4: GNSS improves the productivity. What about the precision? Are there any reports testing/comparing GPS vs GNSS?

    Gakstatter: At this point, the ideal situation would be to only utilize GPS satellites. The quality, integrity and monitoring is world-class. Unfortunately, for RTK users there just aren’t enough of them in orbit to be able to work consistently throughout the day.

    The quality and reliability of GLONASS measurements aren’t as good as GPS yet. The ephemeris data and clock corrections are worse and there isn’t world-wide monitoring of the satellites. Russia’s program managers have stated they are striving to reach the same measurement quality as GPS.

    So, the short answer is no, I wouldn’t expect GPS/GLONASS to improve positioning precision. However, it also depends on the scenario. If the comparison is between a GPS constellation of 5 satellites with a PDOP of 5 against a GPS/GLONASS constellation of 5 + 5 with a PDOP of 2, then I’d vote for the latter.

    There is an extensive report available from The Survey Assocation in the UK. Although it focuses on Network RTK, there’s a valuable discussion in it regarding GLONASS. You can download the report here.

    Question #5: By 2020, is the DOD going to completely get rid of L2 signal?

    Gakstatter: No, not at all. L2 was never intended for use by the civilian community. However, in the 1980’s, some really smart scientists in the commercial sector figured out a way to gain access to the encrypted L2 signal via a technique is referred to as semicodeless.

    Since that time, the Department of Defense (DOD) has respected that technique because it’s been vitally important in the development of the GPS commercial markets. By respected, I mean they have intentionally not made changes to the GPS that would disrupt the semicodeless technique.

    The DOD has now has come to a point that dancing around the semicodeless issue has become a bigger liability than they want to assume. That’s understandable since L2C will allow dual frequency GPS receivers to utilize L2 without using semicodeless techniques, the DOD wants to be released of their liability with respect to L2 semicodeless.

    So, after December 31, 2020, the DOD will no longer guarantee that semicodeless receivers will operate as they do today. It is not a “brick wall” in that it will stop working at midnight on December 31, 2020. In fact, a semicodeless receiver may work perfectly fine most of the time after December 31, 2020, but if it stops working properly, the user assumes the liability.

    Off-topic

    One of the reasons my column is late this week is that I caught a bug earlier this week. It’s nothing serious; it’s just slowing me down a bit because I don’t have the energy I normally have. The fact is that I just don’t get sick beyond my tendency to attract strep throat once every few years.

    This year, I’ve opted out of the flu shot despite a specific call from my mother putting the heat on me to get one. I’ve never gotten a flu shot and probably never will. But, I do admit this is the first year I’ve actually considered it. At one point a few weeks ago, 25% of the primary and middle school-aged kids in our school district
    were absent due to illness. There were significantly fewer Trick-or-Treaters in our neighborhood this year; I believe due to illness.

    I’ve always made an effort to wash my hands, face, nose regularly (no, I’m not obsessive-compulsive) and pay attention to those around me when I’m in public places like malls, movie theaters and airplanes. I absolutely hate getting stuck sitting next to a person on an airplane who is coughing and sneezing. I remember specifically sitting next to a person on a flight back from Phoenix, Arizona, a half-dozen years ago. She looked like death warmed-over…coughing and sneezing horribly. Sure enough, the next day I could feel my body losing the battle. I ended up contracting strep. Ugh.

    Anyway, I want to remind you given that many of the US readers are traveling next week for the Thanksgiving holiday to take care of yourselves and your loved ones.  You’ll be traveling amongst those who haven’t escaped “the bug,” but have still decided to travel. Here are some tips from the Center for Disease Control and Prevention to keep you and your loved ones healthy.

  • Future Roles of the RPLS and GISP

    One of the new initiatives at Geospatial Solutions (GSS) that I mentioned a couple of weeks ago is a Surveying Section on the website. This is an area on the GSS website that’s going to be dedicated to surveyors and GISer’s who want to collaborate. By collaborating, I mean sharing ideas, sharing data, resolving conflicts and generally communicating in a positive way.

    From my previous column…

    “A particular area where I want to pay specific attention is what I call the Survey Section. There is no doubt in my mind that land surveying professionals and GIS professionals are going to be close brethren in the geospatial world. The roles of both are evolving and the line of demarcation is not always clear, but the two need each other terribly in order to best serve the public. GIS isn’t always about parcel maps and land surveying isn’t always about coordinates. The Survey Section (or whatever better name I come up with) will be a place for this sort of knowledge exchange and collaboration in a positive way. There is not one person or company that can stop this geospatial train, so what’s left is how best the two professions can work together.”

    In the column title, I refer to RPLS (Registered Professional Land Surveyor) and GISP (Geographic Information System Professional). RPLS is a generic term I use, but actually there are many different titles used depending on which US state or which country you reside in. RPLS roles are defined by each U.S. state statute (or country law) and their role varies widely from state to state and from country to country. For example, their role in California is much more encompassing than in Nevada. Likewise, the RPLS definition from one country to the next can be vastly different. GISP, on the other hand, is a certification of competency. Their role is not defined nor regulated by individual states or countries (that I’m aware of).

    RPLS and GISP are formal titles for the licensed (RPLS) and certified (GISP) people in their respective professions. Beyond those who are licensed and certified, there are orders of magnitude more practioners, technicians and specialists who utilize measurement, data collection and data processing technology (hardware and software) in order to complete their tasks at hand. As technology advances and becomes more accessible and more powerful, the growth rate of practioners, technicians and specialists is going to far exceed the growth rate of RPLS and GISP personnel.

    How can I make that statement?

    The fact is that data collection (hardware/software) and analysis (software) technology is becoming cheaper and easier to use every year. The established guard might think of it as “dumbing down” the profession, but I don’t think it is. Think back 60 years ago when data entry was accomplished via punch cards. Today, it is widely accepted and expected that everyone uses a keyboard to enter data…and they are responsible for their data entry errors.

    The result of advancing technology and a tightening economy is that there are many more organizations purchasing the technology and performing certain tasks themselves. So, not only are the roles between the RPLS and GISP getting fuzzier, but also the line of demarcation between the client and the RPLS/GISP.

    One example is wetland delineation mapping. In the past, it was common for a wetland scientist to flag the boundary of a wetland and then hire a third party to measure the locations of the flags and create the wetland delineation map. However, it is becoming common for the wetland scientist to carry a GPS mapping receiver with them and map the flags as they are set. This saves the client time by not having to wait for someone else to return to the site and map it. It also saves money by being able to keep the activity in-house. The risk of bringing the activity in-house is having potentially lower quality data if the wetland scientist isn’t well-versed in how to utilize the GPS mapping technology.

    One can argue that the line of demarcation is easy to draw…just refer to the local statute. Maybe, but I can see two problems with that:

    1. Advancing technology and expertise have allowed RPLS to extend their scope of services in their businesses. For example, an RPLS firm offers mapping services that aren’t inside the bounds of the local statute (eg. wetland surveys). GPS and GIS technology advancements have stimulated this growth.
    2. In the areas of expertise that fall outside of the local statutes, there ends up being a “turf battle.” In the wetland mapping example above, the wetland scientist may not be an in-house employee. He/she may be a contractor to the client just like the RPLS firm. In essence, they are competitors. As technology tools become more accessible, powerful and friendlier, this type of “turf war” is inevitable.

    Does this mean the RPLS firm is destined to only be competitive within the confines of the local statutes (eg. boundary surveys, etc.)?

    I think it depends on the RPLS firm. The answer is “probably” if the RPLS firm is not willing to update its technology toolbox and technology expertise. That would be a shame, though.

    From an expertise perspective, the GISP need the RPLS, badly…but that can only work if the RPLS can speak and operate in terms that make sense to the GISP. The fact is that it’s a bigger step for a GISP to learn RPLS-speak than it is for an RPLS to learn GISP-speak. The GISP speaks coordinates and metadata. To an RPLS, a boundary survey does not a coordinate make.

    From a “turf war” perspective, it’s more difficult. When egos and money are involved, people predictably become sensitive and defensive. GISP are a threat to the way RPLS firms have been doing business for decades. There have been two typical attitudes by the RPLS firm in response to this threat:

    1. Disengage and view the GISP as an adversary rather than a complementary colleague
    2. Expand its “turf” by effecting change in the local statutes to increase the scope in which the RPLS firm operates, thus excluding/restricting the GISP from practicing in certain areas (e.g., GIS mapping).

    The former isn’t going to accomplish much. Change is inevitable and firms must adapt to change in order to survive. Sticking one’s head in the sand isn’t going to make the problem go away.

    The latter is a short-term solution. One can “hide behind a stamp” for only so long. Maybe that’s a rough way to state it, but it’s a proven fact that competition promotes excellence. One only has to look as far as the automobile industry to understand this. Had not Japan entered the automobile industry, the quality of automobiles would not be near what they are today. Yes, it has shaken the core of the US economy, but it was something that was needed. It was a “wake-up call” of sorts.

    This column was not meant to provide answers or even attempt to paint the entire picture. It’s an opening statement on what will be a core part of the Geospatial Solution’s coverage in the future.

    See you next week.

  • Where Are We Going?

    It occurred to me that I haven’t discussed my plans for GeoSpatial Solutions (GSS) since I assumed the editorship of GSS a couple of months ago. Some of you have told me that you thought GSS had “gone away.” True, it was somewhat dormant for awhile, but we’ve got some fantastic initiatives underway for 2010 that will renew your interest in GSS.

    First of all, GeoSpatial Weekly will have an opinion column (mine or a guest whom I coordinate) every issue. I’ll strive to provide something interesting to read that’s relevant every week. Sometimes there is big news to cover and sometimes there’s not, but I’ll always strive to make it interesting. We’ll also continue to produce the monthly GeoIntelligence Insider Newsletter which is focused on news and analysis of spatial technologies in the homeland security and defense segment.

    As some of you may know, I am the founding editor (and continue to be) of GPS World magazine’s Survey Scene newsletter that began more than three years ago. Target marketed e-mail newsletters were a new concept for GPS World at that time, and over the past several years we’ve proven it’s the right formula for delivering valuable information to your e-mail inbox in a timely manner. Furthermore, our highly successful webinar series has drawn a tremendous amount of response from our readers.

    Fortunately, GeoSpatial Solutions is a sister publication of GPS World magazine. Both are owned by Questex Media, which operates a fair number of print and digital magazines in addition to other products and services. They have a very capable IT department which can administer a number of powerful technologies like webinars and video hosting.

    This gives GSS a firm leg in which to leverage from.

    Some initiatives I’m working on now:

    Website, 98.27.162.175/gpsworld.com:

    Currently, you may have noticed that we are piggy-backed on the GPS World website as a temporary home. Over the next couple of months, we will be redesigning the website with its own “look and feel.” We will be adding a number of sections that will make resources available to you such as archived webinars (GIS-oriented), videos, white papers and others.

    A particular area where I want to pay specific attention is what I call the Survey Section. There is no doubt in my mind that land surveying professionals and GIS professionals are going to be close brethren in the geospatial world. The roles of both are evolving and the line of demarcation is not always clear, but the two need each other terribly in order to best serve the public. GIS isn’t always about parcel maps and land surveying isn’t always about coordinates. The Survey Section (or whatever better name I come up with) will be a place for this sort of knowledge exchange and collaboration in a positive way. There is not one person or company that can stop this geospatial train, so what’s left is how best the two professions can work together.

    Webinars:

    As I mentioned above, webinars are a powerful communication tool. Also consider that travel budgets and industry conference budgets have been chopped considerably in the “new economy,” webinars are a natural fit. Last year during the weeks before the ESRI User Conference, I dedicated a GPS World webinar to GIS. I plan to do the same this before prior to the ESRI UC in July as well as the INTERGEO conference in Europe in October. These are the two largest geospatial events.

    Guest/Industry perspectives:

    I tell my wife I’d hate to be married to me. Thank goodness for our family that she doesn’t always listen to me :-)

    I think it’s invaluable to hear perspectives from industry folks, even if they don’t agree with me. I’ve started reaching out to those whom I think would bring an interesting perspective to GeoSpatial Solutions. Starting in 2010, I’d like to have at least one per month on varying topics from GIS database technology to trend analysis to data collection methods to new computer hardware developments that effect geospatial professionals.

    Multimedia content:

    The next best thing to being there is viewing a video of an event, an interview, a process, or experience of some sort.

    Youtube, Google Earth and the internet in general have transformed the way we interact in our world and specifically our geospatial world. Those technologies have brought us closer. During my last webinar, I had questions from several people who lived on different continents…Asia, Australia, Europe and Africa. I was interacting with other geospatial professionals who lived in completely different cultures, spoke different languages and lived in significantly different time zones. I cannot begin to imagine kind the room he or she sat in while attending the webinar anymore than he or she could picture what my little office space looked like, but our common geospatial connection brought us together.

    Multimedia content is a tremendously important technology that allows us to grow closer in the geospatial community even though our geographic coordinates are significantly different.

    Industry Conference Live Coverage:

    Attending major industry conferences is important to me because that’s where a lot of industry buzz is taking place and where I get a chance to meet up with a lot of people with whom I don’t see on a regular basis. I also tend to present at these conferences too. The next one is the ACSM/GITA conference next Spring in which I’m leading a half-day GPS workshop along with Pamela Fromhertz of the National Geodetic Survey.

    Live coverage of conferences is a great way of bringing you closer to the conference buzz from your desktop at work or home especially when combined with blogging (such as what we’ve done at GPS World) and video coverage.

    KSA (keyword search) Service:

    Soon, we will give you the ability to sign up for KSA free of charge. Essentially, you select from a list of keywords (such as web-mapping, WAAS, GeoPDF). Once signed up, we will automatically send you an e-mail every time new content (news stories, columns, webinars, etc.) is published that include your keywords.

    Blog/Twitter/Discussion Forum:

    There is a notion of utilizing too much technology. I want to be careful of that. Blog’s make sense if they are relevant and insightful. Twitter is the fast-food of the blog world.

    Discussion forums can be very useful, but they are only powerful if there is participation from a lot of users. That can only happen if there is a foundation of relevant and useful content.

    I can’t tell you if we will use these technologies, but I can tell you that if we do, we will do it right. I respect your time and attention enough to not want to waste it.

     

    Thanks, and see you next week.

  • What’s the Difference between a Used Car Salesman and a GPS Salesman?

    Years ago, I heard a funny joke/maxim. I repeat it often and so do several others I know of so maybe you’ve heard it.

    “What’s the difference between a used car salesman and a GPS salesman?”

    Answer: The used car salesman knows when he’s lying to you.

    I didn’t attend the Minnesota GIS/LIS Annual Conference last week, but I received a report from someone who attended a session in which the presenter seemed to fit the maxim quite well. One of the presenter’s messages was that people should stop using WAAS immediately as a GPS correction source due to the inability of data collection software to handle the ITRF00 > NAD83/CORS96 datum shift. Following is a statement from one of his slides…

    “WAAS Real-time accuracy degraded because of datum shift”

    He claimed that users are “in a panic over it.” In all fairness, the presenter could have very well understood that the datum shift can be handled by a number of data collection software packages…just not the one he represents. After all, he works for a local distributor of GPS equipment. Or, even a scarier scenario would be that he really believed what he spoke.

    I’m not interested in naming names or company names of the offending party, but rather painting the true picture. Of course, the attendee I mentioned above knew better than to believe what the presenter was pitching. His group has been using WAAS as a primary correction source for a number of years and reconciling the datum shift between ITRF00 and NAD83/CORS96. It’s not that hard folks.

    Let’s review.

    ITRF00 is essentially the same as WGS-84(G1150) for sub-meter mapping purposes. WAAS (as well as EGNOS and MSAS) are referenced to ITRF00. You need to be aware that the definition of ITRF/WGS-84 has changed over time. Here is a link to a NIMA WGS-84 document that describes earlier versions of WGS-84 and here’s a link to the current version of WGS84 (G1150) that was adopted in 2002.

    In North America (my apologies to readers from other countries), the generally accepted mapping datum is NAD83. NAD83 has also changed substantially over time. Whereas the original WGS-84 was consistent with the original NAD83 (NAD83/86), today there is a substantial difference between the current WGS-84(G1150) and NAD83/CORS96 and also NAD83/NSRS2007. Here is a graphic from Joel Cusick of the U.S. National Park Service that gives you an idea of the difference over North America:

    Here is a link to a technical report from the National Geodetic Survey (NGS) describing the 14-parameter transformation from ITRF00/WGS-84(G1150) to NAD83/CORS96.

    Sadly and surprisingly, some data collection software today and even some PC-based “GIS” software still treat WGS-84 and NAD83 as the same. This instantly introduces a few feet of error. The irony is that people spend thousands of dollars purchasing high-performance GPS/GIS receivers capable of sub-meter accuracy only to introduce several feet of error by using software that improperly handles the datum transformation.

    What’s the solution if your software doesn’t handle the datum transformation properly?

    As mentioned above, WAAS is based on the ITRF00 datum and not NAD83/CORS96. As most base maps in North America aren’t referenced to ITRF, most likely you’ll need to transform your WAAS-corrected coordinates to NAD83/CORS96. This can be done one of two ways:

    1. As mentioned above, use GPS/GIS data collection software that handles the transformation correctly. This makes the transformation transparent, painless to the user and accurate in real-time.
    2. Apply a datum shift after you’ve collected your data. You can compute the shift by accessing an NGS datasheet near your project area (within 25 miles is close enough). Make sure it was occupied using GPS. Better yet, use coordinates from a CORS. The datasheet will report coordinates in both ITRF00 and NAD83/CORS96. Here is an example of coordinates from the CORS at Wisconsin Point, WI (near Duluth where the MN GIS/LIS Annual Conference was held):

    ITRF00 Position (Epoch 1997.0) – N 46 42 18.20201, W 092 00 54.760208

    NAD83/CORS96 Position (Epoch 2002.0) – N 46 42 18.17201, W 092 00 54.73394

    Simply enter the two coordinates into your favorite mapping software and you’ll be able to compute the distance and direction of the difference.

     

    Once you know this, you can apply the same offset to all of the data for your project. Quick and dirty? Yes. We’re not splitting hairs. WAAS isn’t delivering cm-level accuracy so this sort of transformation is more than adequate…and very efficient.

    The fact of the matter is that many, many organizations have adopted WAAS as a primary source of GPS corrections and are dealing with this datum transformation issue on a daily basis.

    GPS Constellation Management: Playing Not to Lose

    The WAAS/SBAS subject segues perfectly into the second subject of this column which is a follow-up of last week’s column on GPS Constellation Management.

    Last week, I failed to mention that SBAS (WAAS, EGNOS, MSAS) is a valuable contributor to RTK users. Although not designed specifically to aid RTK ground users, some GPS receiver designers have exploited the value of SBAS satellites to enhance RTK operations. In North America, there are two SBAS satellites. In Europe, there are two and there are two in the Japan region. Following is a graphic depicting the regional coverage of the SBAS satellites and their approximate location.

     

    In many regions of the world, users have at least one SBAS satellite available in view. The beauty of SBAS satellites for RTK is that, unlike GPS satellites, SBAS satellites are geostationary. The are available 24/7 as long as their signal path isn’t blocked by trees, terrain or buildings.

    Since using SBAS satellites for RTK is a relatively new innovation within the past couple of years, not all manufacturers have jumped on the bandwagon yet. The slow adoption of GLONASS was similar. This causes a problem when users want to mix and match RTK receivers from different manufacturers. For example, a user purchases an SBAS-capable L1/L2 RTK rover to be used with their existing L1/L2 RTK reference station. If their existing L1/L2 RTK reference station doesn’t support SBAS for RTK, then the feature on their new RTK rover is worthless.

    Even more important is the lack of support from RTN software designers. “No one’s asking for it” is the answer I get from RTN operators when asked if they are interested in supporting SBAS correctors in their RTN. I believe that users aren’t asking for it because users don’t have a clue how it would help them, and frankly, 99% don’t know the technology even exists. Now, if you would ask users if they’d be interested in one or two extra observables for RTK that would be
    available 24/7 in a geostationary orbit every day, I bet you’d hear some really positive answers.

    RTK users need to be able to utilize every observable that could help them. As Rob Lorimer and I reported last year in our market research report, machine control (based on RTK) will be the fastest growing GNSS segment over the period 2008-2012.

  • 3D Geospatial Data

    The usage of three dimensional data in the geospatial industry is in its infancy. It makes sense to me. Sometimes, it’s hard enough for folks to obtain and maintain accurate two dimensional data, not to mention elevation! However, as geospatial technology continues to evolve, the availability of 3D geospatial data will evolve. I’m pretty sure that in ten years we will look back and be amazed at how little we used 3D geospatial data.

    But for now, what the heck are Mean Sea Level, ellipsoidal height, orthometric height, geoid height?

    Sources of accurate elevation data are difficult to find. Typically, you’re going to find elevation data from aerial photogrammetry projects, LiDAR missions or from GPS data collection projects. Since availability of this sort of data on the world-wide web isn’t as prevalent as 2D geospatial data, 3D geospatial data utilization isn’t main stream yet.

    There’s also the issue of the definition of elevation. Yes, just like there are differential horizontal datums, there are a variety of elevation datums. On legacy paper maps, elevations are typically displayed with respect to Mean Sea Level (MSL). MSL is an the elevation reference for local areas, but the Earth is not like a bathtub where gravity has an equal impact on the water in the bathtub that forms a smooth surface. MSL around the world varies tremendously. 2 meters MSL in New York is orders of magnitude different than 2 meters MSL in Hong Kong.

    MSL is a complicated subject in itself. Check out this web page on the National Geodetic Survey’s web site that provides definitions related to MSL. The Earth is not a perfect sphere and gravity influences vary by region. For centuries until recently, elevations were stated with respect to sea level because that was the most reliable and widely known reference.

    GPS has changed that. GPS uses an elevation model called the geoid which was intended to somewhat approximates MSL. There are a couple of good references that provide much more detail. They are worth reading. One is from ESRI written back in 2003 by Witold Fraczek. The other is from an NGS presentation given in 2007 by Daniel Roman.

    In fact, following are a couple of graphics from the NGS as well as one from Dr. Roman’s presentation that draws a clear picture of how GPS heights are related to MSL.

    H = Orthometric height (Mean Sea Level), h = Ellipsoidal height, N = Geoid height

    Note that the height determined by GPS is the ellipsoidal height, not Mean Sea level. The difference between the two can be tens of meters.

    Most GPS receivers have a rough model of the Geoid height built into it. However, it’s very rough and can be a few meters in error. To resolve this, significant efforts have been made in the two decades to create high resolution geoid models. Creating a high resolution geoid model (for a country) is a relatively large effort that requires very skilled people and specific equipment.

    Following is a similar graphic illustrating North American Datum of 1983 and GEOID03, which was the most recent geoid model of the United States (GEOID09 was just released).

     

    Finally, following is a graphic from Dr. Fraczek that depicts the relationship between the ellipsoid, MSL and the Earth’s surface. You can see here that at some points, the ellipsoid is actually above the geoid and at some points, it’s below the geoid.

     

     

    The purpose of this column is to point out that when you receive 3D geospatial data, you should inquire what about the elevation data is referenced to. Are they ellipsoidal elevations? Are they MSL elevations? If MSL, what was the resolution of the geoid model used?

    Flushing out horizontal datum inconsistencies in your GIS is, for the most part, pretty straight-forward. The 2D view is the norm and once you bring data into your GIS, you can compare the imported features to the existing features and identify fairly quickly if there’s a problem with the 2D data. The problem is that most GIS folks aren’t used to working in a 3D world. I speculate that most people figure that if the 2D data is reasonable, then the elevation (if it exists in the database at all) must be accurate. It would be interesting to hear from folks who are making a concerted effort in quality checking the heights used in their GIS.

    Even though GIS horizontal data is still far from perfect with respect to accuracy, at least I can see the road to success. The quality of horizontal data in the past ten years has improved significantly thanks to widespread availability of data collected via remote sensing and GPS data. I think that trend will continue as the widespread availability of accurate horizontal data continues to improve. The roadmap for 3D data isn’t so clear. Not only is there a lack of accurate 3D data, but also the models (eg. geoid model) for generating accurate 3D data continue to evolve.

    Applications for 3D data are expanding and are going to continue to expand. People, both inside the geospatial industry as well as the general public, still have a hard time visualizing 3D data. For example, a land development plan for a site can be communicated much more effectively if there’s a 3D visualization (either still image or animated video) that accompanies the engineering drawings. Following is a visualization of a particular golf course hole where the architect was trying to convey the design change to the golf course owner. The image on the top is the existing golf course. The image on the bottom is the proposed design. The data used to create the terrain model in these images was high quality 3D geospatial data.

     

    Thanks and see you next week.

  • TIGER Database Historical Perspective

    In my last two columns, I’ve made several references to geospatial data. Jon Sperling, Ph.D. GISP, wrote in and commented on the omission of the importance of TIGER data in the history of geospatial data development and commercialization. He made reference to a document he wrote that was published in 1995 regarding the development and maintenance of the TIGER database. I’ve decided to reprint his work, with his permission, as this week’s column. It gives keen insight into the early stages of TIGER. Albeit quite in-depth, it’s a fascinating read for gaining a historical perspective on geospatial data development.

    Keep in mind that this document was written in 1992 so there are references to initiatives, etc. that were subsequently developed and that you enjoy today.

    Sperling argues that our public investment in TIGER need not be just history but a pro-active means to leverage partnerships and new advances and innovations (e.g. synergistic links with national parcel data initiatives, local/state/federal data sharing and a national road network). Census still remains a pioneer in supporting and furthering geospatial science at all levels of our society for the betterment of our Nation’s communities.

    Dr. Sperling is currently a Senior Researcher of Geographic Information and Analysis at the Office of Policy, Development and Research for the U.S. Department of Housing and Urban Development. He has designed and led many innovative geospatial, addressing, and data integration efforts in coordination with local and state governments and the academic research community. Dr. Sperling was involved in the initial development of the Nation’s TIGER/Master Address File databases for the 1990 and 2000 Census, enabling digital spatial data sharing capabilities, and efforts to enhance its coordinate accuracy and data quality. Currently, he is working with university partners on a number of innovative research applications to enable sophisticated querying of unstructured text and tables using textual spatial references in the data.


    Jonathan Sperling, “Development and Maintenance of the TIGER Database: Experiences in Spatial Data Sharing at the U.S. Bureau of the Census,” in Harlan J. Onsrud and Gerard Rushton, eds., SHARING GEOGRAPHIC INFORMATION (New Brunswick, NJ: Center for Urban Policy Research). Copyright 1995 by Rutgers, The State University of New Jersey. Reprinted with permission.

     

    Development and Maintenance of the TIGER Database: Experiences in Spatial Data Sharing at the U.S. Bureau of the Census (1992)

    The U.S. Census Bureau has played, and will continue to play, a vital role in the development, maintenance, and sharing of spatial and attribute data for Geographic Information Systems (GISs) on the local, regional, national, and international levels. The Census Bureau’s development of shareable geographic data files, the GBF/DIME (Geographic Base File/Dual Independent Map Encoding) Files for the 1970 and 1980 censuses, and the TIGER (Topologically Integrated Geographic Encoding and Referencing) database for the 1990 census, have provided a major impetus to the rapid growth and diffusion of GIS technology. This chapter discusses the Census Bureau’s experiences in the spatial data sharing during these two file-building projects as well as from ongoing experiences in developing Memoranda of Understanding with federal and state agencies to update and improve the spatial and attribute data in TIGER. On the basis of these experiences, preliminary generalizations are made concerning the organizational issues that may facilitate or impede the future digital interchange of spatial data.

    Introduction

    The entrance and persistence of the nation’s lead statistical agency as a primary producer and user of both geographic and attribute data have grown out of practical but critical concerns (Tomasi 1990). The mandate to conduct a population and housing census of the entire nation and its territories every ten years, and then disseminate the resulting information  quickly and accurately, has led to the need to devise innovative ways of improving the collection, processing, and tabulation of data.  These improvements have aimed at four goals: increasing efficiency and timeliness, improving data quality, lowering costs, and providing new products for the data user.

    Over the past half century, the Census Bureau has pursued innovations and led the government and private sector in computerization, statistical sampling and interviewing techniques, data processing, quality control, and cartographic techniques, to name but a few (Anderson 1989).  The Census Bureau pioneered the first large-scale commercial user of the computer with UNIVAC 1 following the 1950 census and the development of the Film Optical Sensing Device for Input to Computers for the 1960 census.  The broad use of computer mapping by local governments and private firms was strongly influenced by the Census Bureau when it developed the GBF/DIME-Files for the 1970 and 1980 censuses and the TIGER System for the 1990 census.

    In addition to being one of the nation’s largest digital geographic databases — currently sixteen gigabytes — TIGER enables the automated spatial manipulation of census data for all legal and statistical entities in the United States and its territories.  Every state and local government now has the capability to create rudimentary GIS using small-area census data, publicly available extracts of the TIGER database – TIGER/Line  files – and the appropriate hardware and software.  More than 130 private vendors currently have the capability of processing TIGER/Line files, and the number is growing.

    In this respect, the development of the TIGER database may be the most important “data” file from the 1990 Census of Population and Housing.  The accessibility and widespread potential application of this innovation make it qualitatively different from earlier technological developments at the Census Bureau.  The TIGER database will be used not only internally to administer future censuses and surveys (see Marx 1986 for a basic rationale of the TIGER system) but externally to provide a major impetus to the development and sharing of integrated special information systems in the public and private sectors as well as the academic community.

    A common theme in the GIS literature, generated both within and outside the Census Bureau, has been the notion that although the Census Bureau developed its GBF/DIME-Files and TIGER database to meet internal Census Bureau needs, their existence has facilitated applications well beyond the scope of census-taking.  Perhaps analogous to the many commercial spin-offs that have been generated from wartime military innovations or the nation’s space program, the decennial census operation, conducted by the government’s largest non-military assemblage of people and resources, has been responsible for a number of innovations, some already outlined, that have had a major effect on the private sector and the academic research community.

    The Census Bureau’s recognition of these “consumer spin-offs” traditionally has never been well articulated or coordinated because most innovations have resulted from an internal production standpoint rather than a customer-oriented design.  Recent efforts toward building a national spatial data infrastructure and the Census Bureau’s adoption of the principles of Total Quality Management and Strategic Planning create the external and internal incentives, respectively, to stimulate a change in that design.  Paradoxically, however, the fiscal constraints of the 1990s and their impact on congressional funding, while often considered an incentive for data sharing, may also function as an impediment in the early developmental stages of new technologies.

    THE DEVELOPMENT OF SHAREABLE GEOGRAPHIC DATA FILES – GBF/DIME-File Development 1966-1982

    Many local agencies have been introduced to GIS by the Census Bureau through is various geographic base-building projects over the past twenty-five years.  The development of the Address Coding Guides (ACG) for the 1970 census and the GBF/DIME-Files for the final stages of the 1970 census and for large-scale use in the 1980 census were major steps toward full automation of the Census Bureau’s geographic support programs.  Althought the ACGs provided the building blocks for the later development of the GBF/DIME-Files, they lacked geographic coordinates and topological structure (Marx 1986).

    The design and development of these computer-readable files involved the active participation of federal, state, local, private and academic organizations.  The Census Use Study, a small-area data research group sponsored by the Census Bureau from 1966 to 1969, was instrumental in creating and diffusing knowledge about a system that represented map features numerically for processing by a computer to create a geographic base file (U.S. Bureau of the Census 1973).  The enhancement of this body of knowledge was of critical importance to the Census Bureau because it enabled the adoption of census-by-mail enumeration methodologies for the major urban centers of the United States.

    The change in enumeration procedures was a response to the increasing costs and difficulty of conducting a traditional door-to-door canvassing of the population, a growing and increasingly urban population living within areas having mail delivery by house-number/street-name address, and technical feasibility of linking such addresses with the geographic units used for data tabulations due to improvements in computer capabilities.  For the 1980 census, the GBF/DIME-Files were enhanced to cover 287 of the nation’s largest urban centers, representing more than 60 percent of the population but less than 2 percent of the nation’s land area (Carbaugh and Marx 1990).

    Data sharing during the 1970s.  The development of the ACGs and GBF/DIME-Files involved data sharing with more than 300 local planning agencies.  Sharing primarily took the form of converting analog data into a computer-readable format rather than digital exchange per se.  The long-term nature of these relationships provided the Census Bureau with intimate knowledge of the resources available to local agencies, the limitations of available data, and the willingess and ability of agencies to share data.  At the same time, local planning agencies and others, through their association with the Census Bureau, became increasingly aware of the potential computer mapping, automated address matching, and spatial data analysis to meet local needs (Sobel 1978).  These relationships played an important role in the later development of the TIGER system.

    Monetary and other incentives to the local agencies played a major role in the “data sharing” development of the ACGs and GBF/DIME-Files (Silver 1977).  In many cases, local agencies completed work under contract with the Census Bureau or with funding provided by the Department of Housing and Urban Development (HUD), and Federal Highway Administration (FHWA), and other federal, state, and local planning sources.  Sensitive to the fact that the development of the GBF/DIME-Files provided a practical solution to many needs of local governments, the Census Bureau offered to provide the computer programs, processing methodology, and clerical procedures for creating  and updating the file, as well as a free copy of the completed file, to each participating local agency.  The Census Bureau also offered to do the data keying and processing if agency resources were limited.  The promise of higher quality data when these files were used for taking and tabulating the 1970 and 1980 census provided a further incentive for data sharing.

    As a result of this process, the Census Bureau and local officials learned that the quality and currency of existing data used by planning agencies could not be taken for granted.  For example, many local communities relied on the knowledge of a few people for the location of dwellings, address-numbering systems often were not systematic, tax assessor sources sometimes did not meet the bureau’s quality standards, and data from different agencies often were inconsistent.  Because of these situations, the initial transition to address assignment via automated processes was difficult.

    The efforts of working with so many local agencies also challenged the Census Bureau.  During the file-building projects, there was turnover in project personnel and key decision makers in the local agencies as well as at the Census Bureau.  Some “champions” of the new methods were not reelected or moved on to other jobs.  The long-term benefits of building such files were not always apparent to public administrators.  Some administrators viewed the new computer technology as a threat to their role in the agency.  Also, during the 1970s, there was a general lack of understanding (personal computers had not yet been invented) and/or trust in the new computer technology and the ever-present fear of “big brother” mainframe computers held by a few large government agencies.  All these factors tended to hamper development activities and to result in considerable variation in the quality, time expended, and funds necessary to complete the GBF/DIME-Files.

    Data sharing during the 1980s.  Census Bureau funding of data collection and coding by local agencies to create the GBF/DIME-Files created precedents that would later affect the pre-1990 TIGER-building efforts.  The overall reductions in federal aid to cities and states during the 1980s provided an atmosphere of “less than cooperative initial attitudes” among many local agencies struggling with small staffs and fewer resources than they had in the 1970s.  Many agencies expected to be paid for their efforts.  These situations, and the perceived difficulties inherent in working with several hundred local agencies, contributed to the Census Bureau’s decision to do most of the map and address updates for the 1990 census in-house, albeit often based on materials supplied by local agencies.

    Changes in the original GBF/DIME-File format by local agencies exacerbated some early data-sharing efforts.  Many of the larger files that had been maintained by local agencies (e.g., New York City) had been adapted and enhanced to meet local planning and administrative needs.  Fiscal difficulties at the local level, time constraints on the Census Bureau, and the lack of additional programming staff in all agencies often precluded efforts to recreate the original file structure without losing the map and address updates.  In these cases, the feature and address range update work had to be redone manually by the Census Bureau from digital plots and databases.

    One of the general weaknesses of the GBF/DIME-Files was that they were limited geographically and, therefore, the ability to use the files on an ongoing basis was limited to large-scale users with on-line access to mainframe computers.  Relatively few of the original GBF/DIME-Files given to local governments were updated and maintained during the 1980’s. Even fewer of the locally updated files met Census Bureau standards for direct incorporation into the TIGER database. In practice, however, these updated GBF/DIME-Files provided the Census Bureau with its first challenge in the digital spatial data exchange at the local level.

    Digitized GBF/DIME-Files, attribute-rich but of mediocre
    coordinate accuracy, formed the cartographic base for 345 urban centers in the 1990 TIGER database. Absolute coordinate accuracy was not a primary concern in the development of the GBF/DIME-Files, as they were used primarily by the Census Bureau for geocoding rather than mapping purposes. Although their coordinate accuracy was well below that of the U.S. Geological Survey’s (USGS’s) Digital Line Graph (DLG) files derived from their 1:100,000-scale maps, these files represented features with all their respective feature names, address ranges, and 1980 geographic area codes in their correct relative location – sufficiently accurate for taking a census (Sobel 1986).

    Although the Census Bureau would have liked to provide an enhanced cartographic quality, the deadline pressures of an upcoming decennial census forced management to abandon initial plans to align this information to the USGS’s DLG files. Also, because of staff and time constraints, the files were sent to four private-sector contractors for digitizing of feature updates using Census Bureau-supplied updated 1980 census maps. The results from these arrangements were of mixed quality.

    TIGER Database Development, 1983-1990

    The institutional knowledge and experience gained from the development of the GBF/DIME-Files, further theoretical and conceptual advances in the field of mathematics (Corbett 1979 and White 1984), and the “enabling” availability of new and affordable technology, provided fertile ground for the Census Bureau’s next challenge: the development of the TIGER database for use in the 1990 census. Whereas the GBF/DIME-Files covered small noncontiguous portions of the United States and were developed initially without spatial or geographic references in their design, the TIGER database covered the entire nation and its territories and was grounded in a more rigorous conceptual model of topology and space (see Boundriault 1987; Kinnear 1987; Broome and Meixler 1990).

    Census Bureau/USGS cooperative agreement. In addition to data-sharing arrangements on the local level, the ability to complete the building of the TIGER database in time for the 1990 census was directly dependent on a landmark 1983 data-sharing agreement with the USGS. The USGS provided the Census Bureau with computer files of scanned versions of its 1:100,000-scale maps for the lower forty-eight states. In return, the Census Bureau assigned cartographic classification codes to the roads in these files. The resultant product formed the cartographic base for all areas outside the large urban centers covered by the GBF/DIME-Files, thereby enabling the Census Bureau to complete a coast-to-coast digital map base in time for the 1990 census (McKenzie and LaMacchia 1987).

    Interagency cooperation with the USGS was an experience that provided valuable lessons to the Census Bureau in particular, and a model for future cooperation between federal agencies in general. Following a successful Florida pilot project, high-level management in both agencies perceived that cooperation would result in a win-win situation. Each agency would be able to accelerate its individual map production programs and, in the process, they could develop the first “large-scale” digital map file of the United States. Early negotiations ensured that neither agency would feel it was bearing an unfair burden. A schedule of meetings on a regular basis ensured communications during all phases of the cooperative agreement. The challenge of meeting the Census Bureau’s decennial deadlines provided an added measure of incentive to “get the job done” and an ongoing requirement to measure progress.

    The U.S. Census Bureau/USGS cooperative agreement minimized duplication of effort in federal map automation activities and provided immediate short-term benefits to both agencies. The success of this cooperative venture demonstrated to the Department of Commerce, the Federal Office of Management and Budget (OMB), and the Congress that there were significant benefits to be derived from such activities. The success of this cooperative effort also resonated in the later development of the Federal Geographic Data Committee (FGDC) (OMB 1990), the growing impetus for further cooperative efforts in spatial data sharing, and the increasingly articulated vision of a national spatial data infrastructure (Marx 1992).

    Other success factors. The success of the TIGER System and the ability of the Census Bureau to overcome organizational inertia both within and outside the Census Bureau were due to a number of factors. There was a shared sense both within the Census Bureau and by the data-user public that change was needed in the geographic support process. A primary incentive for developing the TIGER database was the large number of inconsistencies between the statistical and geographic data products in the 1980 and earlier censuses, a product of the complex and clerically intensive preparation of maps, ACGs and GBF/DIME-Files, and geographic reference files (Marx 1986).

    The enormous political and economic ramifications of the decennial census made everyone a stakeholder in the process. The growing importance of the information sector of the economy and growing public demands for more accurate, cost-efficient, timely, and accessible data products helped to promote an environment receptive to the exchange of data, expertise, and experience with other governmental agencies at all levels, the private sector, and the academic community.

    Bureaucratic inertia was further overcome by staff commitment, expertise, and initiative with the Census Bureau’s Geography Division. The transition from traditional to automated mapping for the 1990 census required changes in the organization and planning of the Census Bureau’s mapping activities as well as in the requirements of staff in developing and incorporating new cartographic techniques and computer skills. Motivated by a decennial environment of schedules and fixed deadlines with no alternative to full automation for product delivery and a cooperative agreement with the USGS, the Census Bureau’s staff produced significant results in a relatively short time (Trainor 1990). The resources and skills gained from this experience, combined with a history of successful technical innovations at the Census Bureau, promoted a willingness to reach out and explore the potential for digital data sharing.

    Some criticisms. Countering these positive aspects are criticisms of the TIGER database, such as the relative poor coordinate accuracy of the roads in the major urban centers (the roads that came from the GBF/DIME-files used in lieu of USGS DLG file), lack of address range and ZIP Code improvements or expansion beyond the 345 GBF/DIME-File areas, and inconsistencies in the names and classifications of streets. Public complaints about the quality of the data in the TIGER database provided the Census Bureau and its parent agency, the Department of Commerce, with further verification of the wide applicability and importance of this database beyond the internal needs of the Census Bureau.

    Although valid, most of these situations were not critical for the taking of the 1990 census, the primary mission of the Census Bureau. In fact, many private consulting firms have taken advantage of these “problems” to repackage “new and improved” versions of the bureau’s publicly available extracts from the TIGER database: the TIGER/Line files. The Census Bureau is correcting many of these situations and will release future TIGER extract products with these updates and corrections.

    In general, the TIGER database continues the GBD/DIME-File tradition of being attribute-rich and current but with limited coordinate accuracy in the major urban centers. The USGS’s DLG files, on the other hand, have high “ground truth” accuracy for the features they show but have few attributes (DLG-Enhanced Files, once released, will improve on the latter). In addition, the DLG Files do not contain current information and the USGS has not been provided with the financial resources need to perform frequent, nationwide, and systematic updates. As stated previously, alternative methodologies for updating the files are being evaluated, including an initiative to accelerate the collection of base cartographic data using graphic or digital orthophoto quadrangles or aerial photography (FGDC 1992).

    ENHANCING THE TIGER DATABASE

    Since the completion of the TIGER database for the 1990 census, the Census Bureau has become increasingly aware of its vast potential as well as its current weaknesses. If viewed as a process rather than a product, the TIGER database provides an opportunity to improve statistical accuracy and data quality significantly. The updated address and geographic information systems in a growing number of public and private agencies and the databases of the U.S Postal Service (USPS) provide important means of enhancing the collection, processing, and tabulation of census data.

    The planned release of a new TIGER/Line extract by the Census Bureau containing extended address ranges and ZIP Codes for all areas with city-style mail delivery is significant, not only for the inherent value of the added data (there will be an increase in address range coverage from approximately 55 percent to 85 percent of all housing units in the United States), but because it represents new capabilities that never existed before. For the first time, the Census Bureau will be releasing value-added files for data users after the census that are not directly tied to the decennial statistical data products (however, they will be used for geocoding establishments in the intervening economic census). This precedent also is important in that it reflects a subtle change in the traditional once-a-decade data dissemination paradigm and opens new possibilities for future digital data exchanges. Perhaps, it also is indicative of the more customer-oriented approach mentioned earlier in this chapter.

    Because the Census Bureau was not intended to be the nation’s preeminent mapping agency, any data-sharing agreements to improve the TIGER database must be perceived by the overall organization as primarily benefitting the census-taking process. At this stage of planning for the 1992 and 1997 economic censuses and the 2000 decennial census, the Census Bureau has made an organizational commitment to the integration of the Census Bureau’s related Address Control File with the intercensal update and improvement of the TIGER database. This commitment, however, is dependent on the availability of resources.

    In the absence of a national updated map system, the U.S. Census Bureau has pursued a relatively high-cost mapping compilation strategy for the 1990 and previous censuses (Rhind 1991). Labor-intensive comparisons of reference sources, often of varying scale and quality, have been the primary means for updating census maps. In this respect, the Census Bureau has pursued and maintained close contacts and relationships with other federal agencies, state, regional, and local planning and transportation agencies, engineering firms, aerial survey companies, tax departments, utility firms, and a host of other public and private firms with current map and address reference source materials.

    The development of the TIGER System and other digital spatial and attribute databases, coupled with the proliferation of more powerful computer hardware and GIS software, allows data exchange to occur in a more sophisticated, more timely, and potentially more accurate and less costly manner. From a technical perspective, there appear to be few limits to the advance of this new mode of digital data exchange. According to Cooke (1995), the technical problems of data sharing have mostly been, or are in the process of being, solved. The non-technical components of data interchange may prove more daunting.

    Current Data-Sharing Plans

    Current data-sharing plans at the Census Bureau are twofold. On the one hand, the Census Bureau is investigating the possibility of national sources, predominantly federal agencies, that could provide the information to keep the feature and address-range information in the TIGER database up to date. Based on a report by the Government Accounting Office (GAO 1991), which stated that federal agencies increased their planned expenditures on GIS by about 60 percent between fiscal years 1990 and 1992, the likelihood of such exchanges is promising.

    At the national level, the Census Bureau has entered into or proposed data-sharing agreements with several large governmental or quasi-governmental agencies including the USGS, USPS, the Environmental Protection Agency (EPA), the Soil Conservation Service, the Federal Railroad Administration, the U.S. Army Corps. of Engineers, and the Federal Emergency Management Agency (FEMA). These efforts to improve the spatial and attribute data in the TIGER database are ongoing and likely will include several other agencies by mid-decade. As the coordination of GIS activities improves in the federal sector, bilateral agreements between agencies to improve the TIGER database will likely evolve into multi-agency agreements, as has already occurred at the state and local levels (see Murakami and Greenleaf 1992).

    The Census Bureau also is investigating possible mechanisms for the electronic interchange of updated geographic information with state, local, private, and academic organizations. The current preference of the Census Bureau is to coordinate these efforts and control quality at the state level rather than having to deal with conflicting data and different file formats from several thousand local governments, private agencies, universities, and other sources. Experience indicates, however, that this will not always be possible.

    Role of the FGDC in Data Sharing

    Increased GIS use by federal agencies as well as state and local agencies has led to renewed efforts to coordinate development, sharing, and dissemination of spatial data, primarily through the Federal Geographic Data Committee (FGDC). The FGDC, formed in late 1990 at the direction of the OMB in its Circular A-16 (OMB 1990), includes representatives of fourteen departments and independent agencies but has no direct authority, responsibility, or resources. Participation is voluntary, with decisions based on consensual agreement among its members. Given the current limits on availability of fiscal resources, several agencies have agreed to pursue cooperation in accelerating the 1:12,000-scale digital orthophoto program and the 1:24,000-scale digital quadrangle program. The Census Bureau is working on individual Memoranda of Understanding (MOU) with other federal agencies in the spirit of the FGDC and has agreed to cooperate with the USGS in devising a still more powerful data structure.

    In the long run, the FGDC may provide the vehicle necessary to transform institutional relationships within the federal government as well as with state and local governments, the private sector, and the academic community. The FGDC is making an increased effort to involve the non-federal community in its coordination work. Although the goals are lofty and the potential long-term benefits extraordinary, effective leadership at the highest levels and a concomitant commitment to the development of compatible standards will be necessary. In the absence of these developments, only significant short-term and real cost-saving benefits gained from data sharing by particular agencies will move the process forward toward a national digital spatial database.

    Significantly, in July 1992 the Census Bureau and the USGS signed an amendment to the original 1981 Memorandum of Understanding that commits both agencies to merging the current DLG and TIGER databases, including information resulting from partnerships with other agencies. The development of a shared database that combines the essential geographic information needed by both agencies to carry out their respective institutional mandates will have a profound effect in further stimulating the development of a national spatial data infrastructure in the United States.

    Intercensal Data-Sharing Projects, Post-1990

    Current data-sharing experiences at the Census Bureau have been exploratory, and the actual mechanisms and standards for digital data interchange are still in the process of being developed.  The Census Bureau is engaged in a number of activities to help promote digital data sharing during the 1990s.  These activities include conferences, participation in the FGDC initiative, MOUs with other federal, state, and local agencies, pilot projects, and the planning and imminent release of the prototype version of the TIGER/SDTS (Spatial Data Transfer Standard) file.

    Based on these forums and activities, the Census Bureau has begun to receive initial feedback on the non-technical impediments to and incentives for digital spatial data interchange.  The Census Bureau has provided its digital geographic and statistical data sets to the public at the cost of dissemination and as a public resource (OMB 1992).  Other public and private agencies, however, have different perspectives and regulations pertaining to their own data sets and on the updates they may perform.  Profit is a major concern of private companies, and public agencies also are looking to their products as a source of revenue.

    States and local agencies consistently have reported one or more of the following problems in trying to coordinate a GIS:

    •    Agencies wanting proprietary control of internal data

    •    Lack of resources in one department or institution affecting data requirements of another

    •    Archaic systems

    •    Managers and commissioner-level officials who know, or care, little about GIS

    •    Staff turnover

    •    Lack of commitment

    Once a state or local GIS is operational, the lack of overt incentives to expend the additional time and expense required to feed local updates into the TIGER/Line or SDTS formats for interchange become more apparent.  Ensuring the currency, accuracy, and quality of the TIGER database is an integral part of ensuring the accuracy and quality of the associated census data, which are used for reapportionment, redistricting, the distribution of federal funds, and innumerable planning and development programs – but this may be a long-term and nebulous consideration for some agencies.  The lack of a clearly defined formal process for data interchange by the Census Bureau could provide an even greater impediment to institutions willing to share data.

    The existence of multiple geographic data file formats also have inhibited the interchange of data.  Future geographic data files at the Census Bureau will be released in accordance with a recent Federal Information Processing Standard (FIPS) – the SDTS.  Adoption of the SDTS involved cooperation of federal, state, and local officials, the academy community, and private sector over an extended period of time.  The Census Bureau was an active participant in the development of this new federal standard for data exchange and, to that end, released its first prototype TIGER/SDTS file (Davis et al. 1992).  However, the effect of this rather complex format on data interchange is not yet clear.

    Each data-sharing agreement brings forth new possibilities, new arrangements between agencies, and the potential for new products.  Working with a variety of agencies and soliciting recommendations for improving TIGER, Census Bureau staff have noted similarities among the interests of many agencies.  For instance, conversations with the USPS and the U.S. Department of Transportation have revealed similar interests in enhancing attributes for streets (e.g., turn and directional restrictions).  In many cases, the Census Bureau would be able to use the enhancements needed by other agencies for improving the quality and cost-effectiveness of its own internal operations (e.g., routing of enumerators).

    Proposed Census/USPS cooperative program.  The USPS and the Census Bureau have been working together for more than thirty years in the delivery and return of questionnaires for the decennial, agriculture, and the economic censuses and surveys.  The increasing use of mail-out/mail-back procedures throughout the nation has made the USPS an indispensable partner in the Census Bureau’s data-collection activities.  The Census Bureau traditionally has paid the USPS to verify the completeness and accuracy of its decennial census address list, which was purchased from private vendors and enhanced through in-house programs, prior to the mailout of questionnaires.  The Census Bureau also worked with the USPS on the development of computer algorithms to match the ZIP+4 files to GBF/DIME-File records during the 1980s.  ZIP+4 files, also known as the Address Management System (AMS) Files, contain potential address ranges for all areas where the USPS delivers mail.

    In an effort to enhance this cooperation to the benefit of both agencies, the Census Bureau proposed a formal Memorandum of Understanding (MOU) with the USPS similar to the one it had with USGS in the 1980s. In 1990, the Census Bureau and the USPS, with the participation of the USGS, began cooperating on a pilot project to provide a better geographic database for all three agencies.  If signed, this MOU will have broad implications, not only for these three agencies, but for the GIS community as a whole during the 1990s.

    The Census Bureau’s proposal envisions a four-year file update/enhancement plan (fiscal years 1994-1997) and subsequent ongoing cooperative efforts to update a Post/TIGER database.  As with the earlier USGS agreement, the USPS/Census Bureau MOU would formalize a seemingly well-suited alliance between two agencies.  Cooperative database-building activities could reduce duplication of efforts, thereby reducing overall costs, as well as improve the geographic and attribute accuracy of the information available to each agency.

    The Census Bureau’s objectives for the proposed joint program during the intercensal years are (1) to obtain updated information on the location of streets with their names, address ranges, and ZIP codes as well as the location of group quarters, office building or other locations of economic activity, and (2) to improve the error-prone decennial census address lists development operations.  According to a recent GAO report (1992), enumerator follow-up to vacant and nonexistent units alone resulted in an added expenditure of approximately $317 million to the 1990 census operation.   Accomplishing the above objectives will enable the Census Bureau to reduce its critical dependence on a large, temporary clerical workforce before and during each decennial census, thereby reducing costs, and to improve the overall quality and consistency of decennial census data products.

    In the overall proposal, the joint venture envisions updating the TIGER database to permit automated analysis of carrier routes and the production of carrier route maps for use by the USPS.  In the pilot study, the effort to improve and maintain the positional accuracy and completeness of the TIGER database involved the use of Global Positioning System (GPS) technology with receivers mounted on USPS-supplied vehicles.  In order to improve and update the geocoding capability of the TIGER system, the pilot study also updated the address ranges in the TIGER database and added ZIP+4 Codes and other USPS information.  The joint venture envisioned would extend similar geocoding improvements to all parts of the United States with city-style address systems.  The Census Bureau would provide the USPS with its technical and geographic expertise.

    Potential impediments.  Although this data-sharing scenario appears to satisfy the needs of both agencies, there are a number of organizational, behavioral, and institutional impediments that will need to be overcome.  Some of these impediments are specific to these two agencies while other are generic to any data-sharing milieu.  One specific impediment is that the USPS is not part of the FGDC.  The USPS also is a quasi-federal agency, which means that it must justify its participation in an agreement on a benefit/cost basis including expected revenue or savings from potential products.  There also are questions about what information will be shared and what will be the property of each organization.

    A more general institutional impediment is the difficult of building a single database to serve the needs of different agencies.  Federal agencies have worked independently of each other for a long period of time collecting and structuring their data according to geographic units based on their own unique criteria and naming conventions.  Data sharing presupposes a strong, long-term, funded commitment to reconcile what really constitutes different versions of the same reality.  In order to reach agreement, a shared database initially may involve compromises that could make it less effective than two separate databases.  Each agency has its own self-interest and mission that must be met first.  Short-term objectives may become more pronounced and inhibit progress.  The need to understand each other’s terminology, organizational structure, and needs represents another potential impediment.

    Another important issue, not only for the Census Bureau but for all potential data partners, is the potentially differing perception of the benefits from data sharing.  One agency may believe that it is giving up more than the other agency and is bearing an unfair burden, causing a negative effect on data-sharing plans.  Some groups within each agency may either be opposed to or less than committed to the idea of data sharing.  While this issue was always in the background during the joint Census Bureau/USGS Cooperative Mapping Project, it never came to the forefront as a major issue.

    Another potentially critical impediment common to bureaucracies is the inertia effect; that is, it is easier to stick with the tried and reasonably true methods than to try something new.  Change can be intimidating and can upset a delicate balance of power in an organization.

    OTHER ONGOING DATA-SHARING ACTIVITIES

    In a broad sense, the Census Bureau traditionally has been in the business of sharing geographic data and has a long history of partnerships with state and local governments.  The Census Bureau receives updated governmental unit boundaries from local officials on a periodic basis through its Boundary and Annexation Survey.  The Census Bureau also works with local Census Statistical Area Committees, composed of representatives of the public, private, and academic communities, in delineating the boundaries of census statistical areas such as census tracts, block groups, and census-designated places.

    The Census Bureau also has worked closely with state election officials to provide the information they need for redistricting and reapportionment; with the U.S. Department of Education to incorporate the boundaries of school districts as a means to produce data for school districts; and with metropolitan planning organizations to improve the quality of the Census Bureau’s address reference files, which improves the quality of the usefulness of the census journey-to-work and place-of-work data, and to define traffic analysis zones in terms of census blocks to facilitate the tabulation of decennial census data for those areas.  The Census Bureau has built its massive geographic database primarily from source materials acquired from state and local agencies.  In a new program based on 1990 census data, data users may independently aggregate census blocks to define their own statistical areas and receive maps and data profiles of these user-defined areas from the Census Bureau on a cost-reimbursable basis.

    In addition, the Census Bureau maintains and is constantly improving its huge, ongoing institutional data-sharing apparatus.  Each of the Census Bureau’s twelve regional offices supports information services and geographic programs that coordinate activities with state data centers and their affiliates throughout the United States.  The Census Bureau’s Data User Services Division combines educational functions (e.g., ongoing workshops on TIGER, census maps, and data products) with its data distribution functions.  The Census Bureau participates in the kindergarten through twelfth grade (K-12) geographic literacy campaign in the United States a means to address the important issues of access to new information technologies.  Public access issues (Emergency Planning and Community Right-to-Know Act 1986) also have provided the impetus for an ongoing cooperative project with the EPA and the National Oceanic and Atmospheric Administration (NOAA) that supports the development of public domain software that links and displays environmental, socioeconomic, and demographic data using an extract of the TIGER database.

    From a more global perspective, the Census Bureau shares its technological and statistical know-how with a number of participating countries through its in-house and overseas training programs.  The Census Bureau also is cooperating with Statistics Canada (Haythornthwaite 1992) and pursuing talks with Mexico’s statistical agency, Instituto Nacional de Estadistica, Geografia e Informatica, to create a North American Common Borders Database.  In summary, the Census Bureau maintains a huge ongoing apparatus that supports and complements its current efforts at spatial data interchange.

    CONCLUSIONS

    As the Census Bureau prepares for the 2000 census, change, once again, appears imminent.  According to a recent GAO report (1992,4), “the current approach to taking the census appears to have exhausted its potential for counting the population cost-effectively.”  Similar statements were made in reference to the Census Bureau’s geographic support program following the 1980 census (Tomasi 1990).  These statements have recurred with periodic frequency in the recent history of census-taking.  In large part, the innovations that followed were a response to intense public scrutiny, a result of a process that has significant and far-reaching political (reapportionment and redistricting) and economic (distribution of government funds) consequences.  Over the past fifty years, the Census Bureau has met not only the challenges brought about by massive social, demographic, and economic change, but has provided effective leadership in applying and diffusing a number of new technologies to both the governmental and non-governmental sectors.

    The application and use of new technologies on a vast scale by public organizations are reshaping the internal organization and relationships within the public sector as well as among the public and private sectors and the academic and research communities.  The dominant values of narrow, functionally separate governmental agencies and departments are increasingly being replaced by a system of greater complexity and interrelatedness and a growing trend toward public and private sector cooperation.  The Census Bureau’s TIGER system is an important example of this phenomenon and may be a primary motivator for such changes.

    The Census Bureau’s geographic and statistical products – inexpensive and ubiquitous spatial and attribute raw material – have helped transform GIS from a highly technical field dominated by large agencies, private firms, and universities, to one that is becoming increasingly accessible to many data users.  Advances in our technological infrastructure thus far have been the primary factor enabling institutions to develop and share digital geographic data.  Personal computers, workstations, CD-ROMS, and databases available for automation were relatively nonexistent until the 1980s.  The incipient use of new telecommunication technologies, such as the Internet, may have an equally profound effect on data sharing and online services in the latter part of this decade.

    As computer hardware and software continue to become less expensive and more powerful, the vast potential of GIS will depend increasingly on the behavioral, organization, and institutional issues acting as impediments and incentives to the sharing of geographic data.  The integration of various multi-media technologies and the growing capability to link a wide variety of public and private databases also raise a number of privacy issues.  Deriving the full benefits of GIS and related information systems will depend, to a significant degree, on how society approaches and resolves these issues (Onsrud 1992).

    Based on past experience, it will require extraordinary leadership, communication and flexibility among agencies to facilitate the process of spatial data interchange.  Data sharing will be most successful when such ventures can be justified by short-term results, verified cost reductions, improved operations, and minimal problems of data ownership.  Data sharing will be enhanced to the degree that these ventures can be built around joint development projects such as the Census Bureau/USPS and the Census Bureau/USGS experiences in the 1990s.  Awareness of the need for such coordination is growing and is best reflected in the increasing number of statewide GIS committees and partnerships between the federal and state communities.

    Geographic databases have been built thus far to support the mandates of single institutions or parts of an institution.  All who collect and manage data for activities related to their own responsibilities will need to understand and appreciate the value of those data to others and to collect and structure their data accordingly.  In order to take full advantage of the opportunities offered to these new technologies, business, government, and academic will need to develop, support, and fund data exchange on a systematic and ongoing basis as well as promote accessibility of GIS capabilities to all sectors of our society.

     

    REFERENCES

    Anderson, M.J. 1988. The American census: a social history. New Haven: Yale University Press.

    Boudriault, G. 1987. Topology in the TIGER file. Eighth International Symposium on Computer-Assisted Cartography, Proceedings. Baltimore, Maryland, 258-263.

    Broome, F.R. and D.B. Meixler. 1990. The TIGER database structure. Cartography and Geographic Information Systems 17, 1:39-47.

    Carbaugh, L.W. and R.W. Marx. 1990. The TIGER system: a Census Bureau innovation serving data analysts. Government Information Quarterly 7, 3:285-306.

    Cooke, D. 1995. Sharing street centerline spatial databases. In H.J. Onsrud and G. Rushton, eds., Sharing Geographic Information. New Brunswick, NJ: Center for Urban Policy Research, Rutgers University.

    Corbett, J.P. 1979. Topological principles in cartography. Technical Paper 48. U.S. Bureau of Census, Washington, D.C.

    Davis, B.A., J.R. George, and R. W. Marx. 1992. TIGER/SDTS: standardizing an innovation. Cartography and Geographic Information Systems 19, 5:321-327.

    Emergency Planning and Community Right-To-Know Act: Title 3 of the Superfund Amendments and Reauthorization Act of 1986. PL 99-499, 17 October 1986. United States Statuates at Large 100. pp. 1728-1758.

    Federal Geographic Data Committee. 1992. Multi-agency initiative to meet high priority requirements for base cartographic data. FGDC Subcommittee of Base Cartographic Data. Washington, D.C.

    Government Accounting Office. 1991. Geographic Information Systems: information on federal use and coordination. IMTEC 91-72-FS. Washington, D.C.

    ________. 1992. Decennial Census: 1990 results show need for fundamental reform. GAO/GGD-92-94. Washington, D.C.

    Haythornwaite, T. 1992. Development of the United States-Canada Common Border Database. The Operational Geographer 10, 1:28-30.

    Kinnear, C. 1987. The TIGER Structure. Eighth International Symposium on Computer-Assisted Cartography, Proceedings. Baltimore, Maryland, 249-257.

    Marx, R.W. 1986. The TIGER System: automating the geographic structure of the United States census. Government Publications Review 13, 181-201.

    ________. 1992. Building the National Spatial Data Infrastructure: the data integrity challenge. Paper presented at the Regional Surveying Engineering Conference, Hartford, Connecticut.

    McKenzie, B.Y., and R.A. LaMacchia. 1987. The U.S. Geological Survey-U.S. Bureau of Census Cooperative Digital Mapping Project: a unique success story. Paper presented at American Congress on Surveying and Mapping meeting, Reno, Nevada. Fall.

    Murakami, E., and K. Greenleaf. 1992. Multi-agency TIGER file updating. URISA Proceedings 2:25-35.

    Office of Management and Budget. 1990. Coordination of surveying, mapping, and related spatial data activities. OMB Circular A-16 (Revised). Washington, D.C.

    _______. 1992. Management of federal information resources. OMB Circular A-130. Washington, D.C.

    Onsrud, H. 1992. Privacy and spatial databases. Technical Program Abstracts., 27th International Geographical Congress, Washington, D.C., 480-481.

    Rhind, D.W. 1991. Counting the people: the role of GIS. In D.J. Maguire, M.F. Goodchild, and D.W. Rhind, eds., Geographic information systems: principles and applications. Longman Scientific and Technical, Essex, 2:127-137.

    Silver, J. 1977. The GBF/DIME system: development, design and use. Paper presented at 1977 Joint Annual Meeting of the American Society of Photogrammetry and the American Congress on Surveying and Mapping. U.S. Government Printing Office, 1977-240-869/1102.

    Sobel, J. 1978. GBF/DIME system – development and reference source problems. Applied Geography Conference, SUNY – University Center at Binghamton, 1:112:121.

    _______. 1986. Principal components of the Census Bureau’s TIGER file. Research in contemporary and applied geography: a discussion series. SUNY at Binghamton, 10, 3:1-17.

    Tomasi, S.G. 1990. Why the nation needs a TIGER system. Cartography and Geographic Information Systems 17, 1:21-26.

    Trainor, T.F. 1990. Fully automated cartography: a major transition at the Census Bureau. Cartography and Geographic Information Systems 17, 1:27-28.

    U.S. Bureau of Census. 1973. Census Use Study. International DIME Colloquium. Confernce Proceedings, Washington, D.C., August 27-29, 1972.

    White, M. 1984. Technical requirements and standards for a multipurpose geographic data system. The American Cartographer 11, 1:15-26.

  • TIGER Database Historical Perspective

    In my last two columns, I’ve made several references to geospatial data. Jon Sperling, Ph.D. GISP, wrote in and commented on the omission of the importance of TIGER data in the history of geospatial data development and commercialization. He made reference to a document he wrote that was published in 1995 regarding the development and maintenance of the TIGER database. I’ve decided to reprint his work, with his permission, as this week’s column. It gives keen insight into the early stages of TIGER. Albeit quite in-depth, it’s a fascinating read for gaining a historical perspective on geospatial data development.

    Keep in mind that this document was written in 1992 so there are references to initiatives, etc. that were subsequently developed and that you enjoy today.

    Sperling argues that our public investment in TIGER need not be just history but a pro-active means to leverage partnerships and new advances and innovations (e.g. synergistic links with national parcel data initiatives, local/state/federal data sharing and a national road network). Census still remains a pioneer in supporting and furthering geospatial science at all levels of our society for the betterment of our Nation’s communities.

    Dr. Sperling is currently a Senior Researcher of Geographic Information and Analysis at the Office of Policy, Development and Research for the U.S. Department of Housing and Urban Development. He has designed and led many innovative geospatial, addressing, and data integration efforts in coordination with local and state governments and the academic research community. Dr. Sperling was involved in the initial development of the Nation’s TIGER/Master Address File databases for the 1990 and 2000 Census, enabling digital spatial data sharing capabilities, and efforts to enhance its coordinate accuracy and data quality. Currently, he is working with university partners on a number of innovative research applications to enable sophisticated querying of unstructured text and tables using textual spatial references in the data.


    Jonathan Sperling, “Development and Maintenance of the TIGER Database: Experiences in Spatial Data Sharing at the U.S. Bureau of the Census,” in Harlan J. Onsrud and Gerard Rushton, eds., SHARING GEOGRAPHIC INFORMATION (New Brunswick, NJ: Center for Urban Policy Research). Copyright 1995 by Rutgers, The State University of New Jersey. Reprinted with permission.

     

    Development and Maintenance of the TIGER Database: Experiences in Spatial Data Sharing at the U.S. Bureau of the Census (1992)

    The U.S. Census Bureau has played, and will continue to play, a vital role in the development, maintenance, and sharing of spatial and attribute data for Geographic Information Systems (GISs) on the local, regional, national, and international levels. The Census Bureau’s development of shareable geographic data files, the GBF/DIME (Geographic Base File/Dual Independent Map Encoding) Files for the 1970 and 1980 censuses, and the TIGER (Topologically Integrated Geographic Encoding and Referencing) database for the 1990 census, have provided a major impetus to the rapid growth and diffusion of GIS technology. This chapter discusses the Census Bureau’s experiences in the spatial data sharing during these two file-building projects as well as from ongoing experiences in developing Memoranda of Understanding with federal and state agencies to update and improve the spatial and attribute data in TIGER. On the basis of these experiences, preliminary generalizations are made concerning the organizational issues that may facilitate or impede the future digital interchange of spatial data.

    Introduction

    The entrance and persistence of the nation’s lead statistical agency as a primary producer and user of both geographic and attribute data have grown out of practical but critical concerns (Tomasi 1990). The mandate to conduct a population and housing census of the entire nation and its territories every ten years, and then disseminate the resulting information  quickly and accurately, has led to the need to devise innovative ways of improving the collection, processing, and tabulation of data.  These improvements have aimed at four goals: increasing efficiency and timeliness, improving data quality, lowering costs, and providing new products for the data user.

    Over the past half century, the Census Bureau has pursued innovations and led the government and private sector in computerization, statistical sampling and interviewing techniques, data processing, quality control, and cartographic techniques, to name but a few (Anderson 1989).  The Census Bureau pioneered the first large-scale commercial user of the computer with UNIVAC 1 following the 1950 census and the development of the Film Optical Sensing Device for Input to Computers for the 1960 census.  The broad use of computer mapping by local governments and private firms was strongly influenced by the Census Bureau when it developed the GBF/DIME-Files for the 1970 and 1980 censuses and the TIGER System for the 1990 census.

    In addition to being one of the nation’s largest digital geographic databases — currently sixteen gigabytes — TIGER enables the automated spatial manipulation of census data for all legal and statistical entities in the United States and its territories.  Every state and local government now has the capability to create rudimentary GIS using small-area census data, publicly available extracts of the TIGER database – TIGER/Line  files – and the appropriate hardware and software.  More than 130 private vendors currently have the capability of processing TIGER/Line files, and the number is growing.

    In this respect, the development of the TIGER database may be the most important “data” file from the 1990 Census of Population and Housing.  The accessibility and widespread potential application of this innovation make it qualitatively different from earlier technological developments at the Census Bureau.  The TIGER database will be used not only internally to administer future censuses and surveys (see Marx 1986 for a basic rationale of the TIGER system) but externally to provide a major impetus to the development and sharing of integrated special information systems in the public and private sectors as well as the academic community.

    A common theme in the GIS literature, generated both within and outside the Census Bureau, has been the notion that although the Census Bureau developed its GBF/DIME-Files and TIGER database to meet internal Census Bureau needs, their existence has facilitated applications well beyond the scope of census-taking.  Perhaps analogous to the many commercial spin-offs that have been generated from wartime military innovations or the nation’s space program, the decennial census operation, conducted by the government’s largest non-military assemblage of people and resources, has been responsible for a number of innovations, some already outlined, that have had a major effect on the private sector and the academic research community.

    The Census Bureau’s recognition of these “consumer spin-offs” traditionally has never been well articulated or coordinated because most innovations have resulted from an internal production standpoint rather than a customer-oriented design.  Recent efforts toward building a national spatial data infrastructure and the Census Bureau’s adoption of the principles of Total Quality Management and Strategic Planning create the external and internal incentives, respectively, to stimulate a change in that design.  Paradoxically, however, the fiscal constraints of the 1990s and their impact on congressional funding, while often considered an incentive for data sharing, may also function as an impediment in the early developmental stages of new technologies.

    THE DEVELOPMENT OF SHAREABLE GEOGRAPHIC DATA FILES – GBF/DIME-File Development 1966-1982

    Many local agencies have been introduced to GIS by the Census Bureau through is various geographic base-building projects over the past twenty-five years.  The development of the Address Coding Guides (ACG) for the 1970 census and the GBF/DIME-Files for the final stages of the 1970 census and for large-scale use in the 1980 census were major steps toward full automation of the Census Bureau’s geographic support programs.  Althought the ACGs provided the building blocks for the later development of the GBF/DIME-Files, they lacked geographic coordinates and topological structure (Marx 1986).

    The design and development of these computer-readable files involved the active participation of federal, state, local, private and academic organizations.  The Census Use Study, a small-area data research group sponsored by the Census Bureau from 1966 to 1969, was instrumental in creating and diffusing knowledge about a system that represented map features numerically for processing by a computer to create a geographic base file (U.S. Bureau of the Census 1973).  The enhancement of this body of knowledge was of critical importance to the Census Bureau because it enabled the adoption of census-by-mail enumeration methodologies for the major urban centers of the United States.

    The change in enumeration procedures was a response to the increasing costs and difficulty of conducting a traditional door-to-door canvassing of the population, a growing and increasingly urban population living within areas having mail delivery by house-number/street-name address, and technical feasibility of linking such addresses with the geographic units used for data tabulations due to improvements in computer capabilities.  For the 1980 census, the GBF/DIME-Files were enhanced to cover 287 of the nation’s largest urban centers, representing more than 60 percent of the population but less than 2 percent of the nation’s land area (Carbaugh and Marx 1990).

    Data sharing during the 1970s.  The development of the ACGs and GBF/DIME-Files involved data sharing with more than 300 local planning agencies.  Sharing primarily took the form of converting analog data into a computer-readable format rather than digital exchange per se.  The long-term nature of these relationships provided the Census Bureau with intimate knowledge of the resources available to local agencies, the limitations of available data, and the willingess and ability of agencies to share data.  At the same time, local planning agencies and others, through their association with the Census Bureau, became increasingly aware of the potential computer mapping, automated address matching, and spatial data analysis to meet local needs (Sobel 1978).  These relationships played an important role in the later development of the TIGER system.

    Monetary and other incentives to the local agencies played a major role in the “data sharing” development of the ACGs and GBF/DIME-Files (Silver 1977).  In many cases, local agencies completed work under contract with the Census Bureau or with funding provided by the Department of Housing and Urban Development (HUD), and Federal Highway Administration (FHWA), and other federal, state, and local planning sources.  Sensitive to the fact that the development of the GBF/DIME-Files provided a practical solution to many needs of local governments, the Census Bureau offered to provide the computer programs, processing methodology, and clerical procedures for creating  and updating the file, as well as a free copy of the completed file, to each participating local agency.  The Census Bureau also offered to do the data keying and processing if agency resources were limited.  The promise of higher quality data when these files were used for taking and tabulating the 1970 and 1980 census provided a further incentive for data sharing.

    As a result of this process, the Census Bureau and local officials learned that the quality and currency of existing data used by planning agencies could not be taken for granted.  For example, many local communities relied on the knowledge of a few people for the location of dwellings, address-numbering systems often were not systematic, tax assessor sources sometimes did not meet the bureau’s quality standards, and data from different agencies often were inconsistent.  Because of these situations, the initial transition to address assignment via automated processes was difficult.

    The efforts of working with so many local agencies also challenged the Census Bureau.  During the file-building projects, there was turnover in project personnel and key decision makers in the local agencies as well as at the Census Bureau.  Some “champions” of the new methods were not reelected or moved on to other jobs.  The long-term benefits of building such files were not always apparent to public administrators.  Some administrators viewed the new computer technology as a threat to their role in the agency.  Also, during the 1970s, there was a general lack of understanding (personal computers had not yet been invented) and/or trust in the new computer technology and the ever-present fear of “big brother” mainframe computers held by a few large government agencies.  All these factors tended to hamper development activities and to result in considerable variation in the quality, time expended, and funds necessary to complete the GBF/DIME-Files.

    Data sharing during the 1980s.  Census Bureau funding of data collection and coding by local agencies to create the GBF/DIME-Files created precedents that would later affect the pre-1990 TIGER-building efforts.  The overall reductions in federal aid to cities and states during the 1980s provided an atmosphere of “less than cooperative initial attitudes” among many local agencies struggling with small staffs and fewer resources than they had in the 1970s.  Many agencies expected to be paid for their efforts.  These situations, and the perceived difficulties inherent in working with several hundred local agencies, contributed to the Census Bureau’s decision to do most of the map and address updates for the 1990 census in-house, albeit often based on materials supplied by local agencies.

    Changes in the original GBF/DIME-File format by local agencies exacerbated some early data-sharing efforts.  Many of the larger files that had been maintained by local agencies (e.g., New York City) had been adapted and enhanced to meet local planning and administrative needs.  Fiscal difficulties at the local level, time constraints on the Census Bureau, and the lack of additional programming staff in all agencies often precluded efforts to recreate the original file structure without losing the map and address updates.  In these cases, the feature and address range update work had to be redone manually by the Census Bureau from digital plots and databases.

    One of the general weaknesses of the GBF/DIME-Files was that they were limited geographically and, therefore, the ability to use the files on an ongoing basis was limited to large-scale users with on-line access to mainframe computers.  Relatively few of the original GBF/DIME-Files given to local governments were updated and maintained during the 1980’s. Even fewer of the locally updated files met Census Bureau standards for direct incorporation into the TIGER database. In practice, however, these updated GBF/DIME-Files provided the Census Bureau with its first challenge in the digital spatial data exchange at the local level.

    Digitized GBF/DIME-Files, attribute-rich but of mediocre
    coordinate accuracy, formed the cartographic base for 345 urban centers in the 1990 TIGER database. Absolute coordinate accuracy was not a primary concern in the development of the GBF/DIME-Files, as they were used primarily by the Census Bureau for geocoding rather than mapping purposes. Although their coordinate accuracy was well below that of the U.S. Geological Survey’s (USGS’s) Digital Line Graph (DLG) files derived from their 1:100,000-scale maps, these files represented features with all their respective feature names, address ranges, and 1980 geographic area codes in their correct relative location – sufficiently accurate for taking a census (Sobel 1986).

    Although the Census Bureau would have liked to provide an enhanced cartographic quality, the deadline pressures of an upcoming decennial census forced management to abandon initial plans to align this information to the USGS’s DLG files. Also, because of staff and time constraints, the files were sent to four private-sector contractors for digitizing of feature updates using Census Bureau-supplied updated 1980 census maps. The results from these arrangements were of mixed quality.

    TIGER Database Development, 1983-1990

    The institutional knowledge and experience gained from the development of the GBF/DIME-Files, further theoretical and conceptual advances in the field of mathematics (Corbett 1979 and White 1984), and the “enabling” availability of new and affordable technology, provided fertile ground for the Census Bureau’s next challenge: the development of the TIGER database for use in the 1990 census. Whereas the GBF/DIME-Files covered small noncontiguous portions of the United States and were developed initially without spatial or geographic references in their design, the TIGER database covered the entire nation and its territories and was grounded in a more rigorous conceptual model of topology and space (see Boundriault 1987; Kinnear 1987; Broome and Meixler 1990).

    Census Bureau/USGS cooperative agreement. In addition to data-sharing arrangements on the local level, the ability to complete the building of the TIGER database in time for the 1990 census was directly dependent on a landmark 1983 data-sharing agreement with the USGS. The USGS provided the Census Bureau with computer files of scanned versions of its 1:100,000-scale maps for the lower forty-eight states. In return, the Census Bureau assigned cartographic classification codes to the roads in these files. The resultant product formed the cartographic base for all areas outside the large urban centers covered by the GBF/DIME-Files, thereby enabling the Census Bureau to complete a coast-to-coast digital map base in time for the 1990 census (McKenzie and LaMacchia 1987).

    Interagency cooperation with the USGS was an experience that provided valuable lessons to the Census Bureau in particular, and a model for future cooperation between federal agencies in general. Following a successful Florida pilot project, high-level management in both agencies perceived that cooperation would result in a win-win situation. Each agency would be able to accelerate its individual map production programs and, in the process, they could develop the first “large-scale” digital map file of the United States. Early negotiations ensured that neither agency would feel it was bearing an unfair burden. A schedule of meetings on a regular basis ensured communications during all phases of the cooperative agreement. The challenge of meeting the Census Bureau’s decennial deadlines provided an added measure of incentive to “get the job done” and an ongoing requirement to measure progress.

    The U.S. Census Bureau/USGS cooperative agreement minimized duplication of effort in federal map automation activities and provided immediate short-term benefits to both agencies. The success of this cooperative venture demonstrated to the Department of Commerce, the Federal Office of Management and Budget (OMB), and the Congress that there were significant benefits to be derived from such activities. The success of this cooperative effort also resonated in the later development of the Federal Geographic Data Committee (FGDC) (OMB 1990), the growing impetus for further cooperative efforts in spatial data sharing, and the increasingly articulated vision of a national spatial data infrastructure (Marx 1992).

    Other success factors. The success of the TIGER System and the ability of the Census Bureau to overcome organizational inertia both within and outside the Census Bureau were due to a number of factors. There was a shared sense both within the Census Bureau and by the data-user public that change was needed in the geographic support process. A primary incentive for developing the TIGER database was the large number of inconsistencies between the statistical and geographic data products in the 1980 and earlier censuses, a product of the complex and clerically intensive preparation of maps, ACGs and GBF/DIME-Files, and geographic reference files (Marx 1986).

    The enormous political and economic ramifications of the decennial census made everyone a stakeholder in the process. The growing importance of the information sector of the economy and growing public demands for more accurate, cost-efficient, timely, and accessible data products helped to promote an environment receptive to the exchange of data, expertise, and experience with other governmental agencies at all levels, the private sector, and the academic community.

    Bureaucratic inertia was further overcome by staff commitment, expertise, and initiative with the Census Bureau’s Geography Division. The transition from traditional to automated mapping for the 1990 census required changes in the organization and planning of the Census Bureau’s mapping activities as well as in the requirements of staff in developing and incorporating new cartographic techniques and computer skills. Motivated by a decennial environment of schedules and fixed deadlines with no alternative to full automation for product delivery and a cooperative agreement with the USGS, the Census Bureau’s staff produced significant results in a relatively short time (Trainor 1990). The resources and skills gained from this experience, combined with a history of successful technical innovations at the Census Bureau, promoted a willingness to reach out and explore the potential for digital data sharing.

    Some criticisms. Countering these positive aspects are criticisms of the TIGER database, such as the relative poor coordinate accuracy of the roads in the major urban centers (the roads that came from the GBF/DIME-files used in lieu of USGS DLG file), lack of address range and ZIP Code improvements or expansion beyond the 345 GBF/DIME-File areas, and inconsistencies in the names and classifications of streets. Public complaints about the quality of the data in the TIGER database provided the Census Bureau and its parent agency, the Department of Commerce, with further verification of the wide applicability and importance of this database beyond the internal needs of the Census Bureau.

    Although valid, most of these situations were not critical for the taking of the 1990 census, the primary mission of the Census Bureau. In fact, many private consulting firms have taken advantage of these “problems” to repackage “new and improved” versions of the bureau’s publicly available extracts from the TIGER database: the TIGER/Line files. The Census Bureau is correcting many of these situations and will release future TIGER extract products with these updates and corrections.

    In general, the TIGER database continues the GBD/DIME-File tradition of being attribute-rich and current but with limited coordinate accuracy in the major urban centers. The USGS’s DLG files, on the other hand, have high “ground truth” accuracy for the features they show but have few attributes (DLG-Enhanced Files, once released, will improve on the latter). In addition, the DLG Files do not contain current information and the USGS has not been provided with the financial resources need to perform frequent, nationwide, and systematic updates. As stated previously, alternative methodologies for updating the files are being evaluated, including an initiative to accelerate the collection of base cartographic data using graphic or digital orthophoto quadrangles or aerial photography (FGDC 1992).

    ENHANCING THE TIGER DATABASE

    Since the completion of the TIGER database for the 1990 census, the Census Bureau has become increasingly aware of its vast potential as well as its current weaknesses. If viewed as a process rather than a product, the TIGER database provides an opportunity to improve statistical accuracy and data quality significantly. The updated address and geographic information systems in a growing number of public and private agencies and the databases of the U.S Postal Service (USPS) provide important means of enhancing the collection, processing, and tabulation of census data.

    The planned release of a new TIGER/Line extract by the Census Bureau containing extended address ranges and ZIP Codes for all areas with city-style mail delivery is significant, not only for the inherent value of the added data (there will be an increase in address range coverage from approximately 55 percent to 85 percent of all housing units in the United States), but because it represents new capabilities that never existed before. For the first time, the Census Bureau will be releasing value-added files for data users after the census that are not directly tied to the decennial statistical data products (however, they will be used for geocoding establishments in the intervening economic census). This precedent also is important in that it reflects a subtle change in the traditional once-a-decade data dissemination paradigm and opens new possibilities for future digital data exchanges. Perhaps, it also is indicative of the more customer-oriented approach mentioned earlier in this chapter.

    Because the Census Bureau was not intended to be the nation’s preeminent mapping agency, any data-sharing agreements to improve the TIGER database must be perceived by the overall organization as primarily benefitting the census-taking process. At this stage of planning for the 1992 and 1997 economic censuses and the 2000 decennial census, the Census Bureau has made an organizational commitment to the integration of the Census Bureau’s related Address Control File with the intercensal update and improvement of the TIGER database. This commitment, however, is dependent on the availability of resources.

    In the absence of a national updated map system, the U.S. Census Bureau has pursued a relatively high-cost mapping compilation strategy for the 1990 and previous censuses (Rhind 1991). Labor-intensive comparisons of reference sources, often of varying scale and quality, have been the primary means for updating census maps. In this respect, the Census Bureau has pursued and maintained close contacts and relationships with other federal agencies, state, regional, and local planning and transportation agencies, engineering firms, aerial survey companies, tax departments, utility firms, and a host of other public and private firms with current map and address reference source materials.

    The development of the TIGER System and other digital spatial and attribute databases, coupled with the proliferation of more powerful computer hardware and GIS software, allows data exchange to occur in a more sophisticated, more timely, and potentially more accurate and less costly manner. From a technical perspective, there appear to be few limits to the advance of this new mode of digital data exchange. According to Cooke (1995), the technical problems of data sharing have mostly been, or are in the process of being, solved. The non-technical components of data interchange may prove more daunting.

    Current Data-Sharing Plans

    Current data-sharing plans at the Census Bureau are twofold. On the one hand, the Census Bureau is investigating the possibility of national sources, predominantly federal agencies, that could provide the information to keep the feature and address-range information in the TIGER database up to date. Based on a report by the Government Accounting Office (GAO 1991), which stated that federal agencies increased their planned expenditures on GIS by about 60 percent between fiscal years 1990 and 1992, the likelihood of such exchanges is promising.

    At the national level, the Census Bureau has entered into or proposed data-sharing agreements with several large governmental or quasi-governmental agencies including the USGS, USPS, the Environmental Protection Agency (EPA), the Soil Conservation Service, the Federal Railroad Administration, the U.S. Army Corps. of Engineers, and the Federal Emergency Management Agency (FEMA). These efforts to improve the spatial and attribute data in the TIGER database are ongoing and likely will include several other agencies by mid-decade. As the coordination of GIS activities improves in the federal sector, bilateral agreements between agencies to improve the TIGER database will likely evolve into multi-agency agreements, as has already occurred at the state and local levels (see Murakami and Greenleaf 1992).

    The Census Bureau also is investigating possible mechanisms for the electronic interchange of updated geographic information with state, local, private, and academic organizations. The current preference of the Census Bureau is to coordinate these efforts and control quality at the state level rather than having to deal with conflicting data and different file formats from several thousand local governments, private agencies, universities, and other sources. Experience indicates, however, that this will not always be possible.

    Role of the FGDC in Data Sharing

    Increased GIS use by federal agencies as well as state and local agencies has led to renewed efforts to coordinate development, sharing, and dissemination of spatial data, primarily through the Federal Geographic Data Committee (FGDC). The FGDC, formed in late 1990 at the direction of the OMB in its Circular A-16 (OMB 1990), includes representatives of fourteen departments and independent agencies but has no direct authority, responsibility, or resources. Participation is voluntary, with decisions based on consensual agreement among its members. Given the current limits on availability of fiscal resources, several agencies have agreed to pursue cooperation in accelerating the 1:12,000-scale digital orthophoto program and the 1:24,000-scale digital quadrangle program. The Census Bureau is working on individual Memoranda of Understanding (MOU) with other federal agencies in the spirit of the FGDC and has agreed to cooperate with the USGS in devising a still more powerful data structure.

    In the long run, the FGDC may provide the vehicle necessary to transform institutional relationships within the federal government as well as with state and local governments, the private sector, and the academic community. The FGDC is making an increased effort to involve the non-federal community in its coordination work. Although the goals are lofty and the potential long-term benefits extraordinary, effective leadership at the highest levels and a concomitant commitment to the development of compatible standards will be necessary. In the absence of these developments, only significant short-term and real cost-saving benefits gained from data sharing by particular agencies will move the process forward toward a national digital spatial database.

    Significantly, in July 1992 the Census Bureau and the USGS signed an amendment to the original 1981 Memorandum of Understanding that commits both agencies to merging the current DLG and TIGER databases, including information resulting from partnerships with other agencies. The development of a shared database that combines the essential geographic information needed by both agencies to carry out their respective institutional mandates will have a profound effect in further stimulating the development of a national spatial data infrastructure in the United States.

    Intercensal Data-Sharing Projects, Post-1990

    Current data-sharing experiences at the Census Bureau have been exploratory, and the actual mechanisms and standards for digital data interchange are still in the process of being developed.  The Census Bureau is engaged in a number of activities to help promote digital data sharing during the 1990s.  These activities include conferences, participation in the FGDC initiative, MOUs with other federal, state, and local agencies, pilot projects, and the planning and imminent release of the prototype version of the TIGER/SDTS (Spatial Data Transfer Standard) file.

    Based on these forums and activities, the Census Bureau has begun to receive initial feedback on the non-technical impediments to and incentives for digital spatial data interchange.  The Census Bureau has provided its digital geographic and statistical data sets to the public at the cost of dissemination and as a public resource (OMB 1992).  Other public and private agencies, however, have different perspectives and regulations pertaining to their own data sets and on the updates they may perform.  Profit is a major concern of private companies, and public agencies also are looking to their products as a source of revenue.

    States and local agencies consistently have reported one or more of the following problems in trying to coordinate a GIS:

    •    Agencies wanting proprietary control of internal data

    •    Lack of resources in one department or institution affecting data requirements of another

    •    Archaic systems

    •    Managers and commissioner-level officials who know, or care, little about GIS

    •    Staff turnover

    •    Lack of commitment

    Once a state or local GIS is operational, the lack of overt incentives to expend the additional time and expense required to feed local updates into the TIGER/Line or SDTS formats for interchange become more apparent.  Ensuring the currency, accuracy, and quality of the TIGER database is an integral part of ensuring the accuracy and quality of the associated census data, which are used for reapportionment, redistricting, the distribution of federal funds, and innumerable planning and development programs – but this may be a long-term and nebulous consideration for some agencies.  The lack of a clearly defined formal process for data interchange by the Census Bureau could provide an even greater impediment to institutions willing to share data.

    The existence of multiple geographic data file formats also have inhibited the interchange of data.  Future geographic data files at the Census Bureau will be released in accordance with a recent Federal Information Processing Standard (FIPS) – the SDTS.  Adoption of the SDTS involved cooperation of federal, state, and local officials, the academy community, and private sector over an extended period of time.  The Census Bureau was an active participant in the development of this new federal standard for data exchange and, to that end, released its first prototype TIGER/SDTS file (Davis et al. 1992).  However, the effect of this rather complex format on data interchange is not yet clear.

    Each data-sharing agreement brings forth new possibilities, new arrangements between agencies, and the potential for new products.  Working with a variety of agencies and soliciting recommendations for improving TIGER, Census Bureau staff have noted similarities among the interests of many agencies.  For instance, conversations with the USPS and the U.S. Department of Transportation have revealed similar interests in enhancing attributes for streets (e.g., turn and directional restrictions).  In many cases, the Census Bureau would be able to use the enhancements needed by other agencies for improving the quality and cost-effectiveness of its own internal operations (e.g., routing of enumerators).

    Proposed Census/USPS cooperative program.  The USPS and the Census Bureau have been working together for more than thirty years in the delivery and return of questionnaires for the decennial, agriculture, and the economic censuses and surveys.  The increasing use of mail-out/mail-back procedures throughout the nation has made the USPS an indispensable partner in the Census Bureau’s data-collection activities.  The Census Bureau traditionally has paid the USPS to verify the completeness and accuracy of its decennial census address list, which was purchased from private vendors and enhanced through in-house programs, prior to the mailout of questionnaires.  The Census Bureau also worked with the USPS on the development of computer algorithms to match the ZIP+4 files to GBF/DIME-File records during the 1980s.  ZIP+4 files, also known as the Address Management System (AMS) Files, contain potential address ranges for all areas where the USPS delivers mail.

    In an effort to enhance this cooperation to the benefit of both agencies, the Census Bureau proposed a formal Memorandum of Understanding (MOU) with the USPS similar to the one it had with USGS in the 1980s. In 1990, the Census Bureau and the USPS, with the participation of the USGS, began cooperating on a pilot project to provide a better geographic database for all three agencies.  If signed, this MOU will have broad implications, not only for these three agencies, but for the GIS community as a whole during the 1990s.

    The Census Bureau’s proposal envisions a four-year file update/enhancement plan (fiscal years 1994-1997) and subsequent ongoing cooperative efforts to update a Post/TIGER database.  As with the earlier USGS agreement, the USPS/Census Bureau MOU would formalize a seemingly well-suited alliance between two agencies.  Cooperative database-building activities could reduce duplication of efforts, thereby reducing overall costs, as well as improve the geographic and attribute accuracy of the information available to each agency.

    The Census Bureau’s objectives for the proposed joint program during the intercensal years are (1) to obtain updated information on the location of streets with their names, address ranges, and ZIP codes as well as the location of group quarters, office building or other locations of economic activity, and (2) to improve the error-prone decennial census address lists development operations.  According to a recent GAO report (1992), enumerator follow-up to vacant and nonexistent units alone resulted in an added expenditure of approximately $317 million to the 1990 census operation.   Accomplishing the above objectives will enable the Census Bureau to reduce its critical dependence on a large, temporary clerical workforce before and during each decennial census, thereby reducing costs, and to improve the overall quality and consistency of decennial census data products.

    In the overall proposal, the joint venture envisions updating the TIGER database to permit automated analysis of carrier routes and the production of carrier route maps for use by the USPS.  In the pilot study, the effort to improve and maintain the positional accuracy and completeness of the TIGER database involved the use of Global Positioning System (GPS) technology with receivers mounted on USPS-supplied vehicles.  In order to improve and update the geocoding capability of the TIGER system, the pilot study also updated the address ranges in the TIGER database and added ZIP+4 Codes and other USPS information.  The joint venture envisioned would extend similar geocoding improvements to all parts of the United States with city-style address systems.  The Census Bureau would provide the USPS with its technical and geographic expertise.

    Potential impediments.  Although this data-sharing scenario appears to satisfy the needs of both agencies, there are a number of organizational, behavioral, and institutional impediments that will need to be overcome.  Some of these impediments are specific to these two agencies while other are generic to any data-sharing milieu.  One specific impediment is that the USPS is not part of the FGDC.  The USPS also is a quasi-federal agency, which means that it must justify its participation in an agreement on a benefit/cost basis including expected revenue or savings from potential products.  There also are questions about what information will be shared and what will be the property of each organization.

    A more general institutional impediment is the difficult of building a single database to serve the needs of different agencies.  Federal agencies have worked independently of each other for a long period of time collecting and structuring their data according to geographic units based on their own unique criteria and naming conventions.  Data sharing presupposes a strong, long-term, funded commitment to reconcile what really constitutes different versions of the same reality.  In order to reach agreement, a shared database initially may involve compromises that could make it less effective than two separate databases.  Each agency has its own self-interest and mission that must be met first.  Short-term objectives may become more pronounced and inhibit progress.  The need to understand each other’s terminology, organizational structure, and needs represents another potential impediment.

    Another important issue, not only for the Census Bureau but for all potential data partners, is the potentially differing perception of the benefits from data sharing.  One agency may believe that it is giving up more than the other agency and is bearing an unfair burden, causing a negative effect on data-sharing plans.  Some groups within each agency may either be opposed to or less than committed to the idea of data sharing.  While this issue was always in the background during the joint Census Bureau/USGS Cooperative Mapping Project, it never came to the forefront as a major issue.

    Another potentially critical impediment common to bureaucracies is the inertia effect; that is, it is easier to stick with the tried and reasonably true methods than to try something new.  Change can be intimidating and can upset a delicate balance of power in an organization.

    OTHER ONGOING DATA-SHARING ACTIVITIES

    In a broad sense, the Census Bureau traditionally has been in the business of sharing geographic data and has a long history of partnerships with state and local governments.  The Census Bureau receives updated governmental unit boundaries from local officials on a periodic basis through its Boundary and Annexation Survey.  The Census Bureau also works with local Census Statistical Area Committees, composed of representatives of the public, private, and academic communities, in delineating the boundaries of census statistical areas such as census tracts, block groups, and census-designated places.

    The Census Bureau also has worked closely with state election officials to provide the information they need for redistricting and reapportionment; with the U.S. Department of Education to incorporate the boundaries of school districts as a means to produce data for school districts; and with metropolitan planning organizations to improve the quality of the Census Bureau’s address reference files, which improves the quality of the usefulness of the census journey-to-work and place-of-work data, and to define traffic analysis zones in terms of census blocks to facilitate the tabulation of decennial census data for those areas.  The Census Bureau has built its massive geographic database primarily from source materials acquired from state and local agencies.  In a new program based on 1990 census data, data users may independently aggregate census blocks to define their own statistical areas and receive maps and data profiles of these user-defined areas from the Census Bureau on a cost-reimbursable basis.

    In addition, the Census Bureau maintains and is constantly improving its huge, ongoing institutional data-sharing apparatus.  Each of the Census Bureau’s twelve regional offices supports information services and geographic programs that coordinate activities with state data centers and their affiliates throughout the United States.  The Census Bureau’s Data User Services Division combines educational functions (e.g., ongoing workshops on TIGER, census maps, and data products) with its data distribution functions.  The Census Bureau participates in the kindergarten through twelfth grade (K-12) geographic literacy campaign in the United States a means to address the important issues of access to new information technologies.  Public access issues (Emergency Planning and Community Right-to-Know Act 1986) also have provided the impetus for an ongoing cooperative project with the EPA and the National Oceanic and Atmospheric Administration (NOAA) that supports the development of public domain software that links and displays environmental, socioeconomic, and demographic data using an extract of the TIGER database.

    From a more global perspective, the Census Bureau shares its technological and statistical know-how with a number of participating countries through its in-house and overseas training programs.  The Census Bureau also is cooperating with Statistics Canada (Haythornthwaite 1992) and pursuing talks with Mexico’s statistical agency, Instituto Nacional de Estadistica, Geografia e Informatica, to create a North American Common Borders Database.  In summary, the Census Bureau maintains a huge ongoing apparatus that supports and complements its current efforts at spatial data interchange.

    CONCLUSIONS

    As the Census Bureau prepares for the 2000 census, change, once again, appears imminent.  According to a recent GAO report (1992,4), “the current approach to taking the census appears to have exhausted its potential for counting the population cost-effectively.”  Similar statements were made in reference to the Census Bureau’s geographic support program following the 1980 census (Tomasi 1990).  These statements have recurred with periodic frequency in the recent history of census-taking.  In large part, the innovations that followed were a response to intense public scrutiny, a result of a process that has significant and far-reaching political (reapportionment and redistricting) and economic (distribution of government funds) consequences.  Over the past fifty years, the Census Bureau has met not only the challenges brought about by massive social, demographic, and economic change, but has provided effective leadership in applying and diffusing a number of new technologies to both the governmental and non-governmental sectors.

    The application and use of new technologies on a vast scale by public organizations are reshaping the internal organization and relationships within the public sector as well as among the public and private sectors and the academic and research communities.  The dominant values of narrow, functionally separate governmental agencies and departments are increasingly being replaced by a system of greater complexity and interrelatedness and a growing trend toward public and private sector cooperation.  The Census Bureau’s TIGER system is an important example of this phenomenon and may be a primary motivator for such changes.

    The Census Bureau’s geographic and statistical products – inexpensive and ubiquitous spatial and attribute raw material – have helped transform GIS from a highly technical field dominated by large agencies, private firms, and universities, to one that is becoming increasingly accessible to many data users.  Advances in our technological infrastructure thus far have been the primary factor enabling institutions to develop and share digital geographic data.  Personal computers, workstations, CD-ROMS, and databases available for automation were relatively nonexistent until the 1980s.  The incipient use of new telecommunication technologies, such as the Internet, may have an equally profound effect on data sharing and online services in the latter part of this decade.

    As computer hardware and software continue to become less expensive and more powerful, the vast potential of GIS will depend increasingly on the behavioral, organization, and institutional issues acting as impediments and incentives to the sharing of geographic data.  The integration of various multi-media technologies and the growing capability to link a wide variety of public and private databases also raise a number of privacy issues.  Deriving the full benefits of GIS and related information systems will depend, to a significant degree, on how society approaches and resolves these issues (Onsrud 1992).

    Based on past experience, it will require extraordinary leadership, communication and flexibility among agencies to facilitate the process of spatial data interchange.  Data sharing will be most successful when such ventures can be justified by short-term results, verified cost reductions, improved operations, and minimal problems of data ownership.  Data sharing will be enhanced to the degree that these ventures can be built around joint development projects such as the Census Bureau/USPS and the Census Bureau/USGS experiences in the 1990s.  Awareness of the need for such coordination is growing and is best reflected in the increasing number of statewide GIS committees and partnerships between the federal and state communities.

    Geographic databases have been built thus far to support the mandates of single institutions or parts of an institution.  All who collect and manage data for activities related to their own responsibilities will need to understand and appreciate the value of those data to others and to collect and structure their data accordingly.  In order to take full advantage of the opportunities offered to these new technologies, business, government, and academic will need to develop, support, and fund data exchange on a systematic and ongoing basis as well as promote accessibility of GIS capabilities to all sectors of our society.

     

    REFERENCES

    Anderson, M.J. 1988. The American census: a social history. New Haven: Yale University Press.

    Boudriault, G. 1987. Topology in the TIGER file. Eighth International Symposium on Computer-Assisted Cartography, Proceedings. Baltimore, Maryland, 258-263.

    Broome, F.R. and D.B. Meixler. 1990. The TIGER database structure. Cartography and Geographic Information Systems 17, 1:39-47.

    Carbaugh, L.W. and R.W. Marx. 1990. The TIGER system: a Census Bureau innovation serving data analysts. Government Information Quarterly 7, 3:285-306.

    Cooke, D. 1995. Sharing street centerline spatial databases. In H.J. Onsrud and G. Rushton, eds., Sharing Geographic Information. New Brunswick, NJ: Center for Urban Policy Research, Rutgers University.

    Corbett, J.P. 1979. Topological principles in cartography. Technical Paper 48. U.S. Bureau of Census, Washington, D.C.

    Davis, B.A., J.R. George, and R. W. Marx. 1992. TIGER/SDTS: standardizing an innovation. Cartography and Geographic Information Systems 19, 5:321-327.

    Emergency Planning and Community Right-To-Know Act: Title 3 of the Superfund Amendments and Reauthorization Act of 1986. PL 99-499, 17 October 1986. United States Statuates at Large 100. pp. 1728-1758.

    Federal Geographic Data Committee. 1992. Multi-agency initiative to meet high priority requirements for base cartographic data. FGDC Subcommittee of Base Cartographic Data. Washington, D.C.

    Government Accounting Office. 1991. Geographic Information Systems: information on federal use and coordination. IMTEC 91-72-FS. Washington, D.C.

    ________. 1992. Decennial Census: 1990 results show need for fundamental reform. GAO/GGD-92-94. Washington, D.C.

    Haythornwaite, T. 1992. Development of the United States-Canada Common Border Database. The Operational Geographer 10, 1:28-30.

    Kinnear, C. 1987. The TIGER Structure. Eighth International Symposium on Computer-Assisted Cartography, Proceedings. Baltimore, Maryland, 249-257.

    Marx, R.W. 1986. The TIGER System: automating the geographic structure of the United States census. Government Publications Review 13, 181-201.

    ________. 1992. Building the National Spatial Data Infrastructure: the data integrity challenge. Paper presented at the Regional Surveying Engineering Conference, Hartford, Connecticut.

    McKenzie, B.Y., and R.A. LaMacchia. 1987. The U.S. Geological Survey-U.S. Bureau of Census Cooperative Digital Mapping Project: a unique success story. Paper presented at American Congress on Surveying and Mapping meeting, Reno, Nevada. Fall.

    Murakami, E., and K. Greenleaf. 1992. Multi-agency TIGER file updating. URISA Proceedings 2:25-35.

    Office of Management and Budget. 1990. Coordination of surveying, mapping, and related spatial data activities. OMB Circular A-16 (Revised). Washington, D.C.

    _______. 1992. Management of federal information resources. OMB Circular A-130. Washington, D.C.

    Onsrud, H. 1992. Privacy and spatial databases. Technical Program Abstracts., 27th International Geographical Congress, Washington, D.C., 480-481.

    Rhind, D.W. 1991. Counting the people: the role of GIS. In D.J. Maguire, M.F. Goodchild, and D.W. Rhind, eds., Geographic information systems: principles and applications. Longman Scientific and Technical, Essex, 2:127-137.

    Silver, J. 1977. The GBF/DIME system: development, design and use. Paper presented at 1977 Joint Annual Meeting of the American Society of Photogrammetry and the American Congress on Surveying and Mapping. U.S. Government Printing Office, 1977-240-869/1102.

    Sobel, J. 1978. GBF/DIME system – development and reference source problems. Applied Geography Conference, SUNY – University Center at Binghamton, 1:112:121.

    _______. 1986. Principal components of the Census Bureau’s TIGER file. Research in contemporary and applied geography: a discussion series. SUNY at Binghamton, 10, 3:1-17.

    Tomasi, S.G. 1990. Why the nation needs a TIGER system. Cartography and Geographic Information Systems 17, 1:21-26.

    Trainor, T.F. 1990. Fully automated cartography: a major transition at the Census Bureau. Cartography and Geographic Information Systems 17, 1:27-28.

    U.S. Bureau of Census. 1973. Census Use Study. International DIME Colloquium. Confernce Proceedings, Washington, D.C., August 27-29, 1972.

    White, M. 1984. Technical requirements and standards for a multipurpose geographic data system. The American Cartographer 11, 1:15-26.

  • 3D Visualization Software and…Introducing a New Contributing Author

    A couple of weeks ago, I dedicated a column to discussing the emergence of 3D geospatial data. This week, I was navigating around the U.S. Army Geospatial Center’s (AGC) website, which was formerly known as the Engineer Research and Development Center’s Topographic Engineering Center (TEC). As of October 1, 2009, AGC is operating as a Major Subordinate Command Center under the U.S. Army Corps. of Engineers. Anyway, I was navigating the website and stumbled upon the most comprehensive list of commercial 3D visualization software programs I’ve ever seen.

    I’ve been involved with 3D visualization software (mostly on the data side) since about 2001. In my experience, it has always been a labor intensive process to develop high quality 3D visualizations. Still images are easier than animations, but still a chore to do if you desire high quality rendering in the images.

    Following are two images. One was rendered using medium quality resolution/textures vs. high quality resolution/textures:

    It’s a big step in time, both development time and rendering time, to upgrade from medium quality to high quality renderings. Most 3D visualization software programs work at the medium level or lower. This is primarily because they produce 3D visualizations that are “good enough” for the task at hand.

    3D visualizations have become much more common as compared to nearly a decade ago when I first started experimenting with them. Software has become more powerful and easier to use. Computing power has become exponentially more powerful. One of today’s computers can render as fast as small “server farm” back in the year 2000.

    Back to the AGC

    While surfing the AGC website, I found the most comprehensive listing of commercial 3D visualization software as I’ve seen anywhere. You can view it here. Be aware that some of the links might be obsolete, but certainly all of the 3D visualization softwares I’ve experienced are included in the listing.

    Introducing our new Contributing Author

    If you recall in my column a couple of weeks ago, I presented the many initiatives I plan for Geospatial Solutions in 2010. One of the initiatives was to enlist a number of industry specialists who could offer a different perspective from a very specific part of the geospatial industry. Well, I’m pleased to announce that Craig Greenwald is joining our team as our Contributing Author for Mobile GIS.

    Although I’ll ask him to formally introduce himself in his first contribution, I’ve known Craig for well over ten years. In the mid-90’s, he and I worked together at the same company…his first job out of graduate school at Oregon State University. Craig then spent a number of years at ESRI on the ArcPad Team, interrupted by a brief stint at Bradshaw Consulting. Many of you may have run into Craig at the ESRI User Conference where he conducted numerous basic and advanced ArcPad workshops and briefings. Craig is now a principal at the GIS firm GeoMobile Innovations.

    I’ll be publishing Craig’s first contribution in just a few weeks. I’ve asked him to provide us with a look forward into 2010 with respect to Mobile GIS. Will there be any disruptive technologies or will it just be the status quo? What kind of new productivity tools can we expect to see? What will be the trends in the industry?

    I look forward to his answers and I hope you do too.

    See you next week.

  • GPS Constellation Management: Playing Not to Lose

    In sports, there is a phenomenon that sometimes occurs when a team is leading towards the end of a game. It’s called “playing not to lose”.

    For example, there’s five minutes left in a basketball game and a team is leading by ten points. The leading team wants to run the clock down as much as possible and still maintain their lead. There are two basic strategies the leading team can take. One is to continue being aggressive and using the strategy that put them in a winning position to begin with. The other strategy is to try to “play it safe” until the time clock expires. The problem with the latter strategy is that the other team can sense the change in mentality and feed off of it. It’s called “playing not to lose” instead of “playing to win”. I’ve seen it happen over and over again in team sports and in business. Once an organization has achieved a level of success, they lose the edge that brought them their success.

    The reason you are seeing high HDOP warnings from the NAVCEN and GPS “brownouts” during the day when RTK (GPS-only) isn’t working is because the GPS satellite constellation is sub-optimal. The current design of the GPS constellation is not focused on “playing to win”, but rather “playing not to lose”.

    Even the original GPS Program Manager, Dr. Brad Parkinson, has voiced his concern about GPS brownouts and discussed possible solutions. You can read one of his presentations here. In 2006, noted GNSS consultant John W. Lavrakas published a GPS World article entitled Managing the GPS Constellation for Today’s Needs discussing the disparity between the professional user community needs and GPS constellation management.

    Today, there are 28 operational satellites. There were 30, but PRN08 is offline for maintenance and PRN24 was placed in active reserve after an “unusual failure”. The 31st one, PRN01/SVN49, never has been declared operational since its launch last March due to the issues discussed here before. The current GPS ground control infrastructure can only handle 30 or 31 satellites.

    Given these limitations, GPS looks grim for the GPS-only RTK user, right?

    Not necessarily.

    The GPS constellation is optimized for 24 satellites. When there are more than 24 satellites in orbit, like there has been for many years, the extras are not positioned to benefit the users but rather to be in a position to replace satellite failures. They are sometimes referred to as “paired orbits”. Simply put, the active spares are orbiting very near other satellites that are most likely to fail. This does very little for the user community.

    The current discussion is not whether to launch more satellites, but rather how to reconfigure the satellites that are in orbit. Launching more satellites is a complicated issue. It’s not just an US Air Force (the GPS stewards) technical issue, but a political one because it’s expensive (~$150M per GPS satellite launch). That leaves the Air Force with the option of adjusting the GPS constellation to benefit the user community. Doing this is not completely void of political implications I’m sure, but certainly not near the risk of launching a new satellite and certainly a better bang for your buck to the user community.

    For many years in the GPS scientific community, there have been open discussions in the past of GPS constellations designed for 27 or 30 satellites. The good news is that this is an active discussion within the US Air Force today. It’s quite an important discussion because GPS-only RTK users are increasingly being shut down during the day due to the lack of GPS satellite signals and/or high PDOP. Even a constellation designed for 27 satellites would be a significant gain for GPS-only RTK users.

    During my webinar a month ago, I submitted to the audience the following question:

    “Do you or your crews experience GPS “brownouts” where you have to wait for the GPS constellation to change before you can continue using your GPS system?”

     

    The following results speak for themselves:

     

    Email me your experiences so I can continue to raise awareness of the impact the current GPS constellation is having on GPS-only RTK users. Tell me about your productivity loses, extra mission planning and other time spent dealing with the GPS “brown outs”.

    I’m doing my best to make the Air Force aware of that the current constellation is causing GPS-only RTK users a significant loss in productivity. I have a feeling that the Air Force looks at the millions of consumer GPS users who are happy with their Garmins, TomToms, Magellans, etc. because those folks are able to navigate from Point A to Point B with few difficulties given the current constellation. What the Air Force doesn’t realize are that the GPS demands from the professional user community are much higher. We are the infrastructure people. Without our accurate measurements, the consumer GPS community wouldn’t enjoy the benefits they have.

    RTK users need at least six satellites above 12 degrees and a PDOP below 3.0 for a robust solution. Furthermore, we have to deal with obstructions such as trees, buildings and terrain that will take out, on average, a couple of those. I think the Air Force plugs in a five degree elevation mask back in the office, looks at the sat visibility graph and says “hey, what are these guys complaining about?” The reality is that satellite signals low on the horizon don’t work as well because the data is noisier and many times rejected by the receiver. Secondly, we don’t work in parking lots where we have an unobstructed view of the horizon. We have to deal with trees, buildings and terrain that block satellite signals.

    And the answer is…

    At this point, there is only one solution for RTK users who need better productivity…GLONASS. As much as the Russians have taken a beating in the past for having an unreliable constellation, they hold the key for RTK productivity at this point as the GPS constellation continues to deliver “brownouts” that hamper productivity. It could turn out to be a boon for RTK receiver manufacturers. Although a few include GLONASS as a standard, most RTK receiver manufacturers charge an upgrade fee of several thousand dollars to utilize GLONASS. Even worse for some RTK users, their receiver isn’t upgradeable to utilize GLONASS so they would need to purchase a new receiver(s).

    On a final note, I just spoke to a user in the field who was using a GPS/GLONASS RTK receiver. I asked him to recite to me how many GPS and GLONASS satellites he was tracking. I suppose I shouldn’t be surprised, but it did saddened me a bit. He was tracking more GLONASS satellites (6) than GPS satellites (5). Sigh…

     

  • Geospatial Data Accuracy – Better and Better

    Circa. 1995. I walked into the GIS office of a major forest products company in northern Arkansas (or was it northern Louisiana…not sure). At the time, I was a product manager for a GPS company and field testing one of our newer GPS mapping hand-held products.

    We decided to go out and map the perimeter of a timber tract they owned to compare the area (acres) that the GPS calculated vs. what was in their GIS. This was nothing new as I’d done it many times for other companies. We went to the tract (adjacent to a road) and walked the boundary (~40 acres). Afterwards, we returned to their office and I post-processed the GPS data.

    I forget what the final area calculation was, but it was believable and the company didn’t challenge the result. Also, the shape of the polygon seemed reasonable. However, when the GIS manager inserted the GPS data into his GIS, it was offset a significant amount. I forget exactly, but something on the order of 50-100 feet. I immediately began considering if my data was the problem, but concluded the chance was low. For GPS post-processing, I’d tied into a local US Forest Service GPS base station so my GPS data was referenced to NAD83/86 (if I recall correctly). In the end, we agreed that my data was most likely positioned correctly.

    “So what?”, he said, “Do you think I’m going to adjust my entire GIS because it doesn’t agree with your GPS?” (I’m paraphrasing based on my recollection). I understood that I had won the battle, but lost the war. It didn’t matter that I was right, at least at that moment in time. However, he did agree with me that eventually he was going to have to reconcile the difference because GPS was destined to be the technology that defined the national spatial framework.

    I had many more experiences similar to the above during the mid-90’s. People would swear by the accuracy of USGS 1:24,000 quad sheets because that’s what they were used to. If the GPS data didn’t agree with the quad sheet, they’d dismiss the accuracy of GPS because it didn’t fit. This was particular true with utility companies too, that were some of the early adopters of CAD for mapping.

    Fifteen years later, this problem is not going away. The accuracy of Geospatial data continues to get better and better. Think back fifteen years and ask yourself about the quality/availability/price of orthophotography back then. I remember we were ecstatic to have access to free 1-meter, black/white DOQQs. Today, I can easily find 1’ pixel resolution orthophotography, commonly find 6” and occasionally run into 3” pixel resolution orthophotos free of charge. This allows one to digitize manholes and other infrastructure without leaving the seat at your GIS workstation.

    During the same period, the cost of accurate GPS measurements has reduced considerably. Whereas fifteen years ago, achieving sub-meter accuracy with a $12,000 mapping receiver was on the bleeding edge of technology. Today, a $2,000 mapping receiver can give you sub-meter results and a $6,000 receiver can achieve sub-foot accuracy. Looking way forward, the cost and availability of GPS accuracy is going to change significantly in the next 10 years. Obtaining one foot accuracy will be achievable with a very inexpensive GPS receiver.

    We all know that data drives a GIS. The better quality data we have, the more accurately and precisely and completely the GIS can answer our queries. Along these lines, I think it’s worth mentioning again the outcome of the litigation in California involving Santa Clara County and the ownership of GIS data.

    Santa Clara County GIS lawsuit

    Santa Clara County (California) was charging significant fees (potentially several hundred thousand dollars) to organizations who wanted to utilitize its full suite of GIS data including orthophotography, parcel, planning, streets, boundary, etc. A lawsuit was filed in 2006 by the First Amendment Coalition arguing that the GIS data should be released under the California Public Records Act. Santa Clara County argued that the GIS data was sensitive enough to be excluded due to homeland security issues (eg. making known the locations of critical infrastructure such as utilities). Santa Clara County lost the argument and was ordered by the court to hand over the GIS data. The 6th District Court of Appeal gave the final word last February.

    The outcome of the court case establishes a significant precedent in the geospatial industry. For as long as I can remember, this issue has been solidly ambiguous among state and local governments. One entity would email (or make available via FTP) GIS data at a moment’s notice. Another entity would have you sign away your first-born child. Even another would not entertain the thought of releasing “our data” to anyone. I think the attorney for Santa Clara County was accurate in stating “It was one of those cases that needed to be tried and for which we needed guidance from the court”. Normally, I have an anti-litigious attitude, but I’m happy to see a precedent has been established and publicized.

    Go on…be a TIGER

    After last week’s column about Google’s step forward in using their own base map for Google Maps/Earth in the US, I was admonished by a reader, and rightfully so, in not mentioning the value of Census data as an important part of the history of base map evolution in the US.

    Jon Sperling, Ph.D., GISP wrote:

    “It is quite disconcerting, from an historical and current perspective, that your article made no mention of the “pre-internet” Census TIGER database, the first topologically integrated national digital street centerline for the US or even the newly updated and positionally accurate TIGER files (with an associated but confidential file of GPS address points collected for every housing unit in the Nation). These files, newly updated for the 2010 Census, are still a major source for accurate and easily accessible public domain street level data for every community in the US, including Puerto Rico, the Virgin Islands, and other territories. More importantly, it was the innovation that spurred the GIS revolution across government, private industry, and academia by enabling every local agency, entity and person in the United States to build their own geographic information system by combining census data with TIGER. Prior to this development, the Census was also a leader in the development of the GBF/DIME Files which enabled address geocoding, a capability that led to the later success of Mapquest, Google, and others. Like the development of the internet by DARPA and the Global Positioning System also by the federal government, the widespread development of intelligent national street level mapping was also led by the government.  GDT/TeleAtlas began as a company that offered “enhanced” TIGER files and Navteq often used TIGER for the more rural areas. Not only has the Census pioneered but it remains a key catalyst and building block for delivering a cost-effective and truly integrated national spatial data infrastructure.”

    Attached is an article I wrote back in 1992 on the history/development of TIGER as well as a 2002 proposal for creating a shared national road network (geometry and basic attributes such as address range to enable consistent and shareable geocoding across
    domains). OpenStreetMap is a nice expression of a way to move forward.”

    A copy of Jon Sperling’s 2002 proposal can be read here (scroll down to Page 16).

    Thanks and see you next week.

  • “What Can GLONASS, GPS L2C, and GPS L5 Do for You?” Webinar Q&A Follow-up

    I hope you’ve enjoyed and benefited from the webinar series as much as I have. I think that given the limited travel budgets in this economy, they are one of the most powerful tools for collaborating. I consider it collaboration because I learn also. Your questions and comments make me think about topics I might not normally consider.

    I also have to give credit to our marketing folks in spreading the word about our webinars. I’ve spoken to others who conduct webinars and I don’t hear of anyone attract the attendance numbers that ours are do (if I may be so bold as to toot our horn). I didn’t see the final attendance numbers on the last webinar, but I think we had over 600 registered. By early next year, I think the number should reach 1,000 for each of the survey/construction/GIS webinars. Hopefully, in the next few months we’ll also start up a webinar series for GeoSpatial Solutions, which I started working on earlier this month.

    As I’ve been accustomed to doing, this newsletter addresses the questions you submitted during the Sept. 15 webinar entitled “What Can GLONASS, GPS L2C, and GPS L5 Do for You?”.

    There were some great questions during the webinar, and a lot of them. There were so many, in fact, that I’m going to break them up into a couple of different newsletter issues. Also, I need to update you on my trip to ION GNSS a couple of weeks ago. I might mix up the next newsletter with more Q&A as well as the ION GNSS update.

    Lastly, don’t feel the need to wait until the next webinar to send me your comments/questions. I can guarantee you that many others have the same questions that you do.


    Question #1: Recent Statement: GLONASS satellite signals are not used nearly as much as the GPS satellite signals (domestically) — is this true? If so, what is the percentage of GPS usage vs. GLONASS in the states?

    Gakstatter: The general statement is true. GLONASS is used predominately in high-precision RTK (real-time kinematic) applications that require centimeter-level accuracy. Even in that segment, I think only a minority of the existing survey receivers utilize GLONASS. But that’s considering legacy receivers that have been in operation for many years. You should remember that GLONASS only became a widely adopted technology in the last few years and it’s still an option on most survey receivers unless you purchase the top-of-the-line model. As recent as five years ago, several mainstream manufacturers still didn’t support GLONASS.

    Also, consider that the popular entry-level GPS L1 survey receivers such as the Magellan ProMark 3 line don’t support GLONASS at all.

    On the GIS front, GLONASS is just starting to make its way into mapping-grade receivers such as the Trimble GeoXH and Topcon GMS-2 Pro. But realize that correctors for GLONASS aren’t supported by real-time correction systems such as WAAS/EGNOS/MSAS or DGPS/NDGPS or OmniSTAR. GLONASS isn’t supported by OPUS or other online post-processing services either.

    But make no mistake about it, GLONASS usage is increasing substantially. This is mainly due to GPS “brownout” periods where there aren’t enough GPS satellites throughout the day to be productive. It’s simply too expensive for work crews to sit idle while waiting for the GPS constellation to improve during parts of the day.

    Lastly, next year the Russians are introducing a significant change with their new generation GLONASS-K satellites. They are going to begin supporting CDMA (vs. FDMA they support now). You can think of this like VHS vs. Beta VCRs of 20 years ago. Today, a GPS/GLONASS receiver is basically two receivers in one box, just like a VCR player that would support VHS and Beta formats. This makes a GPS/GLONASS receiver difficult to design, power hungry and generally inefficient. This is the reason you do not find GPS/GLONASS receivers in the consumer GPS market and rarely in GIS/GPS receivers. However, this is going to begin changing next year as Russia will begin to support CDMA signal structure. This will be the start of a new era in simplifying the design of GPS/GLONASS receivers. I believe it will mark the beginning of the wide-spread adoption of GLONASS. However, this is not an overnight process. It will be many, many years before enough operational GLONASS-K satellites are in orbit to support a CDMA GPS/GLONASS receiver. Of course, it’s also critical that the Russian space program stay focused (politically and financially) in order to achieve this.

    Question #2: Will current GLONASS receivers work with the new (GLONASS) “K” satellites?

    Gakstatter: It is my understanding that the GLONASS-K satellite will support legacy signals and signal structures. Essentially, they would be broadcasting FDMA and CDMA signals. So, the answer is yes. I will report back to you if I hear anything different as this is a critical issue given the large number of GPS/GLONASS receivers in use today.

    Question #3: What does the “k” stand for in RTK?

    Gakstatter: I apologize for “flinging around” acronyms so loosely.

    RTK is an acronym for Real-Time Kinematic. Essentially, it’s a GNSS technology that’s capable of providing centimeter-level positioning in real time while it is moving. RTK utilizes the message carrier (carrier phase) rather than the message itself.

    Question #4: Why will traditional GPS L1/L2 receivers become obsolete after Dec 31, 2020?

    Gakstatter: It’s probably best for you to read the article I wrote about this last year. I also conducted a webinar on the subject you can listen to here.

    It’s important to note that the Dec 31, 2020 date is not a date in which your legacy receiver will stop working. After that date, the US Department of Defense says they won’t guarantee support of semicodeless techniques. In other words, it may work and it may not. The risk is with the user.

    Question #5: What about the accuracy of L2C code? Is it like C/A or P code?

    Gakstatter: L2C provides a pilot carrier for L2. Before L2C, the architects of the original GPS never intended for the civil community to be able to utilize L2. But some very smart engineer/entrepreneurs figured out a way to track the L2 carrier in a “round-about” way via the semicodeless technique mentioned above. With L2C, the semicodeless technique isn’t required any longer so the L2C signal-to-noise (SNR) value is stronger.

    However, there aren’t enough satellites (only 7) in orbit broadcasting L2C at this point to make a significant difference.

    Secondly, L2C has a code similar to C/A code broadcast on L1, but much improved. However, this isn’t being broadcast on L2C at this point due to the ground control segment of GPS not being ready yet. Last indication I received was that it was about two years away from being ready.

    Question #6: If there is a black out in GPS in a GPS/GLONASS receiver, how will it affect? No Black out in GLONASS.

    Gakstatter: I’m assuming you are referring to a total black out of GPS signals. GLONASS isn’t at the point where you can rely on it as a stand-alone system. It lacks a sufficient number of satellites (17) and the quality/reliability of the measurements isn’t nearly as good as GPS.

    Question #7: Are certain frequencies more stable/reliable than others.

    Gakstatter: GPS sign
    als/frequencies (L1 C/A and L2C) are very stable and reliable. They are the most reliable satellite navigation signals in the world. I wouldn’t say that a single GPS signal or frequency is more stable or reliable than another. However, there are a limited number of satellites (seven) that broadcast L2C so it’s not as available as it will be when a full constellation of satellites will be broadcasting L2C (several years from now).

    Many users have GPS/GLONASS receivers. GLONASS, and Russia is very open about this, is not as stable or reliable as GPS yet. While not useful yet as a stand-alone system, GLONASS has proven to be very useful as an augmentation to GPS. This is the reason that GPS/GLONASS receivers have become so popular in recent years in high precision RTK systems.

    Russia has stated that their goal is to match GPS performance in the future.

    Question #8: How will the autonomous accuracy improve with L5 or L2C?

    Gakstatter: Multiple frequencies allow the receiver to directly mitigate the effects of the atmosphere which is the major source error in GPS positioning.

    I’ve heard it been discussed quite widely that decimeter accuracy without correction will be possible with a dual frequency receiver (L1/L5). Furthermore, since both L1 and L5 (and L2C) are open signals (unlike legacy L2), multiple frequency receivers will be widely available and a fraction of the cost of today’s dual frequency receivers.

    Question #9: Will any abilities of the L1/L2 w/ L2C be downgraded when semicodeless is disabled?

    Gakstatter: This is a very good question. The difference I can think of may be the number of satellites broadcasting L2C at that time. If there are still a number of legacy satellites that aren’t broadcasting L2C, one may lose the ability to utilize those satellites.

    Also, it’s important to understand that semicodeless isn’t necessarily going to stop working after December 31, 2020. The DoD merely states that they won’t guarantee it will work after that date. In other words, the DoD might choose to test or utilize a feature that might disrupt semicodeless receivers and they aren’t obligated to inform the civilian community that they are doing so.

    Looking into the future, I’m guessing that receiver manufacturers will create firmware in the receivers (L1 C/A, L2, L2C) that might be capable of detecting this scenario and react accordingly.

    Question #10: If you have a receiver supporting L1/L2/L2c/ glonass where you are tracking 16+ satellites has there been any though on a weighting system for satellites in your solution?

    Gakstatter: Another good question. I’m not sure how the receivers handle this. I will ask a couple of receiver designers I know. I am familiar with some receivers (mapping-grade receivers using code phase) that utilize signals from satellites for which there are no corrections available in order to improve the PDOP. For example, some satellites may not be visible by more than one SBAS reference station and therefore no correction would be issued for that satellite by the SBAS…but the range data from that satellite may still be used to improve the PDOP and position.

    Question #11: Are the ground stations shown in the WAAS slide (SBAS(2) I believe) all operational today?

    Gakstatter: Yes. There are currently 38 WAAS reference stations and all of them are operational today. Twelve were added in the last couple of years (red dots on the map below).

    Four were added in central/eastern Canada, four were added in Alaska and five were added in Mexico. This extended the WAAS service area significantly to the north and south into Canada and Mexico and significantly improved WAAS performance in Alaska.

     

    Question #12: What is the expected accuracy of WAAS in North America and can WAAS be received under canopy (forested) areas?

    Gakstatter: Well, like all questions about GPS accuracy, the answer is “it depends”.

    There are two major factors when considering the accuracy of WAAS.

    The first is the WAAS itself. Looking at the WAAS Performance Report published quarterly by the National Satellite Test Bed, WAAS accuracy throughout North America is well under a meter (horizontal).

    Secondly is the quality of the GPS receiver one is using. A standard consumer-grade GPS receiver using a SiRF (or other) GPS chipset or a GPS-enabled mobile phone is not going to deliver submeter accuracy. Those receivers simply weren’t designed with accuracy as a primary design criterion. On the other hand, there are several GPS receivers available that were designed with professional users in mind that are able to optimize WAAS accuracy and achieve submeter accuracy.

    Operation under tree canopy is even a trickier subject. Among GPS receivers designed for professional users, there is a subset that has been optimized to operate under tree canopy. First, let me be clear that GPS accuracy degrades under tree canopy for all GPS receivers. It’s just a matter of how much it degrades.

    There are two primary issues when operating GPS receivers under tree canopy: accuracy and tracking. Great accuracy is not worth anything if the receiver can’t track satellites. On the other hand, great satellite tracking does little for the professional user if the accuracy is horrible.

    Utilizing WAAS under tree canopy has the additional challenge of the GPS receiver needing to track one of the two WAAS broadcasting satellites (GEOs). Their signal is affected by trees just like GPS satellites. Some companies have developed technology that allows their GPS receivers to temporarily lose track on the WAAS GEO satellite for up to 30 minutes and still maintain WAAS accuracy (or close to it).

    Question #13: Is there a live web page that is good for survey planning, based on GPS satellite positions?

    Gakstatter: There are several GPS satellite planning software packages available as free downloads. Trimble, Topcon, and Leica Geosystems offer them. These require the user to install the software on their computer and update the almanac frequently.

    There is one on-line GPS satellite planning tool from NavCom Tech that’s very convenient for two reasons. First, you don’t have to install any software on your computer. Secondly, it updates the almanac automatically. It has a couple of drawbacks. The major one is that it doesn’t consider GLONASS or SBAS satellites. Secondly, one can’t adjust the elevation mask. Hopefully, NavCom will consider adding those features in the future.

    I wrote an article on this subject recently. You can view it here.

    Thanks and see you next time!