Bbox fix--unscale OSM lat/long values

[jeffmaki]

Adjusted OSMRepository.getWorkspaceBBox to unscale OSM node latitude/longitude values when computing workspace bounding boxes, dividing the stored 1e7-scaled coordinates by 1e7 before returning results. The method’s not-found behavior is unchanged.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 182cc20b-461c-47e3-9457-5a0579812baf

📥 Commits

Reviewing files that changed from the base of the PR and between dda4920 and 402f5c2.

📒 Files selected for processing (1)

• api/src/osm/repository.py

---

📝 Walkthrough

Walkthrough

The SQL query in OSMRepository.getWorkspaceBBox was modified to divide the MAX/MIN latitude and longitude aggregates by 1e7, converting stored integer-scaled coordinates into decimal degree values.

Changes

Bounding Box Coordinate Conversion

Layer / File(s)	Summary
Convert bbox coordinates to decimal degrees api/src/osm/repository.py	The bounding box SQL query now divides MAX/MIN latitude and longitude aggregates by 1e7 to return decimal degree coordinates instead of raw scaled integers.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Poem

A hop, a scale, a tiny bug,
Coordinates once too snug.
Divide by ten million, clean and neat,
Now my map hops are precise and sweet! 🐰🗺️

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}