SMASH 1.6.3 is out - experimental Postgis

We just released SMASH 1.6.3 on the stores. It should be available within the day.

This is basically a bugfix release, but we decided to also release one feature that will be very important in the future: postgis support.

The biggest issue with the last release is that we introduced an error trapping engine to allow the user to better send issues of the application to the developers. The problem we didn't notice for soem obscure reason is that everytime an online map tile would not be properly downloaded, this would result into a crash report. Your many email explained well the situation :-)))  This version fixes this.

We also enhanced the WMS source creator (which still needs much love) with the possibility to select the image format:

 

The note taking workflow just got a bit simpler. You can just tap on the text and the edit field is empty if the note had never been edited. This allows for less taps, which is great out in the field.

 Last but not least, we started adding PostGIS support. This will be a 2 steps effort. Step one (this one) is to add full online support. This means that you now can access the remote db view from the layers list:

Let's assume you have a test db running in your network, something like:

Then you can add a new remote db as:

you can enter the table or trigger a refresh, which will also help you in testing the connection:

you can also optionally add a where condition, if you need to load only a subset of the data.

Once the db is completed, it will stay in your list of available db datasets. Just add it as a layer to teh map using the rightmost button:

which will result in:

and on the map:

well, this looks kind of ugly. You might have seen in some previous post that SMASH supports styling via SLD specification. Well, adding style the same as we do for geopackage brings us to this:

Nice right?

Now this is a vector layer that can be selected:

The above view allows also for table data editing.

And also geometric editing is allowed:

So, why is this the first of two steps? Well, out in the field we often do not have network access, so we will need to create a solution that would allow to create a local geopackage cache, which then eventually can sync back to the remote db.

But we decided to first release the direct online postgis access, since that still has some nice usecases in situations in which the network is available. Once we have this one working stable, we will move on to the next step. So, if you are into Postgis and want to help, please test and report issues.

Enjoy!