Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Provides a means of displaying attribute information spatially related to the currently selected entities.

...

com.cohga.html.client.map.selectionIdentify

weave.selectionIdentify

Note: there is also a selectionIdentify2 version of this tool that fetches data from the server in batches, 4 entities at a time, which can start returning data to the user quicker that this original version. This version fetches all the data at once which can take a long time to display anything to the user.

Sub-tags

Name

Type

Cardinality

Default

Description
i18n Resource

label

String

0..1


Label to display as button text

entity

entity

0..n


Optional list of entities to refine/sort the entity list

defaultEntity

String

0..1


The id of the entity to have displayed first

windowTitle

String

0..1

Selection Identify

The title of the popup window

weave.selectionIdentify.window.title

windowWidth

Integer

0..1

800

The width of the popup window

windowHeight

Integer

0..1

500

The height of the popup window
useVisibleEntitiesBoolean0..1falseUse just the entities that are visible (based on ToC)
tooltip\titleString0..1Selection IdentifyThe title for the tooltipweave.selectionIdentify.tooltip.title
tooltip\textString0..1Identify features that intersect the current selectionThe text for the tooltipweave.selectionIdentify.tooltip.text
bufferDistanceNumber0..10Distance to buffer around selection before doing intersection operation
bufferUnitsString0..1mUnits for the bufferDistance value
bufferCrsString0..1CRS of mapCoordinate reference system to use when performing the buffer generation
spatialOperationString0..1intersectwhat What type of spatial operation should be used INTERSECT, OVERLAPS, CONTAINS or WITHIN
includeActiveBoolean0..1falseShould the source entity type also be returned in the results?
ignoreScaleBoolean0..1falseShould the current scale be ignored when determining which entities to check?
entityListWidthInteger0..1200The initial width of the entity list. Only available from 2.5.28.
entityListWidthMinInteger0..1175The minimum width of the entity list. Only available from 2.5.28.
entityListWidthMaxInteger0..1400The maximum width of the entity list. Only available from 2.5.28.
include


List of entities that the tool should be enabled for. Only available from 2.6.4
exclude


List of entities that the tool should not be enable for. Only available from 2.6.4

Notes:

Only one of include or exclude should be used, and they can be specified in multiple ways:

  1. As a comma separated value - quick and easy when specifying entities by hand.
    1. <include>property,reserve</include>
    2. <exclude>lga,suburb</exclude>
  2. As individual entries - useful when setting based on user attributes
    1. <include>property</include><include>reserve</include>
    2. <exclude>lga</exclude><exclude>suburb</exclude>
  3. As a sub-list - useful when using a snippet
    1. <include><entity>property</entity><entity>reserve</entity></include>
    2. <exclude><entity>lga</entity><entity>suburb</entity></exclude

Entity

Name

TypeRequired

Cardinaltiy

Description

id

stringyes

1..1

The unique entity id for this entity

minScale

numberno

0.1

Min zoom scale for this entity to be reported for

maxScale

numberno

0..1

Max zoom scale for this entity to be reported for

isDefault

booleanno

0..1

Set this entity as the default (alternative to defaultEntity above)

datastring0..nA list of the data definition that should be available for the entity


Info

See Common grid panel configuration options for other grid related options.


Code Block
languagexml
titleExample of tools configuration
					<item action="weave.selectionIdentify" useVisibleEntities="true" ignoreScale="true">
						<!-- disable the tools if lga or suburbs is the active entity -->
						<exclude>
							<entity>lga</entity>
							<entity>suburbs</entity>
						</exclude>
						<!-- 
						the above could also be specified as 
						    <exclude>lga,suburb</exclude>
						-->

						<!-- which entities should be interrogate -->
						<entities>
							<entity id="property" maxScale="12000">
								<data>property_details</data>
								<data>property_spatial</data>
								<data>property_owners</data>
							</entity>
							<entity>roads</entity>
							<entity>suburbs</entity>
							<entity>council_buildings</entity>
						</entities>
					</item>