SQL Server (2008, 2012, or Azure) is a requirement for touchgeo. SQL Server stores the spatial and non-spatial data that you want exposed in touchgeo for record creation, updating or deleting. Touchgeo supports different types of spatial data (points, lines and polygons) and requires the use of the Geometry data type in SQL.
In touchgeo each item in the layer/legend list corresponds to a single table in SQL Server. If you're optionally using CRM, the item in the layer/legend list corresponds to a SQL table and a CRM Entity.
The following steps show you how to create a new SQL table for use in touchgeo.
SQL Server (2008, 2012, or Azure)SQL Server Management StudioMapDotNet UX Studio
Step 1 - Create a new table
There are two options for creating your tables. With either option, it is important to ensure that you have spatial index properly set and constraints related to the spatial information applied.
The first option is to use MapDotNet UX Studio.
In MapDotNet UX Studio, right click on a SQL data source and click add new table. Adding a new table will create a new table with two columns (GeometryItem and GeometryIndex) as well as set the appropriate constraints.
The second option is to run the SQL queries manually.
Step 2 - Add any additional columns that you want to make available in touchgeo
If you're only using SQL Server for touchgeo, all data columns will be set up in SQL Server. If you are using CRM, you don't need to replicate every field that you've set up in CRM. At a minimum, you will need one additional column in your table that can be used as a primary identify column. The primary identifier column is use to display information text in the call out.
Next step - Configure the meta data for your .mapx file
The MapDotNet map file (.mapx) stores most of the configuration information that touchgeo needs in order to know which tables and fields are exposed to the user in the HTML5 app for editing. This section contains descriptions of the meta data key value pairs needed in touchgeo.