Enable ssl

[saltaverde]

Enable SSL connections to the database

Add an ssl object based on ISSLConfig
interface

Allow for null geometry and srid

ESRI Feature Services can support tables, which have no geometry. This
change keeps the provider from erroring when reading postgres tables
that have no geometry but can still be served as a Feature Layer

[doneill]

Thanks @saltaverde, do you have an example of some data to test against?

[saltaverde]

Thanks @saltaverde, do you have an example of some data to test against?

@doneill It could be pretty much any table that doesn't have a column of type geometry or geography in it.

For example

create table test_data as (select (random() * 1000 + 1)::integer as id, substr(md5(random()::text), 1, 25) as name from generate_series(0, 9));

[doneill]

What is your intention with these values? I have refactored this module on the develop branch and plan to update with something like the following:

const result = await db.data.getGeometryColumnName(schema, table);

if (!result) {
  throw new Error('Invalid result from getGeometryColumnName');
}

To error out gracefully.

[saltaverde]

ESRI Feature Services can support tables, which have no geometry. This
change keeps the provider from erroring when reading postgres tables
that have no geometry but can still be served as a Feature Layer

My intention is to be able to serve a table (no geometry) in a feature service. We have a use case where we are using Koop to create a feature service with tables for our Survey123 app to query and dynamically populate choices in the survey. When doing this initially I ran into exceptions because the postgres table had no columns of type geometry. The workaround I found was to set these to null and then Koop served a table as expected. Erroring gracefully here is still erroring when this is a case that Koop supports.

[doneill]

@saltaverde Can you change the base branch to develop? I updated the error handling around tables w/o geometry columns. Let me know if that addresses your issue.

[doneill]

@saltaverde not sure if this is still relevant, but v1.0.9 generates an empty json object when geometry column not available on the table. Not sure if that is what you would expect, but the provider doesn't error out now.