When dealing with huge DB tables, the default behavior of geoflow to read the full content of a DB table can result in a bottleneck. Such default behavior, which is common to data fetched from files (local or remote) and DBs, is required to inherit properties that used to enriched the entity. This is essentially the spatial properties, including the srid and spatial coverage.
When skipDataDownload (previously called skipFileDownload, see #349 ) is enabled, we remove the bottleneck, but we lose the spatial properties inheritance.
A method called enrichSpatialCoverageFromDB is going to be developed to get these spatial properties through dedicated SQL queries.
Development sponsored by IRD
@IRDnamik @kikislater @juldebar
When dealing with huge DB tables, the default behavior of geoflow to read the full content of a DB table can result in a bottleneck. Such default behavior, which is common to data fetched from files (local or remote) and DBs, is required to inherit properties that used to enriched the entity. This is essentially the spatial properties, including the
sridandspatial coverage.When
skipDataDownload(previously calledskipFileDownload, see #349 ) is enabled, we remove the bottleneck, but we lose the spatial properties inheritance.A method called
enrichSpatialCoverageFromDBis going to be developed to get these spatial properties through dedicated SQL queries.Development sponsored by IRD @IRDnamik @kikislater @juldebar