Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gde-exporter
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • 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
  • Dynamic ExposureDynamic Exposure
  • Global Dynamic ExposureGlobal Dynamic Exposure
  • gde-exporter
  • Merge requests
  • !5

Added TileExposure and ExportHandler classes

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Cecilia Nievas requested to merge feature/tileexposure into main Jun 29, 2022
  • Overview 0
  • Commits 1
  • Pipelines 2
  • Changes 22

TileExposure is a class that represents a tile and all its buildings and their attributes. gde-core instantiates this class by querying the tables of the GDE Tiles database, bringing together data and parameters that are stored separately and also over which the user has decision capacity (e.g. give number of people for which time of the day, give total costs or structural costs, etc.). The different formats will export the contents of the TileExposure object. TileExposure is independent from the output format.

ExportHandler handles the main processing activities of the gde-exporter. The main() method in gdeexporter.py calls it using multiprocessing.Pool, parallelising by quadkey group-occupancy case. The parallelisation is carried out in this way because different output files can be created for these groups and thus there is no interference in the part of the model that each core handles.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/tileexposure