Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • castellum castellum
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Castellum
  • castellumcastellum
  • Merge requests
  • !1399

Closed
Created Jun 10, 2020 by Bengfort@bengfortOwner
  • Report abuse
Report abuse

Example geofilter

  • Overview 3
  • Commits 4
  • Pipelines 2
  • Changes 9

This is an example geofilter using the existing interfaces. What is striking to me is how much boilerplate code is necessary. I have some ideas how this could be improved.

  • use project templates to generate the boilerplate automatically
  • store the result in AttributeSet.data instead of a custom model. This is a JsonField, so we can add more data without migrations. On the other hand, I am not sure if I want to encourage filter authors to meddle with AttributeSet directly.
  • Do not use custom filters at all and instead provide an interface to import multipolygons as geofilters (inside polygon is a match)
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: example-geofilter