Oracle.EntityFrameworkCore.NetTopologySuite 10.23.26000-Preview.1

Oracle.EntityFrameworkCore.NetTopologySuite 10.23.26000-Preview.1

Release Notes for Oracle Entity Framework Core NetTopologySuite 10 Preview 1 NuGet Package

November 2025

Oracle.EntityFrameworkCore.NetTopologySuite is the spatial extension for Oracle Entity Framework Core provider. It enables the use of spatial data types with Oracle databases through Entity Framework Core and NetTopologySuite (NTS). Entity Framework Core (EF Core) is a cross-platform Microsoft object-relational mapper that enables .NET developers to work with relational databases using .NET objects.

This document provides information that supplements the Oracle Data Provider for .NET (ODP.NET) documentation.

Usage

Call UseNetTopologySuite inside the call to UseOracle when configuring the Oracle database provider for your DbContext.

You can optionally specify a tolerance value, which determines the precision level for spatial operations such as Equals, Intersects, or Buffer.

• The tolerance value must be a positive number greater than zero.

• If not specified, the default tolerance is 0.005.

Example (default tolerance):

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    => optionsBuilder.UseOracle(
        "User Id=hr;Password=<PASSWORD>;Data Source=MyOracleDB;",
        b => b.UseNetTopologySuite());

Example (custom tolerance):

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    => optionsBuilder.UseOracle(
        "User Id=hr;Password=<PASSWORD>;Data Source=MyOracleDB;",
        b => b.UseNetTopologySuite(tolerance: 0.001));

Oracle .NET Links

• Oracle Spatial and Graph Developer’s Guide
• Oracle .NET Home Page
• GitHub - Sample Code
• ODP.NET Discussion Forum
• YouTube
• X (Twitter)
• Email Newsletter Sign Up

New Features

• Oracle spatial data via NetTopologySuite

Tips, Limitations, and Known Issues

LINQ

• LINQ queries comparing GeometryCollection objects with a Polygon as the last item after a LineString are not supported. For example, imagine an entity model with the following entities:

public class GeoEntity
{
    public int Id { get; set; }
    public GeometryCollection Shape { get; set; }
}

The following LINQ would throw 'ORA-13354: incorrect offset in ELEM_INFO_ARRAY':

var gc = new GeometryCollection(
    new Geometry[]
    {
        new Point(1, 1) { SRID = 4326 },
        new LineString(new[]
        {
            new Coordinate(2, 2),
            new Coordinate(3, 3)
        }) { SRID = 4326 },
        new Polygon(new LinearRing(new[]
        {
            new Coordinate(4, 4),
            new Coordinate(4, 6),
            new Coordinate(6, 6),
            new Coordinate(6, 4),
            new Coordinate(4, 4)
        })) { SRID = 4326 }
    }
) { SRID = 4326 };

var match = context.Geometries
                   .Where(e => e.Shape.EqualsExact(gc))
                   .ToList();

As a workaround, Ensure the polygon is placed before the LineString:

var gc = new GeometryCollection(
    new Geometry[]
    {
        new Point(1, 1) { SRID = 4326 },
        new Polygon( ... ) { SRID = 4326 },
        new LineString( ... ) { SRID = 4326 }
    }
);

• LINQ queries using union or convex hull aggregates that return MULTIPOINT are not supported in Oracle 19c database version. Let us first imagine an entity model with the following entity:

public class PointEntity
{
    public int Id { get; set; }
    public string Group { get; set; }
    public Point Point { get; set; }
}

The following LINQ will return incomplete or invalid geometry in the union and convex hull result against Oracle 19c database version:

var results = context.PointEntity
    .Where(e => e.Point != null)
    .GroupBy(e => e.Group)
    .Select(g => new {         
        Union = UnaryUnionOp.Union(g.Select(e => e.Point)),
        ConvexHull = ConvexHull.Create(g.Select(e => e.Point))
        })
    .ToList();

Copyright (c) 2025, Oracle and/or its affiliates.