Raw SQL with Specification - What's the recommended approach?

I'm currently working with Ardalis.Specification and have a use case that requires raw SQL queries, specifically for spatial data with PostGIS functions. For example:

```csharp
var nearbySegments = await _context.StreetSegments
.FromSqlInterpolated($"""
SELECT *
FROM "public"."StreetSegments"
WHERE "CityId" = {act.CityId}
-- exclude segments already processed in the direct pass:
AND NOT ("OsmWayId" = ANY({directWayIds}))
-- use meters with geography casting:
AND ST_DWithin("Geom"::geography, {routeLine}::geography, {sightRadiusMeters}, true)
""")
.AsNoTracking();
```

What is the recommended approach for handling raw SQL queries like this while still using the Specification pattern? Do you have any suggestions for integrating these types of queries into the Ardalis.Specification workflow, or is it better to handle them separately outside the specification pattern?

I'm curious what other developers typically do when they encounter scenarios where LINQ expressions aren't sufficient for their query needs but they want to maintain the benefits of using specifications.

Start with the issue's FromSqlInterpolated example and the repository's specification workflow. Determine whether raw SQL with PostGIS belongs inside a specification or should remain separate, then document a clear recommended approach and its limitations for users.

Written by the indexing model from the issue text.