[fdo-users] TF.NET (Topology Framework .NET)

[Orest Halustchak]

Hi Maksim,

This looks very interesting. Thanks for forwarding this to the list!

Orest.

-----Original Message-----
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Maksim Sestic
Sent: Tuesday, February 12, 2008 5:38 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] TF.NET (Topology Framework .NET)


Hi everyone,

TF.NET (Topology Framework .NET) represents a topology manipulation API
capable of handling managed objects representation of topological entities
based on other popular APIs, exposing it's JTS-based common topology
manipulation core to them.

JTS Topology Suite is, in fact, an API providing spatial object model and
fundamental geometric functions, providing a complete, consistent, robust
implementation of fundamental 2D spatial algorithms. It implements geometry
model defined in the OpenGIS Consortium Simple Features Specification for
SQL. JTS port for .NET was named NetTopologySuite (NTS), and is fully
conformant to Microsoft .NET 2.0 specification. NTS extends JTS with
numerous coordinate transformation and other functions, while TF.NET extends
NTS further, including additional IO functions and generic classes related
to geometry graphs. Recent TF.NET additions were also related to porting JCS
Conflation Suite to .NET.

Supported external managed APIs include:

- OSGeo Feature Data Objects (FDO) geometries
- OSGeo MapGuide Server (FDO-based) geometries
- Autodesk ObjectARX geometries (a.k.a. entities)

TF.NET project is hosted on Google Code:  http://code.google.com/p/tf-net/
http://code.google.com/p/tf-net/

It's free for download via Google Code SVN, licensed under GNU LGPL.

TF.NET Reader/Writer for FDO
A reader/writer for geometric primitives exposed by OSGeo FDO. Although FDO
relays on it's own (well, provider-based) spatial filters, there are
situations when they are simply not enough - most often FDO providers don't
expose necessary spatial filtering by design. On the other hand, you can use
rich JTS API to perform targeted geospatial analysis and bounce results back
to FDO datastore or wherever you like (say, DWG drawing).

For more info see TF.NET Reader/Writer for FDO wiki page:
http://code.google.com/p/tf-net/wiki/FdoReaderWriter
http://code.google.com/p/tf-net/wiki/FdoReaderWriter

I hope this managed supplement to FDO will help .NET developers starting
with GIS to better understand things we're all dealing with here :-)

Regards,
Maksim Sestic
--
View this message in context: http://www.nabble.com/TF.NET-%28Topology-Framework-.NET%29-tp15430622s18162p15430622.html
Sent from the fdo-users mailing list archive at Nabble.com.

_______________________________________________
fdo-users mailing list
fdo-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-users