| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | This page is one of the !MapGuide Community CodeSamples. Visit the CodeSamples page to view more! |
| | 4 | |
| | 5 | == Topology Framework .NET == |
| | 6 | |
| | 7 | 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. |
| | 8 | |
| | 9 | JTS 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 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. |
| | 10 | |
| | 11 | TF.NET project is hosted on Google Code: [http://code.google.com/p/tf-net/] |
| | 12 | |
| | 13 | |
| | 14 | === TF.NET Reader/Writer for MapGuide === |
| | 15 | |
| | 16 | A reader/writer for geometric primitives exposed by OSGeo MapGuide? Server. Before further reading, please see FDO Reader/Writer and Binary Predicates introductory notes (Wiki pages). Althugh MapGuide? relays on it's own (FDO-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 MapGuide? in some form (i.e. redlining, feature or spatial filter, etc). |
| | 17 | |
| | 18 | For more info see TF.NET Reader/Writer for MapGuide wiki page: [http://code.google.com/p/tf-net/wiki/MapGuideReaderWriter] |
