Django ORM raw query not playing nice with Geometric Point objects

[Donovan]

When using <Object>.objects.all() the behavior works as intended and I am able to get the Geometric Point object with the latitude and longitude correct.
When using <Object>.objects.raw() the Point object has incorrect latitude and longitude -- it has scientific notation and completely different numbers.

[Donovan]

Showing what the point objects look like with a <object>.objects.raw() query look like when doing a print(vars(object))

[Donovan]

What the the Point object should have for latitude and longitude

[Mariusz Felisiak]

Using .raw() is a last resort. Django takes a raw SQL query, executes it, and returns results (as documented), it will not automatically add any data conversion to columns. Geometry columns returned by the ORM are wrapped with db-specific functions, e.g. %s::bytea on PostgreSQL or SDO_UTIL.TO_WKBGEOMETRY(%s) on Oracle.

If you're having trouble understanding how Django works, see TicketClosingReasons/UseSupportChannels for ways to get help.