Skip to content

Fix priority bounds check for Multi* geometry types and bypass cache in updateTaskPriorities#1223

Draft
CollinBeczak wants to merge 1 commit intomainfrom
Fix-priority-bounds-check-for-Multi--geometry-types-and-bypass-cache-in-updateTaskPriorities
Draft

Fix priority bounds check for Multi* geometry types and bypass cache in updateTaskPriorities#1223
CollinBeczak wants to merge 1 commit intomainfrom
Fix-priority-bounds-check-for-Multi--geometry-types-and-bypass-cache-in-updateTaskPriorities

Conversation

@CollinBeczak
Copy link
Copy Markdown
Contributor

@CollinBeczak CollinBeczak commented Apr 7, 2026

  • Add support for MultiPoint, MultiLineString, and MultiPolygon geometry types in the priority bounds check. Previously these fell through to a default false case, so tasks with these geometries were never recognized as being inside a priority region.
  • Fix coordinate length checks for Point and LineString from == 2 to >= 2 to handle 3D coordinates (with optional altitude).
  • Bypass cache in updateTaskPriorities to ensure the latest priority bounds are read from the database rather than potentially stale cached values.

Should resolve: maproulette/maproulette3#2800

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 7, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Not getting priority tasks from defined high priority bounds.

1 participant