URL |
The full JDBC connection string for connecting to the MySQL database.
Example: jdbc:mysql://<host>:<port>/<database>
Note: The Database name must be included in either the URL or database parameter.
|
Username |
The username for the MySQL database. |
Password |
The password for the MySQL database. |
Database |
The name of the database to connect to.
Note: Only include the database name if it is not part of the URL you have provided.
Note: The Database name must be included in either the URL or database parameter.
|
Coordinate reference system |
This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data, if it cannot be deduced automatically.
This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined).
Note: Coordinate Reference System parameters are required in a session that will write data to Oracle.
See Coordinate Reference System for more information on when this is required.
|
Allow invalid geometries |
Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported.
This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.
|
Fix ring direction and inclusion errors |
Polygon rings are assumed to be encoded using the right-hand rule, i.e. outer rings are anti-clockwise and inner rings are clockwise.
If the service does not guarantee that encoding, then set this flag to have polygon rings automatically oriented on import to avoid later problems when processing the data.
Note: This requires a small amount of additional processing so only set if the ring direction is not guaranteed.
|