WKB or WKT in a database

Read	Yes
Write	Yes

JMap Server can connect to databases containing geometries that have been coded according to WKB and WKT standards (http://en.wikipedia.org/wiki/Well-known_text).

In addition to the column containing the geometry, you must have a number column with unique integer values used as element identifiers. There must also be 4 columns containing the values of minimum bounding rectangles (MBR).

An SQL query must be provided. The query will be launched to read the data and it can access more than one table at a time.

The connection to the database must already be configured. Refer to the section Creating Databases for more information on this topic.

Database	Select the database from which the data must be read. This database must already be configured in JMap Admin.
SQL query	Enter the SQL query used to extract geometries and attributes from the database.
Geometry table	Select the physical table containing the geometries. Clicking on Load displays the list of fields returned by the query. This action is required to proceed with the configuration.
Geometry field	Select the field containing the geometries.
Geometry type	Select the format of the data to read, either WKB or WKT.
Encoding (for WKB only)	If the data format is WKB, you must indicate the type of coding used by the data: Little Endian or Big Endian.
MBR X1	Minimum X value of the minimum bounding rectangle (MBR) in the geometry.
MBR Y1	Minimum Y value of the minimum bounding rectangle (MBR) in the geometry.
MBR X2	Maximum X value of the minimum bounding rectangle (MBR) in the geometry.
MBR Y2	Maximum Y value of the minimum bounding rectangle (MBR) in the geometry.
Id field	Select a field that contains unique identifiers. Only the fields containing whole numbers are listed.
Creation time field	(Optional) If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained.
Modification date field	(Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained.
Author field	(Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change. If no field is selected, the data can still be edited, but this information will not be maintained.