The general theme of the outcome from yesterday is that we want to make zigGIS a solid experience for PostGIS users first. We have discussed other data sources in the past but we feel that we should nail down PostGIS first and then let that be a reference implementation for other data sources such as Oracle Spatial, MS SQL Spatial and the like.
With that said, the most glaring gap in the current capability of zigGIS is editing. Meaning you can’t. Editing is our highest priority in the near future. Over the next few weeks, we will be developing use cases to define an editing workflow. We’ll also prototype ways to integrate zigGIS with the native editing capabilities of ArcMap in order to reduce the amount of custom editing code we need to write.
We’ll also be restructuring the existing code. The current code is rather flat in that individual .cs files contain multiple classes and the directory structure doesn’t reflect the namespaces. Fixing all of that will give us a little more flexibility with version control and managing distributed programming. It’ll also make it easier if…ahem…any other programmers want to join the project.
There are also still some performance issues with the current capabilities we need to iron out, such as the one Bruce pointed out a while ago.
Of course the catalog objects are ongoing but there may not be any movement on that until after we get the code restructured. Paolo is going on vacation for three weeks 😀 but Abe is planning to start the code restructure in the meantime as a way to re-familiarize himself with the code.
As always, the biggest impediment is time. It seems that the need to put food on the table refuses to go away but we should be able to build a little more forward momentum than we’ve seen recently.