MapDotNet UX Help

Now that you have determined whether to work in Studio Engine or connect to MapDotNet UX Web Services, begin connecting to your spatial data sources by clicking on the icon that looks like a plus with a clipboard.

Keep in mind that a spatial data source connection is always associated with your Local System or with a specific server.  If you add a data source while working in Engine mode, for example, you will have to re-add that source if you later decide to connect to a server instance.  That said, you may connect to any supported data source to which you have local or network access.

The supported data sources are:

  • Microsoft SQL Server 2008 R2, SQL Azure, and SQL Sever 2012
  • Shapefiles
  • PostGIS
  • ESRI ArcSDE 9.x and 10.x
  • KML files
  • MapInfo TAB

Note: Oracle Spatial on 64-bit systems is not currently supported in MapDotNet UX 8 and 9 due to the lack of Oracle support for .NET 4.0.

Making the connection to your tables and shapefiles is a snap.  Once you click the Add Data Source icon, follow the Add Data Source dialogue to access spatial data.

Connect To Microsoft SQL Server 2008 or 2012

First specify the name of your data source as you would like it to appear in the Data Sources list and select the data source type.

The Connection String will autocomplete as you fill the Data Source, User ID, Password and Initial Catalog boxes.

In order to connect to a SQL Server data source you must have SQL Server 2008 or 2012 installed on your machine (or on a network machine to which you have access).  Visit http://www.microsoft.com/en-us/sqlserver/default.aspx for more on the preferred data source of MapDotNet UX.

Connect To PostGIS

First specify the name of your data source as you would like it to appear in the Data Sources list and select the data source type.

The Connection String will autocomplete as you fill the User, Password, Database, Server and Port boxes.

In order to connect to a PostGIS data source you must have PostgreSQL with the PostGIS extension installed on your machine (or on a network machine to which you have access).  PostgreSQL/PostGIS is open source software. Download PostgreSQL at http://www.postgresql.org/ and, upon installation, choose to add PostGIS from the application stack builder.

Connect To ESRI ArcSDE

First specify the name of your data source as you would like it to appear in the Data Sources list and select the data source type.

The Connection String will autocomplete as you fill the Server, Service, Database, Username and Password boxes.

In order to connect to an ArcSDE™ data source you must have the ArcSDE™ client software from ESRI installed on your machine (or on a network machine to which you have access).

Connect To Shapefiles

First specify the name of your data source as you would like it to appear in the Data Sources list and select the data source type.

The Connection String will autocomplete as you fill the Path box.  Note that Path is optional if you are using the default location for your server instance, and password is only needed if the server instance is configured to require one.

There is no special software required to connect to shapefiles.

Connect To KML files


First specify the name of your data source as you would like it to appear in the Data Sources list and select the data source type.

The Connection String will autocomplete as you fill the Path box.  Note that Path is optional if you are using the default location for your server instance, and password is only needed if the server instance is configured to require one.

There is no special software required to connect to KML files.

The KML connector extracts Placemark objects.  KML files have no geometry type constraints.  When adding a map layer using KML data, you will be prompted to select a geometry type and may need to filter your data appropriately.

The following are available as queryable columns and may be used in layer where clauses:

  • GeometryIndex - 0-based index into the set of placemarks (order is the same as the original file)
  • name, description - sub-elements of a Placemark element
  • Folder - represents Folder elements containing the placemark as follows:
    • The Folder's <name> sub-element is used as the folder name.  Folders without a name are ignored.  The Placemarks are still read but the nameless folders are not included in the Placemark's folder path.
    • "/" is used for the folder if a Placemark has no folder.
    • "/" separates nested folders, i.e. /Polygons/Buildings
      When using a filter or where clause that tests Folder,
         Folder = '/Polygons'
      will return only Placemarks directly in the /Polygons folder, not in /Polygons/Buildings.  Use the * wildcard to include subfolders.
         Folder = '/Polygons/*'
      will return Placemarks from both /Polygons and /Polygons/Buildings.