Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • floodam-data floodam-data
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

La forge institutionnelle d'INRAE étant en production depuis le 10 juin 2025, nous vous recommandons d'y créer tous vos nouveaux projets.

  • flood-appraisal
  • floodamfloodam
  • floodam-datafloodam-data
  • Issues
  • #13
Closed
Open
Issue created Mar 08, 2022 by Grelot Frederic@frederic.grelot🏊🏿Owner

analyse intersections of spatial DB

Purpose of the functionality

When analyzing spatial DB with eaip DB, it is performed, for the moment: a test if geometries from the spatial DB intersects eaip DB (with sf::st_intersects). It should be useful to add also the proportion of area inside eaip DB for each geometry. For this part, some preliminary tests have shown that it is quicker with sf than with terra.

The results from the analysis should be added to normalized variables:

  • eaip (TRUE/FALSE) for intersects
  • eaip_prop (double between 0 and 1) for intersection

It is surely better to use a generic function that will be used in a less generic one for eaip

Functions to be added

  • analyse_intersection return the result from intersect or intersection in a convenient way.
    • expected inputs
      • x: sf object to be analysed
      • y: sf object to do the analysis (typically eaip)
      • analysis: character to precise the analysis to perform (intersect / proportion)
      • verbose: to send message
    • expected outputs
      • data.frame of result, same rows as in x, with 1 or 2 columns ("intersect", "proportion")
  • analyse_eaip wrapper of analyse_intersection to have the normalized names for return.
    • expected inputs
      • x: sf object to be analysed
      • y: eaip object
      • analysis: character to precise the analysis to perform (intersect / proportion)
      • verbose: to send message
    • expected outputs
      • data.frame of result, same rows as in x, with 1 or 2 columns ("eaip", "eaip_prop")

Data to be added

  • non

Documentation

  • analyse_intersection
  • analyse_eaip

Test to be performed

  • analyse_intersection with ad hoc data
Edited Mar 09, 2022 by Grelot Frederic
Assignee
Assign to
Time tracking