Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • E exposure-lib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Global Dynamic ExposureGlobal Dynamic Exposure
  • LibrariesLibraries
  • exposure-lib
  • Issues
  • #40

Change the exposure-lib to use the `AbstractDatabase` class for database polymorphy

The exposure-lib currently is derived from SpatiaLiteDatabase. To be able to provide an abstract layer for the user/programmer, it must be based on the AbstractDatabase class so that it can be connected either locally to a SpatiaLite database or to a server-based PostGIS database. This change is necessary so that we can develop the distributor and builder such that these programs can be used for local exposure data creation as well as for the server-based model.

This change may result in a fundamental change of the exposure-lib but should leave the interface the same.

\rfc @laurens @tara @shinde

Edited Aug 29, 2022 by Danijel Schorlemmer
Assignee
Assign to
Time tracking