Conor Brady

> Thanks for your help noting the gap in the docs, @bbroniewski -- we've merged in a change to fix that, so I'm going to close this ticket now. If...

> This could potentially also happen with sqlalchemy I guess. There you have `query.where(foo==bar)` queries. Verified today this is the case.

Potentially something that could be defined as a `Trivia`: https://github.com/charliermarsh/ruff/blob/main/crates/ruff_python_formatter/src/trivia.rs#L46 E.g. a `FilterFunction`. Not sure if it would make more sense to do the analysis at the AST level though,...

> We could consider ignoring these expressions inside of all `.where` calls, regardless of whether it's NumPy, SQLAlchemy, etc. We'd be trading off false negatives for false positives. I think...

> To share another real world example, I encountered this using ruff in a project that uses SQLAlchemy. Ruff fixed comparisons with `None` to use `is`/`is_not` instead of `==`/`!=` but...

> Additionally, once Ruff has type inference Is there an existing ongoing effort for this that's public?

If y'all are still evaluating postgres cluster tooling, I came across CloudNativePG: https://cloudnative-pg.io/ It's a project managed by the CNCF that has some pretty compelling support for cross-cluster architectures: https://www.cncf.io/blog/2023/09/29/recommended-architectures-for-postgresql-in-kubernetes/

Drew up a diagram as we were discussing: 

This ticket will need more refinement when we get into the visualization implementations, and most likely will be split up into further tickets. The file below is captured to provide...

Resolutions: Fuel Layer: Should be the same resolution in SFMS, affects calculations Elevations, Slope, Aspect: Align on SFMS resolution now, potentially add higher resolution layers later