In order to use the Geography data from your tables properly I suggest you follow the steps described in our How to: Work with Special Data documentation section.
You could find an example of our Special Data support at the Basic Special Data with OpenAccess ORM example in the WPF section of our Sample Kit. Also you could take a look at this blog post demonstrating how to integrate an OpenAccess ORM model containing Special Data with the WPF RadMap.
Please bear in mind that if you don't include your Geometry property in the fetch strategy of the context instance of the repository for your Special Data tables, you will get a Null value after detaching the entities.
For example if you need to get the Geometry property of the Location entity from our Basic Special Data with OpenAccess ORM example using Web API service you will need to add the following code in its repository - please find an example result of the service call in the attached image:
.fetchStrategy.LoadWith<Location>(l => l.GeoLocation);
If you still experience the same issues after applying these steps, could you please provide us with more details about the steps for reproducing this issue. Also a sample application demonstrating the problematic behavior will be highly appreciated.
I am looking forward to your feedback.
OpenAccess ORM Q2 2013 brings you a more powerful code generation and a unique Bulk Operations support with LINQ syntax. Check out the list of new functionality and improvements shipped with this release.