#Prisma PostGIS
1 messages · Page 1 of 1 (latest)
You selected the bot's instantaneous insights. Let me compile your answer right away!
There is no specific scheduled release date for PostGIS support, but Prisma has provided some timeline indicators:
-
According to the official Prisma Postgres extensions documentation, "PostGIS is coming in 2026." [Postgres extensions docs]
-
The Prisma team has confirmed they are actively designing GIS support and conducted a community survey to shape the feature. [PostGIS/GIS support issue]
-
The current Q4 2025 roadmap (October–December 2025) focuses on Prisma 7, PGVector, Full-Text Search, and graduating preview features — PostGIS is not listed as a priority for this quarter. [3-Month Roadmap 2025]
Current Workaround
In the meantime, you can use Unsupported types in your schema combined with raw SQL queries:
model berlin_pois {
gid Int @id @default(autoincrement())
geom Unsupported("geometry")?
@@index([geom], name: "berlin_poi_idx", type: Gist)
@@ignore
}
Then query using $queryRaw for PostGIS-specific operations. [PostGIS/GIS support issue]
If PostGIS support is critical for your project, upvoting issue #2789 or issue #1798 is recommended to help prioritize it.
🤔 Alright, thanks for letting us know that there's still some help needed. A team member will reply to you shortly.
In the meantime, please let us know any additional info, questions, or which parts of the answer may need clarification.
Hey!
Thanks for raising this question. We do have this on our roadmap. We are running into a technical bottleneck which is causing the delay. I'll inform our product team and request to get this prioritised.
Many thanks!! Saw it was on the roadmap for 2026 and was wondering if it'll be early or late in the year. GIS is pretty critical for us so would be very nice to have!
+1, i see the docs https://www.prisma.io/docs/orm/prisma-client/special-fields-and-types/working-with-geometry-fields describe support for it but don't mention on this page specifically that its not available yet.
We utilize it and just break out into raw queries and Raw unsupported types in the meantime. GIS is only used for a few features for us so its just a handful of queries. If your entire app requires it — that might be a bit tedious
Our app is definitely GIS heavy but most of it is in one place so the raw types have been fine for us for now gladly
Im not associated with prisma but with their whole push or “plugin rich” ecosystem and calling for plugin authors on Prisma Next - I’m betting you’ll just be waiting on support there instead.