Sunday, May 17, 2015

Geospatial Data Quality System - QGIS integration, git tickets, and Project Info Table

Here is the recap of the work I completed on the GDQS project for this week

QGIS Integration

I'm excited to announce that I have my first integration working - launching QGIS from GeoServer.  This system needs and editor application to review the data that will be delivered to judge and make note of data quality.  Besides, what is a GIS system without a good editor application?  I've worked with a few of the OSS GIS editor applications, but I've had the best experience with QGIS.  An advantage of QGIS is that the "project" file (.qgs) is XML, which I can generate from GeoServer and stream to the user.  If QGIS is installed, the .qgs extension will be recognized by the machine and launch the application.

How was this done?  I created Wicket DownloadLink button and added it to the ProjectInfo page.  When the user clicks the button, a method will read the GDQS project information from the Data directory metadata, write the XML to a .qgs file and deliver it to the user:



I have my browser set to "always open files of type" QGIS, so the application is launched automatically after download.  Aide from the opening tag, the only info in the .qgs file is the Project name ("title" tag):

In the future, it will get populated with Layers and other info for the user.

Github account

I also now have a way to create tickets to track work and a repo to check in code.  Definitely a big step forward for my software development lifecycle:


Project Info Table

The one task that was started this week, but not finished is the Project Info table.  I would like to pull all of the Project object metadata and build a table, but only finished the work to get the table and it's header onto the page:


That is where I will start next week!

No comments: