Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • mapMCDA mapMCDA
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • 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
    • Container 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
  • UMR-ASTREUMR-ASTRE
  • mapMCDAmapMCDA
  • Issues
  • #52
Closed
Open
Issue created Feb 11, 2021 by Facundo Muñoz@famuvie®️Owner

More flexible processing vector layers

For any vector input mapMCDA currently considers only its geometry and computes the distance map to the spatial features it contains, disregarding its attribute table, if any.

However, sometimes users need to use some spatial variable that is spatially aggregated into an attribute of some vector map. They need to rasterize the attribute externally and feed the resulting raster into mapMCDA.

We could offer the possibility of doing this automatically, at the moment of scaling. We can default to the current distance map and, whenever there is an attribute table, offer the possibility to rasterise any of the quantitative variables.

Edited Feb 11, 2021 by Facundo Muñoz
Assignee
Assign to
Time tracking