aws-cqc / aws-cqc/DeviceLayout.jl

Julia geometry ecosystem integration

Open
#35 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Julia
Stars
67
Forks
14
Avg merge
1d 19h
Merged PRs (30d)
24

Description

The geometry ecosystem is maturing, and we should take a fresh look at whether and how to integrate with it. Development seems to focus on geosciences but there are still generic methods and abstractions that could be useful to us. Probably the most utility for the least work would be to [implement GeoInterface](https://juliageo.org/GeoInterface.jl/stable/guides/developer/) for our `Polygon`. Then we could at least use things like [GeometryOps](https://github.com/JuliaGeo/GeometryOps.jl) (e.g. for pure Julia clipping and [simplification](https://juliageo.org/GeometryOps.jl/stable/source/transformations/simplify)) or [Rasters.jl](https://github.com/rafaqz/Rasters.jl/) (c.f. our homebrew `gridpoints_in_polygon`) with polygon-only geometries.

Contributor guide

Open the contributing guide

Research direction

Start by reading the Polygon implementation and the existing homebrew gridpoints_in_polygon functionality, then review the linked GeoInterface developer guide. Determine the interface needed for Polygon and check the proposed GeometryOps clipping/simplification and Rasters.jl polygon use cases; done means Polygon integrates with the relevant generic methods.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.