Q&A

Where can brdr be used?

  • Short answer: for geospatial quality assurance and boundary alignment workflows.
  • Long answer:
    • Geodata management:
      • business workflow integration
      • bulk alignment
      • post-reprojection correction
      • geometric cleanup after processing
    • Data analysis:
      • pattern analysis of deviation between thematic and reference boundaries
    • Update detection:
      • compare observations before and after alignment

Does brdr support multiple coordinate systems (CRS)?

  • Short answer: yes.
  • Long answer: you can choose the CRS when creating the Aligner. Use a projected CRS with meter units. Input data must be available in that CRS. On-the-fly loaders try to request/download that CRS; if unsupported by the source service, loading fails with an error.

Which geometry types are supported?

  • Short answer: (Multi)Point, (Multi)LineString, and (Multi)Polygon.
  • Long answer: brdr started with polygon-to-polygon alignment and later added processors for point/line/polygon combinations.

How do I choose the best processor?

  • Short answer: use AlignerGeometryProcessor (default) first.
  • Long answer:
    • AlignerGeometryProcessor delegates to specialized processors based on context.
    • DieussaertGeometryProcessor is typically faster and strong for polygon-to-polygon scenarios.
    • NetworkGeometryProcessor is more generic for mixed geometry combinations but usually slower.
    • TopologyProcessor is experimental and focuses on preserving shared topology between neighboring thematic features.

Recommendation: for polygon-to-polygon use cases, start with DieussaertGeometryProcessor. Move to NetworkGeometryProcessor when generic/mixed geometry behavior is required.

Does brdr support 3D or M/Z coordinates?

  • Short answer: no, processing is 2D.
  • Long answer: alignment is computed on X/Y coordinates. Any Z or M values are not used by the core alignment logic.

Is topology preserved between thematic input features?

  • Short answer: not by default.
  • Long answer: standard processing handles features independently. If topology preservation is required, use TopologyProcessor (experimental).