RAMP Configuration Migration Guide
Canada Goose to Dragonfly
A number of schema changes were made to the config file in the Dragonfly release of RAMP. Most of the changes were to facillitate a smaller config file, and to have data in more obvious locations.
Also note that a number of fields are now optional. If they are not present in the config file, a default value will be used. The config schema will describe these fields.
Changes to Feature Layers
Feature Layer Collection
The featureLayers collection now resides under the layers node, and is called feature.
Feature UUID
The uuid field has been removed. If a RAMP application uses a uuid, the uuid should be used as the layer’s id field.
Visibility Settings
Fields layerVisible and boundingBoxVisible have been moved to the settings node of the feature layer config object. layerVisible has been renamed to visible
Templates
All template values now reside under the template node. Consequently the mapTipSettings node has been removed. The properties that contain individual template names no longer have the word Template in their name.
Symbology
The symbology section has been restructured to support different types of renderers. See the symbology guide for details on how to format it.
Changes to WMS Layers
WMS Layer Collection
The wmsLayers collection now resides under the layers node, and is called wms.
Visibility Settings and UUID
The changes to visibility settings and UUID that were applied to feature layers (see above) were also applied to WMS layers.
Removed WMS Nodes
Nodes legend, extent and layerInfo have been removed.
Removed Nodes
the levelOfDetails.levels collection has been removed.
Dragonfly to Elk
More schema changes were made to the config file in the Elk release of RAMP. This included support for new features, more defaulting, and removal of state-specifc nodes.
As always, consult the config schema for more granular details.
Changes to Top-Level Nodes
Nodes lang, spatialReference, navWidget.locale, ui and globalFilter have been removed.
Node geometryService has been renamed to geometryServiceUrl
Changes to Support Multiple Spatial References
There is no longer a notion of a map-level spatial reference. Spatial reference is now determined by the active basemap. To support all this switching, the following nodes now have spatialReference values to indicate the spatial reference of the geometry they refer to:
- objects in basemaps collection
- any extents in the extent object
- any layerExtent definition in a layers.feature object
As well, the basemap objects have a new required node called tileSchema, which indicates which tiling schema this basemap belongs to. See the basemap support page for more details.
Changes to Basemap Selector
The basemap object property showOnInit has been removed, and replaced by a root level property called initialSelectedBasemap. This property contains the integer index of the basemap that should be active when the site loads.
Basemap objects also now support showing multiple tile sets at once. The url property has been replaced with an array property called layers that contains individual objects with their own url properties
Changes to levelOfDetails Node
The levelOfDetails node has been renamed to zoomLevels.
The levels child node has been removed.
Child nodes maxLevel and minLevel have been renamed to max and min.
Changes to siteTemplate Node
The siteTemplate node has been renamed to templates.
The filterGlobalRowTemplate and filterRowTemplate child nodes have been removed.
Child node basemapTemplate has been renamed to basemap.
Changes to datagrid Node
The datagrid node (at the root, not the node embedded in each feature layer object) has been removed. Most of the values inside were not being used.
Value extendedDatagridExtentFilterEnabled has been moved to the configuration root.
Value globalGridRowsPerPage has also been moved to the root and has been renamed to rowsPerPage.
- Date modified: