Version 2.1.0

Support for GeoPackage export GeoServer

Bridge can now use GeoPackage instead of using Shapefile to publish your data to GeoServer. Bridge can publish GeoPackage to either a GeoPackage datastore or a PostGIS datastore. Requires the GeoPackage extension for GeoServer to be installed on your GeoServer.

User layer name as OWS title

Optional; use the ArcMap TOC layer name for the OWS title in GeoServer and MapServer instead of the metadata title. Enable this option in the Bridge.config file by setting ArcLayerNameAsOWSTitle.

Set a user-agent string for the HTTP client

Optional; set a user-agent for all the HTTP request in Bridge. Configure this option in the Bridge.config file by setting a value for HTTPUserAgent.

Bugfix for error in PostGIS layer deletion

Bridge did not remove GeoServer PostGIS layers correctly from GeoServer, making it impossible to republish the layer to GeoServer after deletion.

Bugfix for error when importing a configuration database

Message of error was "ProxyServers.Host may not be NULL".

  • Release Notes
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Version 2.0.1

GeoCat Bridge 2.0.1 Bugfix for postgis datastore creation Bugfix for label classes...

Version 2.0.2

GeoCat Bridge 2.0.2 Configure default getfeatureinfo templates [MapServer] Support...

Version 2.0.3

GeoCat Bridge 2.0.3 Test GeoNetwork connection now checks credentials of connection Fix...

Version 2.0.4

Support for OracleNG datastores in GeoServer Publish Oracle SDE layers from ArcMap directly to...

Version 2.0.5

Support for transparency on pattern fill style Pattern file styles for MapServer support for...