Project update for week of Feb. 15th

This week I have been tasked with coming up with a working iPhone application. This application is to have some key functionality, such as:

• connect to the database server
• display some openGL content related to the project
• have a easy to use UI
• provide functionality for iphone functions such as accelerometer and other things

Currently, I have a template and a simple user interface. I hope to expand on this later in the week and at least have the iPhone application for the postgres server running. Later on I will try to incorporate aspects of Jianfei's desktop application.

Currently ,the learning curve is very steep on Objective-C programming and Cocoa touch. I am trying to sift through a mountain of information and come up with something that works, and it's not always easy.

FeatureServer and OpenLayers information

FeatureServer is an implementation of a RESTful Geographic Feature Service. Using standard HTTP methods, you can fetch a representation of a feature or a collection of features, add new data to the service, or delete data from the service. Use it as an aggregator -- post your GeoRSS feeds to it, and then browse them using WFS. Use it as a translator: use the OGR DataSource to load a shapefile and open it in Google Earth.

This software also is able to use a PostGIS as it's storage and information mechanism. In addition to this, there are several options for input/output:

• GeoJSON -- input and output in the emerging GeoJSON specification. FeatureServer supports GeoJSON Points, Lines, and Polygons with Rings, as both input and output.

• GeoRSS Atom (Simple) -- input and output of Points/Lines/Polygons (no rings/holes) in GeoRSS Simple (Atom). This allows one to take any GeoRSS Simple Atom feed and feed it to FeatureServer for storage.
• KML -- Input and output of Points, Lines, and Polygons from KML.
• GML/WFS -- Output-only support of WFS/GML.
• HTML -- Output-only support of features as HTML files, powered by Cheetah templates.
• OSM -- Output-only support of features as OpenStreetMap '.osm' files. (These files can be opened using JOSM and posted to the OSM server.)

Since the iPhone is very capable of reading the JSON data format and it is very useful for tabular data. I have already discusses using JSON earlier in the semester with Robert Kosara and he seems to think that it would be a very efficient and easy way to transfer data to the iPhone. Plus there are several programs available that read data from JSON for the iPhone, such as TouchJSON which can be found at this link: http://code.google.com/p/touchcode/.

As soon as I am able to get a test machine up and running with the new version of Postgresql I will be able to install these things and test them out. Then we can begin developing methods to transfer this information over to a format that will be displayed properly on an iPhone.

The image below shows the framework of the featureserver and the many storage and input/output options:

Project Progress update 1/24/2009

This week I have been able to acquire the CAD data files for the College of Education at UNCC. I have been through the process of "cleaning" up these data files for use in our database and for our automation program. This process allowed me to delete and filter out all polygons and other bits of data that were either erroneous or not useful. After this was finished I was able to take each floor and geo-reference it to the base map in order to put it in the correct coordinate system for this project.

The current building files are now located in our GIS database as spatial data files that have been converted from shapefiles. They are now in the proper format to be read by Jianfei's automated centerline program to make paths inside the building.

Other things that have been done are: setting up and test the new version of Postgresql on my Windows box. This has allowed me to install the pgPhoneHome iPhone web application that will allow us to mainipulate our database from the iPhone. This will hopefully provide a first step in our mobile application.

I have also come across a useful project called FeatureServer. It is basically a implementation of a RESTful Geographic Information feature service. I will be posting more information about this service and all of the details in a later blog post.

More Progress

It seems that I have finally corrected any errors that were occuring that were sending Jianfei's graph out of whack. These seem to have been most disconnection errors or labeling errors. We have been running tests using the path-finding algorithm and everything seems to be working OK. There are still some errors that are occuring due to problems with how the algorithm works and deciding on using stairways and elevators. These problems should be easy to fix.

Right now I am working on incorporating different data sources into ArcScene to try to create a composite scene with the graph model, woodward files, and other GIS data layers that might be relevent.

Here are some screens of how the graph is looking and a couple looks at the incorporated GIS data in ArcScene:



This mainly shows the internal structure of the hallways and paths to get around the building. This graph is what we will use for route-finding, and we hope this will eventually get incorporated into the street networks so we can do route finding on a larger scale (hopefully citywide)






These two images show how different data sources can be incorporated into our current work. I have created 3d building of the campus and added in roads and the woodward and cameron files. These files are obviosly much more detailed, however, having this type of view is nessessary not only to make it easier to visualize, but easier for an emergency worker to find their way around.