Skip to content

Archive for October, 2007

30
Oct

Indiana GIO Announcement

Press Release For Immediate Release October 29, 2007 Press Contact: Mehgan O’Connor moconnor@iot.IN.gov 317.234.4589 317.979.0877

Governor Appoints State’s First Geographic Information Officer INDIANAPOLIS, Ind. – Chief Information Officer Gerry Weaver today announced Governor Mitch Daniels’ appointment of Jim Sparks as the state’s first Geographic Information Officer. Sparks, whose first day with the state is today, will oversee the coordination of Geographic Information Systems (GIS) efforts across all state agencies and work with the Indiana Geographic Information Council, Inc. (IGIC) to adopt and implement the state’s GIS data policies, standards and statewide data integration plan. GIS technology works by linking information stored in databases to a place or location on a map. Users query the data, which is presented in maps, tables and other graphic representations. Since 80% of all government information has a geographic component, the power of GIS can be widely used to support decision-making and problem-solving across all sectors – public, private and not-for-profit. Sparks, an experienced geography and mapping professional, has extensive knowledge of geographic information systems (GIS) technology and experience in administration, policy development and planning. “Having a dedicated GIS expert in Indiana government pushes our capabilities to the next level,” said Weaver. “Working with the state’s current GIS talent, Sparks will create a consistent framework of statewide public maps and data for all levels of government that will help save lives and money and improve government efficiency.” To continue the coordination of enterprise information technology solutions that save the state, and ultimately taxpayers’, time and money, Sparks will report directly to Weaver, who oversees state IT.
###
About the Indiana Office of Technology (IOT) – The Indiana Office of Technology is an internal service agency that was created by Governor Mitch Daniels on January 10, 2005. Its mission is to provide cost-effective, secure, consistent, reliable enterprise technology services to its partner agencies so they can better serve Hoosier taxpayers. For more information about IOT, please visit http://iot.IN.gov .

11
Oct

My World GIS for the Mac

Earlier this summer I made the switch to a MacBook Pro OS-X. While I knew there was a dearth of GIS software for the Mac, I knew all the other reasons for a switch made good sense for me. I continue to use my PC only for GIS needs and every time I use it I hate to boot up the system at all. I have been searching for an easy, inexpensive GIS system to use on my Mac and have been continually disappointed – until now.

First, let me give a quick overview of what I have found… (a more comprehensive review of these systems is on cartographica.com). The tools I’ve downloaded so far are Quantum GIS (QGIS), UDig, SimpleDEMViewer, and OpenOX-Grass. The biggest disappointment is none of the really easy ones have any ANALYSIS capability — I personally don’t think it is a GIS if you can’t analyze the data. Viewing the data is great, but I definitely need more. Also, let me admit I am not sophisticated enough of a Mac user yet to do everything required to run OpenOX-Grass (it requires Apple X11) but I will try to work toward this because it does look very powerful http://openosx.com/grass/grass.html and the price (~$60 US) is right. Also, QGIS with Grass support looks very promising (if I can figure out how to implement it). My conclusion with these existing programs is that those that are easy enough to plug-and-play lack basic analysis capabilities, and those that show promise for being very powerful are limited by not being plug-and-play.

This brings me to a review of My World GIS (v4.1.1) for the Mac (it can also run on a PC). So far I have been pleasantly surprised.

My World GIS

Northwestern University has developed a GIS called My World, which engages ESRI’s MapObjects Java technology. My World is distributed by Pasco Scientific (http://www.pasco.com/myworld/). Built in Java, My World runs on Macintosh OSX and Windows environments. It provides a robust subset of capabilities from a professional GIS environment, including multiple projections, table and map view, hyperlinks, and a common language approach to conducting analyses. It is marketed to educators, but licensing is also available for non-educational use (for research or other non-educational uses) directly from Northwestern University (currently priced at $99 US per single license). There is a fully functional 45-day trial period available.

Data File Types

My World supports the following types of data files and/or folders for reading and writing shape data:

* ESRI Shapefile, Comma-Separated Values, Tab-Separated Values, and GPX Waypoint Files; plus a variety of Grid and Image file types, and WMS data feeds (more info here).

Adding Your Own Data

I did find adding my own shape files a bit confusing at first since My World doesn’t support the shape files in their native projection and requires them to be un-projected. That this wasn’t totally straight-forward was my only real disappointment with My World. But once I got past the hassle involved with importing my own data, I had a lot of fun with this program.

“My World accepts shape data only in Unprojected Latitude and Longitude in Decimal Degrees, and the longitude must be in the range -180 to +180 (rather than 0 to 360).

If your data uses another projection or different units, you can use My World to un-project and convert it to the proper units by selecting Un-Project Shapefile… from the File menu, or by clicking the Import Data From File… button in Construct mode.

My World accepts projected grid and image data, but you must know all the details of the projection used to project that data before you can use it in My World.”

How I added my own shape files… (some data does come pre-packaged)

I had to really experiment with this before being able to import my shape files and have them show correctly on the map. I was successful using the following steps:

1. I copied my existing data into a temporary folder before using the “Un-project” function (and DEFINITELY HAD A BACKUP OF MY ORIGINAL DATA ON AN EXTERNAL DRIVE).

2. I also created a new folder in the Data directory (in the My World application folder) to hold my data after I un-projected it.

3. When I used the “Un-Project” function, I saved the new files into the new directory folder (I got errors every time I just replaced the existing files).

4. I then deleted the temporary folder containing copies of my original data (My World gets confused if it finds 2 datasets with the same name).

5. Under the “Construct” tab, I added my data to the map by simply dragging and dropping the layer from the Library to the Layer list.

6. You can set the map projection later.

Now the fun part – seeing what My World can do.

Note, under the Visualize and Edit tabs, single click a layer to make it active and double click the layer to set parameters or edit.

Cartographic Features

I am pleasantly surprised by the cartographic capabilities of My World. You can outline and fill polygons with any standard or custom RGB value, easy create color ramps, categorize data, create dot density maps, transparencies, etc. If you’re familiar with commercial GIS platforms it should be pretty intuitive (and maybe even easier). There are about 20 shapes for point symbols, all of which you can control the size, color and transparency.

Labels (Annotation)

In My World you don’t label features per se, you create annotations. This wasn’t intuitive and was kind of buried in the documentation (especially since I was expecting labeling to be done in the same place as symbology), but it was really easy to do once I figured it out. Under the Edit tab, you have to click create new layer. One option you will be presented with for the new layer type is “Annotation.” You can then create an annotation layer from an existing layer, select the existing database field for the annotation, choose from a wide array for fonts, colors, sizes, style, alignment etc. While you can’t do a halo, you can do a background block color and make it transparent to help your text stand out. And since it is annotation, you can just select and move your text around to improve placement. Pretty sweet.

Analysis

This is by far my favorite part.

Not only is it robust, but the analysis menu is also super easy to use. Again, if you know GIS and how to do analysis it should be pretty intuitive. Otherwise, there is pretty good documentation available. For example, I was able to very easily “select by spatial relationship” all the building features (first layer) that were within 15 feet of all commercial properties (second layer)(see example). You have the option to save this as a new layer, or make it a selected subset of the existing layer. All the analysis capabilities for selecting by value, by comparing values, by spatial relationship; combining by intersect, union, subtract, and clip; adding fields by math operation, by copying values, reclassifying, computing distances, and selecting members; creating charts of the data, buffering data; dissolving, summarizing statistics, and converting data are all in one place, intuitive and easy to use, and come with a menu complete with graphic depiction of the operation. Wow.

Editing Data

From the edit tab, you can create new layers and/or edit the geometry and data for any of your existing layers, including grids. I easily moved vertices and created new polygons. A note of caution, it seems to automatically save your changes, but there is an undo button or ctrl-Z.

Other Stuff

Overall, the data were pretty zippy to load large files and Web Map Services (WMS). While this wont replace your enterprise GIS, it is a fine system for stand-alone GIS use on your Mac. Besides my own use, my kid’s school only has a Mac computer lab and I now have a good option for getting GIS into their curriculum. I personally am thrilled to have a functional GIS option for my Mac.

My World GIS – I put in the category of “robust low-cost GIS; professionals will be surprised.”

9
Oct

Proposal for a Quid Pro Quo Model for Geographic Data Exchange

Quid pro quo (Latin for “something for something” [1]) indicates a more-or-less equal exchange or substitution of goods or services.

Long time hindrances to the development of Statewide Spatial Data Infrastructures (SSDIs) and the National Spatial Data Infrastructure (NSDI) have been financial, organizational, and political (most believe technical issues have already been overcome). High quality data produced by local government is often encumbered by restrictive local government licensing policies. Those same local governments are faced with the reality of large price tags for geospatial data development and maintenance and shrinking budgets. As regional, statewide, and national driving issues increasingly identify the essential need for integrated SSDIs and an NSDI, many local governments are justifiably concerned that their participation will become an unfunded mandate. In the face of these obstacles, many funding options have been proposed to help offset the high costs of data programs at the local government level and encourage their participation.

However, few programs at the state level have been successful in establishing programs where sustained funding flows among multiple jurisdictional and levels of government for geospatial data development and maintenance. In fact, most states still struggle to establish adequate funding for state-level programs, let alone funding that would flow to other entities. I believe that a Quid Pro Quo approach to developing SSDIs and the NSDI could be a successful one from the standpoint of establishing a funding mechanism for cost sharing among stakeholders and managing the real constraints of local government to participation. Under this model, those essential data sets to local, state, and federal government, i.e. Framework data (such as orthophotography, elevation, and hydrography), that can efficiently be produced over broad areas would be maintained by capable state and federal entities. Those data appropriately maintained by local (city and county*) jurisdictions would continue as such.

An equitable cost share for SSDIs and the NSDI could be realized in a required quid pro quo exchange of framework data that support the majority of stakeholders’ data requirements. The concept of data stewardship at different levels of government is not new. What is uncommon among current business models is a structuring of a quid pro quo data exchange such that all parties clearly recognize and are responsible for a shared funding model for development and maintenance of Framework data (while uncommon, there are limited examples that demonstrate this can be a successful approach, such as Ohio’s Location Based Response System). I suggest that we are well on our way to such a model as an effective means of developing SSDIs and the NSDI if the National States’ Geographic Information Council’s (NSGIC) Imagery For The Nation (IFTN) program is implemented as proposed. However, if we leave out key aspects of this model up front, namely the unequivocal recognition of a quid pro quo exchange, then we are destined to failure once again.

For example, let us assume the development and maintenance costs of parcel, address and street centerline mapping is roughly equivalent to the development and maintenance costs of orthophotography and elevation mapping (of course exact figures depends on the methods of data acquisition, accuracies, etc.). If state and federal government took on the responsibility for orthophotography and elevation layers, as is proposed by the Imagery For The Nation (IFTN) program, this would offset substantial costs to local government to build and maintain their own geospatial programs. If however, the imagery and elevation are provided in the public domain without explicit and agreed upon recognition of a quid pro quo data exchange, then we face the very real possibility that local governments will not recognize it as such and will not recognize their responsibilities to contribute to the whole. In other words, local governments remain free to use the public domain data without recognizing the cost sharing aspects to their own programs.

Many (I would argue most) will be left to continue to view the external requests for their data as unfunded mandates. Without a clear plan for recognition of a quid pro quo data exchange, thus an equitable cost share in a shared public resource, we will continue to face the same financial, organizational, and political obstacles that we do today. It is not enough to “build it and they will come.” We must be prepared to recognize and agree upon, formally, our shared roles and responsibilities. Indiana is about to embark on a social experiment that would equate to such a quid pro quo data exchange. Under a new GIS statute, Indiana’s Framework data layers are formally defined, as is a provision for “data exchange agreements” meaning an agreement concerning the exchange of any GIS data or framework data.

While political subdivisions maintain the right to control the sale, exchange, and distribution of any GIS data or framework data provided by the political subdivision to the state through a data exchange agreement, a political subdivision may agree, through a provision in a data exchange agreement, to allow the sale, exchange, or distribution of GIS data or framework data provided to the state. As a condition in a data exchange agreement for any GIS data or framework data provided by the state to a political subdivision, the state Geographic Information Officer may require the political subdivision to follow the state GIS data standards and the statewide data integration plan when the political subdivision makes use of the GIS data or framework data as provided by the state. (Note, this does not apply to data that is otherwise required by state or federal law to be provided by a political subdivision to the state or federal government.)

As they have not yet been developed, the details of the data exchange agreements remain to be seen. I would assert that to enable a successful SSDI in Indiana, the data exchange agreements and the statewide data integration plan should explicitly define two important quid pro quo provisions: 1. Assurance that the state will maintain an ongoing high-resolution orthophotography and elevation data program, akin to Indiana’s 2005 successful orthophotography project and the proposed IFTN program (this will require a state funding commitment), that the data will reside in the public domain, and 2. That in exchange for receiving state provided framework data, political subdivisions will provide specific locally maintained framework data (e.g. parcels, addresses, and street centerlines), absent of personal/private information such as land owner names, and that the data be integrated into derivative data sets that reside either in the public domain or under a commercially restricted Creative Commons license (this is a policy issue that should be further reviewed).

I assert that equitable shared funding through a formally defined quid pro quo data exchange would enable SSDIs and the NSDI. This will require revised policies and a clear well-coordinated strategy for implementation (I do not believe it can be implemented piecemeal). There are many other issues to be tackled, including developing data where none currently exist, accessing restricted public data where they do exist (e.g., Census address coordinate data), technical issues related to data integration, etc. Still, financial, organizational, and political constraints have been the most significant obstacles to our success. If we can find ways to overcome these obstacles, the payoffs will be high. If we continue to sidestep these issues in favor of incremental progress on individual data layers, I believe the vision of SSDIs and the NSDI will be difficult, if not impossible, to truly realize.

___________ *Every state is different, and this must be recognized in Statewide Spatial Data Infrastructure business plans (e.g. some states already manage statewide addresses and parcels; some states are currently unprepared to manage statewide orthophotography).

This site uses a Hackadelic PlugIn, Hackadelic Sliding Notes 1.6.2.