However, I do think that there are more things at stake than just military and homeland security's wishes for data to be controlled. There is also an aspect of protection of the public from accidental misuse of data, and intentional abuse of data. Where harm to the public may be an issue, typically professional licensure, security clearances, or other safeguards come into play.There are many datasets that can fall into this category - for example, there have been several publicized cases involving the misuse of GIS tax parcel mapping to attempt to enforce such things as building setbacks and other ordinances, to the harm and detriment of property owners who may in retrospect have actually turned out to be in compliance with the ordinances - though in some instances only through costly litigation and/or demolition of a structure. In some instances, actual surveyed boundaries were rejected by undereducated GIS staff or other bureaucrats, in favor of digitized-and-rubbersheeted GIS parcel boundaries or misused COGO routines in the hands of people who do not have a solid understanding of surveying. Clearly this is unacceptable misuse of GIS data.
Among other things, I work extensively with GIS data for facilities, which may contain toxic or hazardous materials - certainly agencies which regulate their activities and emergency responders need to have ready access to what is onsite, and what the consequences of a catastropic event at one of these facilities might be on the community - but aside from keeping this data from the hands of would-be agents of terror, certainly that facility's competitors might be able to gain some competetive edge from knowing what this facility is working with. This is generally known as "Confidential Business Information" (CBI). It is a classified data category apart from the usual Governmental Secret or TS/SCI classification hierarchies.
Another area with tremendous potential for misuse is in traffic incident data - Departments of Transportation collect information on reported accidents and incidents, and plot them on roadway maps - the analysis of this can help the DOT in triaging, prioritizing, budgeting and sequencing improvements to the roadway for safety. However, in the wrong hands, this type of data can also lead to litigation - "you knew this was a bad intersection, yet you didn't do anything". Often a DOT is aware of problems for many years, but given budgetary or organizational constraints may be unable to act on them in as timely a fashion as would be liked - and a multimillion-dollar court award or settlement is generally only going to take away money from being able to address the problem properly.
Another example from personal experience comes from some of the Emergency Response work we had done in conjunction with Hurricanes Katrina and Rita. Here, GIS data on accidental spills and contamination relating to the flood event must be captured, however given Agency issues with cost recovery, along with civil litigation and other issues, often this data must be tightly controlled, to avoid misuse which might undermine cleanup and remediation in the future.These are just a handful of examples - many more come to mind. GIS is, at the end of the day, just a tool. The ever-emergent plethora of geospatial data and the ubiquitousness of GIS tools available to the public is certainly wonderful, however data and a tool in the hands of one, either without the adequate domain expertise to use the data properly - leading to unintentional harm; or the intentional abuse by one who wishes to exploit the data toward personal gain at expense of the public, or toward the outright, intentional harm of the public, can be a dangerous thing.
Having a five-year-old in the house, I usually snag any little conference goodies, such as the LizardTech lizards, yo-yos, and other things of interest... And ESRI never fails to please with a few goodies of their own at the User Conferences.
One interesting one is the Mapping for Congress book, published by ESRI press, it was distributed in the conference bags at sign-in. In usual case-study style, they present a gallery of interesting maps that were developed in response to various Congressional inquiries and toward exhibits and policy development by the Library of Congress Congressional Cartography Program. Plenty of great studies toward support of public policy, social justice and other areas to be found in this book.
Another one that I grabbed at the conference was GIS for Homeland Security, which in a vest-pocket size, provides a good high-level overview of various initiatives, Homeland Security Presidential Directives, and other ongoing efforts toward preparedness and response. A great feature of this book is the extensive glossary, which provides over 30 pages of definitions and explanations of the various terms, definitions and TLAs (three-letter acronyms) that one encounters in the Homeland Security arena.
What appears to be a real gem that was handed out in the conference bags is Standards for Success: GIS for Federal Progress and Accountability which as a sort of follow-on to Measuring Up: The Business Case for GIS - it is of particular interest to me, as it presents many federal geospatial projects - and here, the business case needs to begin getting aligned with the OMB GeoLoB, Agency Blueprints, FEA, CPIC and other directions. This book doesn't appear to touch on these directly, but does provide a high-level overview that is spot on, when it comes to streamlining business, collaboration, business logic and decision support, and optimal use of resources.
Going to have to read that one in a bit more detail.
Technorati tags:
analysis, applications, architecture, author, authors, book, books, collaboration, conference, Congress, coordination, decision support, DHS, e-government, ea, emergency response, enterprise architecture, FEA, federal, geo, Geospatial, GIS, homeland security, map, mapping, maps, OMB, policy, service-oriented architecture, SOA, spatial
Just got home from FedUC and see snow on the ground here-
I actually ran out of room in my "little blue book" with all the thoughts and notes from the conference. Very productive, all in all.
I reckon I can probably share a few more of the thoughts going through my mind...
I followed some of the Enterprise Architecture track today... SAIC gave a presentation on DHS and their notional architecture, which was interesting, and applicable to where we are and where we want to be over at EPA. Their model consists of a foundational layer of geospatial data, harvested via ETL, consumed via web services, et cetera - essentially static data. Next, an OLAP layer, of analytical and modeling tools, and finally realtime, streamed and dynamic data. These are to then plug into an enterprise service bus, for consumption by clients which can make use of the BPEL, flows and integration platform provided by ESB.
We currently need an integration framework as well - we have been pursuing a few things in deconstructing and decomposing EnviroMapper into constituent parts, aligned with functional needs, to get them ready for this type of thing, but is ESB and BPEL really ready?
Now, here, Mark Eustis from SAIC is viewing OGC as the world's "virtual service bus". Is this really true? Are OGC services really up to the challenge - and further, ready to be plugged into ESB? Some say no. Time shall tell.
In another Enterprise GIS session, an application was demoed, using ArcGIS Server and IBM WebSphere Process Server as the ESB. ESRI does have ESB in mind for AGS, however here we are still ESRI-proprietary, which doesn't look good for mix-and-match map services in a dynamic application. What about WFS-T and transactional services?
I see I have much to learn about ESB. Seems exciting, but is it really ready for primetime? Our own pursuits of an integration platform are on hold in the meantime... but that doesn't mean we shouldn't still focus on build-out of services and look at the possibilities as things continue to mature...
Technorati tags:
.NET, .NET 2.0, AJAX, applications, ArcGIS, arcgisserver, architecture, BPEL, conference, developer, DHS, dotnet, ea, EDN, emergency response, enterprise architecture, enterprise service bus, ESB, ESRI developer network, federal, FedUC, geo, Geospatial, GIS, homeland security, IBM, internet, interoperability, map, mapping, maps, modeling, service-oriented architecture, SOA, trade shows, web-20, web 2.0, web services, web2.0, Websphere
I have been scrutinizing the current 2007 Department of Homeland Security Authorization Bill (HR 5814)... Of particular interest are several sections under Title V, which mandates information sharing - specifically mentioned are State, Local, Tribal and Regional partners, along with a data fusion concept.
Music to my ears, anyways... I have been preaching sharing and fusion as the only workable longterm solution for over a decade. However, how well it will actually work out is yet to be seen.(a) Establishment- The Secretary shall establish a State, Local, and Tribal Information Fusion Center Initiative to establish partnerships with State, local, tribal, and regional information fusion centers.
(b) Duties- Through the State, Local, Tribal, and Regional Information Fusion Center Initiative, the Secretary shall--
(1) coordinate with the principal official of each State, local, tribal, or regional information fusion center and the official designated as the Homeland Security Advisor of the State;
(2) provide Department operational and intelligence advice and assistance to State, local, tribal, and regional information fusion centers;
(3) support efforts to include State, local, tribal, and regional information fusion centers into efforts to establish an information sharing environment (as defined under section 1016(2) of the Intelligence Reform and Terrorism Prevention Act of 2004 (Public Law 108-458; 118 Stat. 3665));
(4) conduct table-top and live training exercises to regularly assess the capability of individual and regional networks of State, local, tribal, and regional information fusion centers to integrate the efforts of such networks with the efforts of the
Department;
(5) coordinate with other relevant Federal entities engaged in homeland security-related activities;
(6) provide analytic and reporting advice and assistance to State, local, tribal, and regional information fusion centers;
(7) review homeland security information gathered by State, local, tribal, and regional information fusion centers and incorporate relevant information with homeland security information of the Department;
(8) Provide management assistance to State, local, tribal, and regional information fusion centers;
(9) Serve as a point of contact to ensure the dissemination of relevant homeland security information.
(10) facilitate close communication and coordination between State, local, tribal, and regional information fusion centers and the Department;
(11) provide State, local, tribal, and regional information fusion centers with expertise on Department resources and operations;
(12) provide training to State, local, tribal, and regional information fusion centers and encourage such information fusion centers to participate in terrorist threat-related exercises conducted by the Department; and
(13) carry out such other duties as the Secretary determines are appropriate.
Technorati tags:
collaboration, community, coordination, DHS, e-government, ea, enterprise architecture, FEA, federal, geo, Geospatial, GIS, homeland security, interoperability, law, legislation, mapping, maps, metadata, news, OGC, policy, security, sharing, spatial

