Vector Data Sources

<< Click to Display Table of Contents >>

Navigation:  Spatial Data Sources >

Vector Data Sources

Vector data sources are used to access vector spatial data (points, lines, polygons, etc.). See the following sections for information on the various types of vector data sources that are supported.

JMap ADF / E00 Arc / Info reader

JMap KML reader

JMap Spatial Table

JMap CSV reader

JMap MID / MIF reader

MySQL Spatial

JMap DGN V7 / V8 File reader

JMap SHP reader

Oracle Spatial / Locator

JMap DWG / DXF reader

JMap TAB reader

Personal geodatabase (ESRI)

JMap EDIGEO reader

Annotations in a database

PostGIS

JMap File geodatabase (ESRI) reader

ArcGIS REST

SQL Server Spatial

JMap GeoJSON reader

ArcSDE geotadabase (ESRI)

WFS Server

JMap GML reader

Coordinates in a database

WKB or WKT in a database

JMap GPX reader

Enterprise geodatabase (ESRI)

 

JMap IFC reader

JMap Server

 

Attributes

When configuring a vector spatial data source, you need to configure attributes for the data source. All available attributes are listed in a table. By default, all attributes are included but some attributes can be excluded, in which case they will be completely ignored by JMap Server. It is also possible to specify for which attributes JMap Server should create an index in order to optimize performances when queries are performed on these attributes (if no index is used, this will not affect map download and display times). These indexes are used when performing attribute queries on these fields.

This section also contains settings to configure external attributes. See External Attributes for more details on this topic.

Attributes

Key attribute

A key attribute is used when JMap must establish relationships between certain data and your spatial data. It is important to choose an attribute whose values will never change. If you do not need this parameter, you can keep the default value.

Include

Included attributes are processed by JMap Server. They can be used in reports, to produce thematic maps, for labeling, etc. Excluded attributes are totally ignored by JMap Server. By default, all available attributes are included.

Indexed

JMap Server can create an index on an attribute to speed up queries that will use this attribute. If you plan to use an attribute for attribute queries, this attribute should be indexed, especially if the data source has a lot of elements.