NHibernateSpatial Wiki & Documentation Rss Feed

Updated Wiki: Home

rstuven — Wed, 08 Oct 2008 17:19:01 GMT

__________________________________________________________________________________________________________

We're moving to NHibernate Forge

Thereinafter, please submit your bug reports or feature requests to NH issue tracker
and support questions to NH Users mailing list

__________________________________________________________________________________________________________

NHibernate.Spatial, Spatial extensions for NHibernate, allows you to connect NHibernate to a spatially enabled database and manipulate geometries in HQL or in .NET code using NetTopologySuite, providing you with a fully integrated GIS programming experience.

More info: http://www.nhforge.org/wikis/spatial/introduction.aspx

Updated Wiki: Configuration and mapping

rstuven — Wed, 08 Oct 2008 17:17:49 GMT

See http://www.nhforge.org/wikis/spatial/configuration-and-mapping.aspx

Updated Wiki: Sample usage

rstuven — Wed, 08 Oct 2008 17:17:16 GMT

See http://www.nhforge.org/wikis/spatial/sample-usage.aspx

Updated Wiki: Sample usage

rstuven — Wed, 08 Oct 2008 17:16:58 GMT

http://www.nhforge.org/wikis/spatial/sample-usage.aspx

Updated Wiki: Home

rstuven — Fri, 26 Sep 2008 22:40:59 GMT

__________________________________________________________________________________________________________

We're moving to NHibernate Forge

Thereinafter, please submit your bug reports or feature requests to NH issue tracker
and support questions to NH Users mailing list

__________________________________________________________________________________________________________

NHibernate.Spatial, Spatial extensions for NHibernate, allows you to connect NHibernate to a spatially enabled database and manipulate geometries in HQL or in .NET code using NetTopologySuite, providing you with a fully integrated GIS programming experience.

There is also a similar but independent effort for Java: Hibernate Spatial.

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OGCspecifications.
Dialects: MsSqlSpatial and PostGIS are supported. SQL Server 2008 support is at early stage. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: Spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: Spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. registering of geometry columns in metadata table).
Metadata mappings: Built-in mappings to spatial metadata through GeometryColumns and SpatialReferenceSystem classes.

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll, GeoAPI.dll and to provider assembly (eg. NHibernate.Spatial.PostGis.dll).

Configuration and mapping

Sample usage

Updated Wiki: Home

rstuven — Fri, 26 Sep 2008 21:36:29 GMT

NHibernate.Spatial, Spatial extensions for NHibernate, allows you to connect NHibernate to a spatially enabled database and manipulate geometries in HQL or in .NET code using NetTopologySuite, providing you with a fully integrated GIS programming experience.

There is also a similar but independent effort for Java: Hibernate Spatial.

We're moving to NHibernate Forge

Thereinafter, please submit your report bugs or feature requests to NH JIRA
and support questions to NH Users mailing list

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OGCspecifications.
Dialects: MsSqlSpatial and PostGIS are supported. SQL Server 2008 support is at early stage. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: Spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: Spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. registering of geometry columns in metadata table).
Metadata mappings: Built-in mappings to spatial metadata through GeometryColumns and SpatialReferenceSystem classes.

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll, GeoAPI.dll and to provider assembly (eg. NHibernate.Spatial.PostGis.dll).

Configuration and mapping

Sample usage

Updated Wiki: Home

rstuven — Fri, 26 Sep 2008 19:22:04 GMT

We're moving to NHibernate Forge

Thereinafter, please submit your report bugs or feature requests to NH JIRA
and support questions to NH Users mailing list

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OGCspecifications.
Dialects: MsSqlSpatial and PostGIS are supported. SQL Server 2008 support is at early stage. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: Spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: Spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. registering of geometry columns in metadata table).
Metadata mappings: Built-in mappings to spatial metadata through GeometryColumns and SpatialReferenceSystem classes.

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll, GeoAPI.dll and to provider assembly (eg. NHibernate.Spatial.PostGis.dll).

Configuration and mapping

Sample usage

Updated Wiki: Home

rstuven — Fri, 19 Sep 2008 19:00:49 GMT

We're moving to NH Contrib project

More details coming soon.

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OGCspecifications.
Dialects: MsSqlSpatial and PostGIS are supported. SQL Server 2008 support is at early stage. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: Spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: Spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. registering of geometry columns in metadata table).
Metadata mappings: Built-in mappings to spatial metadata through GeometryColumns and SpatialReferenceSystem classes.

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll, GeoAPI.dll and to provider assembly (eg. NHibernate.Spatial.PostGis.dll).

Configuration and mapping

Sample usage

Updated Wiki: Home

rstuven — Mon, 23 Jun 2008 10:01:54 GMT

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OGCspecifications.
Dialects: MsSqlSpatial and PostGIS are supported. SQL Server 2008 support is at early stage. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: Spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: Spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. registering of geometry columns in metadata table).
Metadata mappings: Built-in mappings to spatial metadata through GeometryColumns and SpatialReferenceSystem classes.

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll, GeoAPI.dll and to provider assembly (eg. NHibernate.Spatial.PostGis.dll).

Configuration and mapping

Sample usage

UPDATED WIKI: Home

rstuven — Tue, 06 Nov 2007 12:42:33 GMT

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OpenGIS specifications.
Dialects: MsSqlSpatial and PostGIS are supported. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: Spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: Spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. registering of geometry columns in metadata table).
Metadata mappings: Built-in mappings to spatial metadata through GeometryColumns and SpatialReferenceSystem classes.

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll and GeoAPI.dll

Configuration and mapping

Sample usage

UPDATED WIKI: Configuration and mapping

rstuven — Thu, 14 Jun 2007 16:43:20 GMT

Dialect Configuration:

In the NHibernate section of your configuration file add the following entry:

<property name="hibernate.dialect">NHibernate.Spatial.Dialect.SomeSpatialDialect,NHibernate.Spatial</property>

If you're using Castle ActiveRecord, the entry will look like this:

<add key="hibernate.dialect" value="NHibernate.Spatial.Dialect.SomeSpatialDialect,NHibernate.Spatial" />

Replace SomeSpatialDialect by the spatial dialect to be used. For example, MsSqlSpatialDialect.

Schema Generation Configuration:

Declarative: Use of <database-object> element is not supported.
Programmatic:

    Configuration cfg = new Configuration();
    // Your configuration code (eg. cfg.Configure(); )
    cfg.AddAuxiliaryDatabaseObject(new SpatialAuxiliaryDatabaseObject(cfg));

Then you can use a SchemaExport object or the hibernate.hbm2ddl.auto configuration property for schema generation.

Metadata Mappings Configuration:

There are two classes available for metadata mapping in the NHibernate.Spatial.Metadata namespace: GeometryColumn and SpatialReferenceSystem. You can add them selectively:

Configuration cfg = new Configuration();
// Your configuration code (eg. cfg.Configure(); )
Metadata.AddMapping(cfg, MetadataClass.GeometryColumn);
Metadata.AddMapping(cfg, MetadataClass.SpatialReferenceSystem);

Then you can use them as normal mapped classes. For example, you could execute the following HQL query:

select srs.WellKnownText from SpatialReferenceSystem as srs where srs.SRID=4326

WARNING: DO NOT add metadata class mappings when using the SchemaExport utility. You could lose all contents of metadata tables.

NHibernate Mapping:

In the XML mappings file, map all properties as usual but for geometry columns use the following entry:

<property name="Geometry" column="the_geom" type="NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial" />

Optionally, for schema generation and default values setting, you can use type parameters. The available parameters are srid and subtype. For example:

<property name="Geometry" column="the_geom">
    <type name="NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial">
        <param name="srid">4326</param>
        <param name="subtype">POLYGON</param>
    </type>
</property>

In the mapped class, declare the corresponding property:

private GeoAPI.Geometries.IGeometry _geometry; 
public virtual GeoAPI.Geometries.IGeometry Geometry
{
	get
	{
		return this._geometry;
	}
	set
	{
		this._geometry = value;
	}
}

ActiveRecord Mapping:

private GeoAPI.Geometries.IGeometry _geometry; 
         
[Property("the_geom", ColumnType = "NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial")]
public virtual GeoAPI.Geometries.IGeometry Geometry
{
	get
	{
		return this._geometry;
	}
	set
	{
		this._geometry = value;
	}
}

NOTE: Type parameters (see NHibernate mapping above) are not supported in ActiveRecord.

ActiveWriter Mapping:

ActiveWriter is a tool to visually model entities and relationships, and generate ActiveRecord classes or NHibernate mapping files. Since Preview 3, it supports custom types, so we can use the GeometryType / IGeometry pair..

Example usage:

Drag & drop a MsSqlSpatial table from Server Explorer/Data connections.
In the model, select "the_geom" property.
In the properties window, enter the following values:

Property	Value
Column Type	Custom
Custom Column Type	NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial
Custom Member Type	GeoAPI.Geometries.IGeometry

NOTE: Type parameters (see NHibernate mapping above) are not supported in ActiveRecord, so it is in ActiveWriter.

UPDATED WIKI: Home

rstuven — Wed, 13 Jun 2007 19:58:04 GMT

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OpenGIS specifications.
Dialects: MsSqlSpatial and PostGIS are supported. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: Spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: Spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. insert rows into geometry columns metadata table).
Metadata mappings: Built-in mappings to spatial metadata through GeometryColumns and SpatialReferenceSystem classes.

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll and GeoAPI.dll

Configuration and mapping

Sample usage

UPDATED WIKI: Configuration and mapping

rstuven — Wed, 13 Jun 2007 19:51:17 GMT

Dialect Configuration:

In the NHibernate section of your configuration file add the following entry:

<property name="hibernate.dialect">NHibernate.Spatial.Dialect.SomeSpatialDialect,NHibernate.Spatial</property>

If you're using Castle ActiveRecord, the entry will look like this:

<add key="hibernate.dialect" value="NHibernate.Spatial.Dialect.SomeSpatialDialect,NHibernate.Spatial" />

Replace SomeSpatialDialect by the spatial dialect to be used. For example, MsSqlSpatialDialect.

Schema Generation Configuration:

Declarative: Use of <database-object> element is not supported.
Programmatic:

    Configuration cfg = new Configuration();
    // Your configuration code (eg. cfg.Configure(); )
    cfg.AddAuxiliaryDatabaseObject(new SpatialAuxiliaryDatabaseObject(cfg));

Then you can use a SchemaExport object or the hibernate.hbm2ddl.auto configuration property for schema generation.

Metadata Mappings Configuration:

There are two classes available for metadata mapping in the NHibernate.Spatial.Metadata namespace: GeometryColumn and SpatialReferenceSystem. You can add them selectively:

Configuration cfg = new Configuration();
// Your configuration code (eg. cfg.Configure(); )
Metadata.AddMapping(cfg, MetadataClass.GeometryColumn);
Metadata.AddMapping(cfg, MetadataClass.SpatialReferenceSystem);

Then you can use them as normal mapped classes. For example, you could execute the following HQL query:

select srs.WellKnownText from SpatialReferenceSystem as srs where srs.SRID=4326

WARNING: DO NOT add metadata class mappings when using the SchemaExport utility. You could lose all contents of metadata tables.

NHibernate Mapping:

In the XML mappings file, map all properties as usual but for geometry columns use the following entry:

<property name="Geometry" column="the_geom" type="NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial" />

Optionally, for schema generation and default values setting, you can use type parameters. The available parameters are srid and subtype. For example:

<property name="Geometry" column="the_geom">
    <type name="NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial">
        <param name="srid">4326</param>
        <param name="subtype">POLYGON</param>
    </type>
</property>

In the mapped class, declare the corresponding property:

private GeoAPI.Geometries.IGeometry _geometry; 
public virtual GeoAPI.Geometries.IGeometry Geometry
{
	get
	{
		return this._geometry;
	}
	set
	{
		this._geometry = value;
	}
}

ActiveRecord Mapping:

private GeoAPI.Geometries.IGeometry _geometry; 
         
[Property("the_geom", ColumnType = "NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial")]
public virtual GeoAPI.Geometries.IGeometry Geometry
{
	get
	{
		return this._geometry;
	}
	set
	{
		this._geometry = value;
	}
}

NOTE: Type parameters (see NHibernate mapping above) are not supported in ActiveRecord.

ActiveWriter Mapping:

ActiveWriter is a tool to visually model entities and relationships, and generate ActiveRecord classes or NHibernate mapping files. Since revision 186, it supports custom types, so we can use the GeometryType / IGeometry pair. To get the latest sources and building instructions, see here.

Example usage:

Drag & drop a MsSqlSpatial table from Server Explorer/Data connections.
In the model, select "the_geom" property.
In the properties window, enter the following values:

Property	Value
Column Type	Custom
Custom Column Type	NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial
Custom Member Type	GeoAPI.Geometries.IGeometry

NOTE: Type parameters (see NHibernate mapping above) are not supported in ActiveRecord, so it is in ActiveWriter.

UPDATED WIKI: Sample usage

rstuven — Wed, 13 Jun 2007 18:49:32 GMT

Find a country by coordinates:

Using NHibernate:

Country country = session.CreateCriteria(typeof(Country))
    .Add(SpatialExpression.Contains("Boundaries", new Point(-70.40, -33.24)))
    .UniqueResult() as Country;

Using ActiveRecord:

Country country = Country.FindOne(
    SpatialExpression.Contains("Boundaries", new Point(-70.40, -33.24))
);

Find all the towns in a bounding box, except the one located at some coordinates:

Using NHibernate:

IList towns = session.CreateCriteria(typeof(Town))
    .Add(SpatialExpression.Filter("Boundaries", new Envelope(-70, -68, -32, -34)))
    .Add(Expression.Not(SpatialExpression.Contains("Boundaries", new Point(-70.40, -33.24))))
    .List();

Using ActiveRecord:

Town[] towns = Town.FindAll(
    SpatialExpression.Filter("Boundaries", new Envelope(-70, -68, -32, -34)),
    Expression.Not(SpatialExpression.Contains("Boundaries", new Point(-70.40, -33.24)))
);

The previous example just shows how to combine a spatial criterion (Contains) with a normal criterion (Not), but in this case we could use simply Disjoint.

Get states boundaries grouping counties by state:

Using ActiveRecord:

ProjectionQuery<County> query = new ProjectionQuery<County>(
    Projections.ProjectionList()
        .Add(Projections.GroupProperty("State"))
        .Add(SpatialProjections.Union("Boundaries"))
    );
IList<object[]> stateBoundaries= query.Execute();

Note: For people with a GIS backgroud, the "projection" term could be confusing. In this context, it has nothing to do with cartographic projections. It's rather a term borrowed from relational algebra.

Create a new vehicle GPS position:

Using NHibernate:

public void TrackVehicule(Vehicle vehicule, double longitude, double latitude, DateTime when)
{
    Tracking tracking = new Tracking();
    tracking.Vehicle = vehicle;
    tracking.Position = new Point(longitude, latitude);
    tracking.When = when;
    session.Save(tracking);
}

More, please!

You also will find lots of sample usage code in the tests project (Tests.NHibernate.Spatial). Check out:

CriteriaFixture.cs
ProjectionsFixture.cs
OgcSfSql11Compliance/ConformanceItemsFixture.cs
RandomGeometries/SpatialQueriesFixture.cs

UPDATED WIKI: Home

rstuven — Wed, 13 Jun 2007 18:44:37 GMT

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OpenGIS specifications.
Dialects: MsSqlSpatial and PostGIS are supported. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. insert rows into geometry columns metadata table).

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll and GeoAPI.dll

Configuration and mapping

Sample usage

UPDATED WIKI: Home

rstuven — Mon, 04 Jun 2007 20:42:49 GMT

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OpenGIS specifications.
Dialects: MsSqlSpatial and PostGIS are supported. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. insert rows into geometry columns metadata table).

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll and GeoAPI.dll

Configuration and mapping

Sample usage

UPDATED WIKI: Home

rstuven — Sun, 03 Jun 2007 17:23:27 GMT

NHibernate.Spatial, Spatial extensions for NHibernate , allows you to connect NHibernate to a spatially enabled database and manipulate geometries in HQL or in .NET code using NetTopologySuite, providing you with a fully integrated GIS programming experience.

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OpenGIS specifications.
Dialects: MsSqlSpatial and PostGIS are supported. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. insert rows into geometry columns metadata table).

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll and GeoAPI.dll

Configuration and mapping

Sample usage

UPDATED WIKI: Home

rstuven — Wed, 30 May 2007 20:49:30 GMT

NHibernate.Spatial, Spatial extensions for NHibernate , allows you to connect NHibernate to a spatially enabled database and manipulate geometries in HQL or in .NET code using NetTopologySuite, providing you with a fully integrated GIS programming experience.

Features:

Geometry types: Geometry columns are mapped to .NET geometry types compliant with OpenGIS specifications.
Dialects: MsSqlSpatial is currently supported and PostGIS is in the works. The most common spatial functions are registered for use within HQL, providing compatible queries among different dialects.
Criteria: spatial relations functions such as Intersects, Within, Crosses, etc.
Projections: spatial aggregate, analysis and tranformation functions.
Schema generation: Support for automatic creation and droping of auxiliary data objects (eg. insert rows into geometry columns metadata table).

Requirements:

.NET 2.0
NHibernate 1.2

Installation:

Download latest sources and build. Copy the binaries to your project's libraries folder.
In you project, add references to NHibernate.dll, NHibernate.Spatial.dll, NetTopologySuite.dll and GeoAPI.dll

Configuration and mapping

Sample usage

UPDATED WIKI: Configuration and mapping

rstuven — Wed, 30 May 2007 19:14:39 GMT

Dialect Configuration:

In the NHibernate section of your configuration file add the following entry:

<property name="hibernate.dialect">NHibernate.Spatial.Dialect.SomeSpatialDialect,NHibernate.Spatial</property>

If you're using Castle ActiveRecord, the entry will look like this:

<add key="hibernate.dialect" value="NHibernate.Spatial.Dialect.SomeSpatialDialect,NHibernate.Spatial" />

Replace SomeSpatialDialect by the spatial dialect to be used. For example, MsSqlSpatialDialect.

Schema Generation Configuration:

Declarative: Use of <database-object> element is not supported yet.
Programmatic:

    Configuration cfg = new Configuration();
    // Your configuration code (eg. cfg.Configure(); )
    cfg.AddAuxiliaryDatabaseObject(new SpatialAuxiliaryDatabaseObject(cfg));

Then you can use a SchemaExport object or the hibernate.hbm2ddl.auto configuration property for schema generation.

NHibernate mapping:

In the XML mappings file, map all properties as usual but for geometry columns use the following entry:

<property name="Geometry" column="the_geom" type="NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial" />

Optionally, for schema generation and default values setting, you can use type parameters. The available parameters are srid and subtype. For example:

<property name="Geometry" column="the_geom">
    <type name="NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial">
        <param name="srid">4326</param>
        <param name="subtype">POLYGON</param>
    </type>
</property>

In the mapped class, declare the corresponding property:

private GeoAPI.Geometries.IGeometry _geometry; 
public virtual GeoAPI.Geometries.IGeometry Geometry
{
	get
	{
		return this._geometry;
	}
	set
	{
		this._geometry = value;
	}
}

ActiveRecord mapping:

private GeoAPI.Geometries.IGeometry _geometry; 
         
[Property("the_geom", ColumnType = "NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial")]
public virtual GeoAPI.Geometries.IGeometry Geometry
{
	get
	{
		return this._geometry;
	}
	set
	{
		this._geometry = value;
	}
}

NOTE: Type parameters (see NHibernate mapping above) are not supported in ActiveRecord.

ActiveWriter mapping:

Drag & drop a MsSqlSpatial table from Server Explorer/Data connections.
In the model, select "the_geom" property.
In the properties window, enter the following values:

Property	Value
Column Type	Custom
Custom Column Type	NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial
Custom Member Type	GeoAPI.Geometries.IGeometry

NOTE: Type parameters (see NHibernate mapping above) are not supported in ActiveRecord, so it is in ActiveWriter.

UPDATED WIKI: Configuration and mapping

rstuven — Wed, 30 May 2007 19:10:57 GMT

Dialect Configuration:

In the NHibernate section of your configuration file add the following entry:

<property name="hibernate.dialect">NHibernate.Spatial.Dialect.SomeSpatialDialect,NHibernate.Spatial</property>

If you're using Castle ActiveRecord, the entry will look like this:

<add key="hibernate.dialect" value="NHibernate.Spatial.Dialect.SomeSpatialDialect,NHibernate.Spatial" />

Replace SomeSpatialDialect by the spatial dialect to be used. For example, MsSqlSpatialDialect.

Schema Generation Configuration:

Declarative: Use of <database-object> element is not supported yet.
Programmatic:

    Configuration cfg = new Configuration();
    // Your configuration code (eg. cfg.Configure(); )
    cfg.AddAuxiliaryDatabaseObject(new SpatialAuxiliaryDatabaseObject(cfg));

Then you can use a SchemaExport object or the hibernate.hbm2ddl.auto configuration property for schema generation.

NHibernate mapping:

In the XML mappings file, map all properties as usual but for geometry columns use the following entry:

<property name="Geometry" column="the_geom" type="NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial" />

Optionally, for schema generation and default values setting, you can use type parameters. The available parameters are srid and subtype. For example:

<property name="Geometry" column="the_geom">
    <type name="NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial">
        <param name="srid">4326</param>
        <param name="subtype">POLYGON</param>
    </type>
</property>

In the mapped class, declare the corresponding property:

private GeoAPI.Geometries.IGeometry _geometry; 
public virtual GeoAPI.Geometries.IGeometry Geometry
{
	get
	{
		return this._geometry;
	}
	set
	{
		this._geometry = value;
	}
}

ActiveRecord mapping:

private GeoAPI.Geometries.IGeometry _geometry; 
         
[Property("the_geom", ColumnType = "NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial")]
public virtual GeoAPI.Geometries.IGeometry Geometry
{
	get
	{
		return this._geometry;
	}
	set
	{
		this._geometry = value;
	}
}

ActiveWriter mapping:

Drag & drop a MsSqlSpatial table from Server Explorer/Data connections.
In the model, select "the_geom" property.
In the properties window, enter the following values:

Property	Value
Column Type	Custom
Custom Column Type	NHibernate.Spatial.Type.GeometryType, NHibernate.Spatial
Custom Member Type	GeoAPI.Geometries.IGeometry