Topics: |
Using InfoAssist+, you can create maps to identify patterns or trends in your data. By converting data into values that can be displayed on a map, you are able to visualize scenarios, illustrate hot spots, and identify potential problem areas. For example, a law enforcement agency may use mapping functionality to identify areas of higher crime within the locations they cover. You can also use maps to determine how places are related, understand where things are located, and identify the best actions to take. By illustrating trends on a map, a decision maker can identify patterns easily, and reach conclusions sooner.
An early example of how maps can be used to illustrate trends is the case of Dr. John Snow, an epidemiologist who was one of the first to use data to map occurrences of cholera to find the cause of infection. By plotting the cholera data on a map of a town, Dr. Snow was able to visualize a trend that showed higher incidences of cholera closest to water pumps. This example is shown in the following image.
Maps also allow you to measure size, shape, and distribution to detect and quantify patterns, and even perform predictive analytics. An example of how maps can help detect and quantify patterns is the scenario in which a state agency used a WebFOCUS mapping application to solve a problem with their food stamp system. Using this application, odd food stamp redemptions, such as rounded numbers transactions, were discovered. By plotting those transactions on a map, the agency discovered that the redemptions appeared in the same geographic location. Upon further investigation, the agency identified that individuals were selling their food stamps at reduced prices, $50 worth of food stamps for $40 in cash, to others instead using them as intended. This map example is shown in the following image.
When working with maps, the concepts of location intelligence and business intelligence are important to understand. A Geographic Information System (GIS) captures, stores, analyzes, manages, and presents data linked to a location, while Business Intelligence (BI) relies on the conversion of raw data into meaningful information. Location intelligence is the process of analyzing data to make better business decisions. It combines GIS and BI/Analytics to allow the recognition of patterns in your data, including the visualization and discovery of geospatial outliers, which would not be easily discovered if you use the technology independently and separately.
More specifically, maps use non-intrusive GIS workflows with existing data. You can view symbol layers for data bound to a geo-location, such as state, country, and ZIP code, in an integrated map viewer. Using metrics from your data, you can also visualize geographic roles or dimensions. Geographic roles, or dimensions, can be built directly into your Metadata or assigned to a data field when you create a map.
Using WebFOCUS InfoAssist+ with the Esri integration, you can create maps that help you illustrate or identify trends, so that you can take action quickly. WebFOCUS architecture provides the framework in which this system operates. Using a Javascript map viewer, you can navigate the interface easily, as shown in the following image.
In addition, this integration utilizes the capabilities of Esri by leveraging the ArcGIS Javascript API and content. Specifically, you can integrate data into maps with published content in ArcGIS Online platform. For more information, see http://www.esri.com/software/arcgis/arcgisonline. Additionally, by using this integration, you can include information about demographics, spending habits, crime, and lifestyle to maps that contain your data. These maps include layers with extensive demographic or reference detail and topography and allow you to view information about people, businesses, climate, and much more.
You can create the following maps in InfoAssist+:
Both maps can be created in Chart or Visualization mode. Built-in zooming capabilities allow you to drill down to a specific geographic area of focus easily. This allows you to get a closer look at regional or local data, draw inferences, and make recommendations, without changing the initial view of your data.
In Chart mode, you can also use the Auto Drill and Auto Linking features that are available when you create charts or reports in InfoAssist+. In Visualization mode, you can also drill up and down within different levels in a data hierarchy in a map. Auto Drill allows you to navigate through the geographical hierarchy of your map data at run time. You can use this information to visualize the same measure at different geographical hierarchies, such as Countries to States and States to Cities. Auto Linking allows you to connect to related charts or reports in your environment that share similar data parameters.
Using the Esri integration in InfoAssist+, you can also add the following layers to your map:
When you apply a Background to your map, its appearance changes. You can then adjust the view of your data, showing different terrain or geographical views. Backgrounds provide at least 17 levels of zoom. For more information, see https://developers.arcgis.com/javascript/jsapi/esri.basemaps-amd.html.
Both mapextent and the Layers menu functionality are applied to your map when you select a Background, Reference Layer, or Demographic Layer. Mapextent is an automatic view of the map. Layers is a menu that appears on the map and provides access to options that allow you to adjust the information that is being displayed.
The map example in the following image shows the use of layers.
Note: Backgrounds, Demographic Layers, and Reference Layers can be accessed from the Format tab for maps in both Chart and Visualization mode. These layers are static, standard options that Esri provides for use with InfoAssist+, and do not change based on the data source that you select.
The Esri On Premise functionality enables you to download and access mapping files through the use of a local Application Programming Interface (API). Once you download and configure the API, you do not need an internet connection to utilize the robust mapping features that Esri provides. For information on downloading and configuring the API that controls this feature, see How to Download and Configure the ArcGIS JavaScript API.
The Ersi On Premise functionality provides you with local access to Esri mapping files. This is particularly useful if you are away from your office or without an Internet connection. You may also be using a mobile device, such as an iPad or smartphone with a large screen, without an Internet connection. The following mapping components are supported when using the Esri On Premise functionality:
Note: Demographic Layers are not supported in an Esri On Premise environment.
You can use this procedure to download and configure the API that controls the Esri On Premise environment.
Note: This is the path to which you extracted the API files.
This field identifies the path to the internal ArcGIS Javascript API Source that develops ESRI-based maps. This setting is blank, by default, indicating that the use of the internal API source to develop ESRI maps is not activated. The API that is referenced is https://js.arcgis.com/3.15/, by default. To direct WebFOCUS to use the internal ArcGIS Javascript API to develop ESRI maps, enter the path to the local API files that you extracted into this setting. For more information, see the WebFOCUS Security and Administration manual.
Note: This path should be a relative path that is accessible within the local WebFOCUS install.
In both files, search for HOSTNAME_AND_PATH_TO_JSAPI. Replace '//' + "[HOSTNAME_AND_PATH_TO_JSAPI]dojo" with '//' + HOSTNAME_AND_PATH_TO_JSAPI + "dojo"
The following procedures provide step-by-step instructions on how to create and customize maps.
As you create your maps, you can use the following built-in map viewer features:
Note: The default option of creating a map utilizes the ArcGIS Javascript API that Esri provides.
A blank map displays and the Layer field container is enabled, as shown in the following image.
This field, which already has a geographic role assigned, is denoted with a Layer icon, , in the Data panel, as shown in the following image. You can also hover over a data field to view the geographic role assignment.
For more information, see Geographic Roles.
The canvas refreshes, and your map displays.
A blank map displays and the Layer field container is enabled.
This field, which already has a geographic role assigned, is denoted with a Layer icon, , in the Data panel, as shown in the following image. You can also hover over a data field to view the geographic role assignment.
For more information, see Geographic Roles.
A basic bubble map displays, as shown in the following image.
The Map dialog box displays, as shown in the following image.
Note: When specifying a geographic role, you can use Name or an ISO-2 value for countries. The ISO-2 codes are recognized worldwide, as published in http://www.iso.org/iso/country_codes
The Map dialog box refreshes and shows the Depends on section, as shown in the following image.
Note: If you used the Map As option, the Depends on section automatically displays, since a geographic role was selected at that time.
The Geographic Role field automatically populates based on the hierarchy of your data source. For example, if your primary geographic role was State, and in your metadata hierarchy, State depends on Country, this option displays.
A basic map displays, as shown in the following image.
You can change the geographic role assignment of any geolocation field using the following steps.
The Map dialog box displays using the selected Geographic Role.
Note: This changes the selection that you made on the Map As list.
The geographic role changes for the selected Geolocation field in the Data pane, and the map refreshes using the new geolocation that you specified.
Note: The Imagery with Labels Background provides the terrain for your map, ranging from land contours to city streets.
Once you make a selection, the background of the map refreshes. You can continue to change your background until it displays the desired information.
Note: These are pre-defined demographic profiles, provided by ArcGIS. You can select multiple options in either category to gain additional insight into your data. Specifically, each Demographic Layer has its own profile and provides a layering option, when comparing values across different layers or profiles.
The Demographic Layers that you select are applied to your map. The map engine displays the different groups with unique hues and coloring. You can use the Table of Contents or Layers option, to toggle between the different layers that you have specified. The Layers option is shown in the following image.
Note: You can select and clear the check boxes to enable the display of one or more Demographic Layers to compare and contrast the different demographic scenarios.
The Reference Layers dialog box displays, as shown in the following image.
Your map refreshes, and the definitions and borders of the References Layers display on the canvas. You can use the Table of Contents or Layers option, to toggle different Reference Layers in your map. These options are shown in the following image.
This section presents the Query field containers that display for both charts and visualizations, by map type.
Query field container |
Chart mode |
Visualization mode |
||
---|---|---|---|---|
Choropleth Map |
Proportional Symbol Map |
Choropleth Map |
Proportional Symbol Map |
|
Layer. One data field, specifically a field containing location data (for example, State). |
|
|
|
|
Color. One data field. |
|
|
|
|
Tooltip. Up to one data field (not required). |
|
|
|
|
Multi-graph. Up to one data field (not required). |
|
|
|
|
Size. One data field. |
|
|
|
|
This section contains information on the geographic roles that are supported for Esri maps in InfoAssist+.
Geographic Role |
Description |
Maps Supported |
---|---|---|
POINT OF INTEREST |
Points of Interest |
Proportional Symbol |
CITY |
World Cities |
Proportional Symbol |
CONTINENT |
World Continents |
Choropleth, Proportional Symbol |
COUNTRY |
World Countries |
Choropleth, Proportional Symbol |
COUNTRY_ISO2 |
World Countries (ISO2 Code) |
Choropleth, Proportional Symbol |
COUNTRY_ISO3 |
World Countries (ISO3 Code) |
Choropleth, Proportional Symbol |
STATE |
World Admin Divisions |
Choropleth, Proportional Symbol |
STATE_ISO_SUB |
World Admin Divisions (by ISO_SUB) |
Choropleth, Proportional Symbol |
USCITY |
USA Major Cities |
Proportional Symbol |
USCITY_FIPS |
USA Major Cities_FIPS |
Proportional Symbol |
USCOUNTY |
USA_Counties |
Choropleth, Proportional Symbol |
USCOUNTY_FIPS |
USA_Counties_FIPS |
Choropleth, Proportional Symbol |
USSTATE |
USA_States |
Choropleth, Proportional Symbol |
USSTATE_FIPS |
USA_States_FIPS |
Choropleth, Proportional Symbol |
USSTATE_ABBR |
USA_States (by abbreviation) |
Choropleth, Proportional Symbol |
ZIP3 |
USA ZIP3 |
Choropleth, Proportional Symbol |
ZIP5 |
USA ZIP5 |
Choropleth, Proportional Symbol |
The following table summarizes additional geographic role information.
Note: All of the following roles are geographic roles, with the exception of Latitude and Longitude, which are coordinates.
Role Name |
Role Format |
Geographic Role |
---|---|---|
Address |
Full |
ADDRESS_FULL |
Line |
ADDRESS_LINE |
|
City |
Name |
CITY |
Continent |
ISO-3166 code |
CONTINENT_ISO2 |
Name |
CONTINENT |
|
Country |
FIPS code |
COUNTRY_FIPS |
ISO-3166-2 code |
COUNTRY_ISO2 |
|
ISO-3166-3 code |
COUNTRY_ISO3 |
|
Name |
COUNTRY |
|
Country (NUTS level 0) |
NUTS code |
NUTS0_CC |
Name |
NUTS0 |
|
District (NUTS level 3) |
NUTS code |
NUTS3_CC |
Name |
NUTS3 |
|
Geometry area |
GEOMETRY_AREA |
|
Geometry line |
GEOMETRY_LINE |
|
Geometry point |
GEOMETRY_POINT |
|
Latitude |
LATITUDE |
|
Longitude |
LONGITUDE |
|
Postal code |
POSTAL-CODE |
|
Province (NUTS level 2) |
NUTS code |
NUTS2_CC |
Name |
NUTS2 |
|
Region (NUTS level 1) |
NUTS code |
NUTS1_CC |
Name |
NUTS1 |
|
State |
FIPS code |
STATE_FIPS |
Name |
STATE |
|
US County FIPS |
FIPS code |
USCOUNTY_FIPS |
US city |
FIPS code |
USCITY_FIPS |
Name |
USCITY |
|
US county |
Name |
USCOUNTY |
US Postal code |
3 digits |
ZIP3 |
5 digits |
ZIP5 |
|
US state |
Abbreviation |
USSTATE_ABBR |
FIPS code |
USSTATE_FIPS |
|
Name |
USSTATE |
|
US ISO subdivision code |
STATE_ISO_SUB |
The following table illustrates the geographic roles and their dependencies. Level 1 indicates the highest level of hierarchy and level 5 is the lowest level of hierarchy.
Region |
Hierarchy Level |
Geographic Role |
---|---|---|
United States |
1 |
COUNTRY, COUNTRY_ISO_CC |
2 |
USSTATE, USSTATE_ABBR, USSTATE_FIPS |
|
3 |
USCOUNTY, USCOUNTY_FIPS |
|
4 |
USCITY, USCITY_FIPS |
|
5 |
ZIP3, ZIP5 |
|
World |
1 |
CONTINENT, CONTINENT_ISO_CC |
2 |
COUNTRY, COUNTRY_FIPS, COUNTRY_ISO_CC, COUNTRY_ISO2, COUNTRY_ISO3 |
|
3 |
STATE, STATE_ISO_SUB |
|
4 |
CITY |
|
5 |
POSTAL CODE |
Customers with Enterprise Data often have map layers that represent their territories, events, or logistical information. These are published as Map Services to either a subscription based in the Esri Cloud (ArcGIS.com) or on an internal portal. This portal is available with ArcGIS Server 10.3 installations. More information can be found at http://server.arcgis.com/en/portal/.
The WebFOCUS Reporting Server comes with a configuration file (geo_services.xml) that contains elements that describe all of the geographic roles, geographic hierarchies, URLs to the map services, and base maps available to the Esri map viewer. This file is located in the catalog directory under the server home directory:
c:\ibi\srvnn\home\catalog
where nn is the release of your WebFOCUS Reporting Server. For example, 82 for version 8.2.
The geographic role selections that you can make while using the InfoAssist+ Map As option are built dynamically using this configuration file. Each role definition in the configuration file, when selected in InfoAssist+, generates Metadata and a request that is sent to Esri in order to download the appropriate map and place the markers or polygons on the map.
Note: When you run a map that has too many polygons, it fails to draw. This applies to maps that use the US Zipcode 5 layer, in particular.
A geographic role can be part of a hierarchy. For example, the World geographic role is at the top of a hierarchy that contains continents, countries, states, and cities. These hierarchies are also described in the geo_services.xml file. The default location is:
C:\ibi\srvnn\home\catalog\geo_services.xml
where nn is the release of your WebFOCUS Reporting Server. For example, 82 for version 8.2.
To add a custom geographic role, you must add the necessary parameters for the geography to this file.
A geographic role is stored as geo_role element in the geo_roles object of the geo_services.xml file. A geographic role must be defined with:
The following attributes define a geographic role.
Is an alphanumeric uppercase value, up to 50 characters, used to identify the geographic role.
Is the data type for the ID. Can be one of the following.
"text". For text data, format TXn.
Is the optional number of characters in USAGE format length (any, if not set).
Is the name of the geographic role.
Is the title of the geographic role, which displays when you hover over a data field with a geographic role assigned. You can also assign a geographic role, by title, using the Map As option.
Is an optional format for the geographic role. This is useful when the role can be referenced using multiple formats, such as a name, an ISO code, and an abbreviation.
Is an optional title for the format of the geographic role. It will be shown in parentheses along with the role title when you use the Map As option. For example, US State (abbreviation).
Is one of the following predefined role types.
Is an element that consists of a group of vocabulary elements that explicitly describe column names for the geographic role. These rules will be used to select the best geographic data for the role.
Elements in a rule are connected by the Boolean logic operation OR (only one needs to be satisfied). Each vocabulary element contains words enclosed with special characters. Words in the rule element are connected by the Boolean logic operation AND (all need to be satisfied).
A word may be prefixed and/or suffixed with the percent character (%), which is a place holder for any sequence of characters. If an element contains more than one word, each word has to be prefixed by the character plus (+) or minus (- ). Plus indicates that the word must be found in the column name. Minus indicates that the word must not be found in the column name.
The following defines the State Abbreviation geographic role. The role ID is USSTATE_ABBR. The role name is USSTATE with a role format of ABBR. The titles that show when using the Map As option are US State (Abbreviation). The format is A2, and the vocabulary rules specify that the characters state must be present, but the characters iso, capital, and population must not be present. The geo type is geography, indicating that the returned data will be a geographic area.
<geo_role id="USSTATE_ABBR" value_size="2" type="alpha" role_name="USSTATE" role_name_title="US state" role_format="ABBR" role_format_title="Abbreviation" geo_type="geography"> <vocabulary_rules> <vocabulary>+%state%-%iso%-%capital%-%population%</vocabulary> </vocabulary_rules> </geo_role>
The following is a role definition for latitude values. The role ID is LATITUDE. The role name is also LATITUDE. Its format is numeric. The title that displays when you hover over a field with a geographic role assigned (or when using the Map As option) is Latitude. The geo type is geometry, indicating that the returned data will be points or areas described using points. The vocabulary rules specify that the characters latitude must be present.
<geo_role id="LATITUDE" type="numeric" role_name="LATITUDE" role_name_title="Latitude" geo_type="coordinate"> <vocabulary_rules> <vocabulary>%latitude%</vocabulary> </vocabulary_rules> </geo_role>
The following is the definition for the city role. The ID is CITY. The role name is also CITY. Its format is NAME. The title that displays when you hover over a field with a geographic role assigned (or when using the Map As option) is City (Name). The definition has a set of vocabulary elements. Only one of the elements in the list must be true. Therefore, the characters city, or town, or country plus capital, or state plus capital must be present.
<geo_role id="CITY" type="alpha" role_name="CITY" role_name_title="City" role_format="NAME" role_format_title="Name" geo_type="geography"> <vocabulary_rules> <vocabulary>+%city%-%population%</vocabulary> <vocabulary>+%town%-%population%</vocabulary> <vocabulary>+%country%+%capital%-%population%</vocabulary> <vocabulary>+%state%+%capital%-%population%</vocabulary> </vocabulary_rules> </geo_role>
Some geographic roles exist as part of a hierarchy, and the data for the hierarchical roles are stored at the same map services endpoint (URL). Hierarchical role relationships are stored as hier elements in the geo_services.xml file.
Hierarchy definitions provide WebFOCUS with the information needed to use Auto Drill from a geographic role at a higher level of the geographic hierarchy to a geographic role at a lower level of the geographic hierarchy.
Each hierarchy has the name of hierarchy (attribute ID) and a group of LEV elements with the attributes level, geo_role, and, optionally, value. Not all defined roles can be used in hierarchies. The same role can be included in more than one hierarchy and may be on different hierarchical levels in each. However, the same role cannot be used more than once in the same hierarchy. Multiple geographic roles can be assigned to the same hierarchical level in a hierarchy.
Geographic hierarchies are defined with the following attributes:
Is a name of up to 50 alphanumeric characters used to identify the hierarchy.
Is a natural number (integer starting with 1 for the top level) that specifies the level of the role within the hierarchy.
Is the ID attribute of a geographic role (geo_role element).
Is an alphanumeric value, up to 50 characters, predefined for this geo role in this hierarchy.
The following element defines the world hierarchy. The top level is CONTINENT, both the Name role and the ISO code role. Level 2 has four COUNTRY geographic roles, corresponding to four different country formats. Level 3 contains three state formats, level 4 contains the city name, and level 5 contains two address formats and the postal code.
<hier id="World"> <lev level="1" geo_role="CONTINENT"/> <lev level="1" geo_role="CONTINENT_ISO2"/> <lev level="2" geo_role="COUNTRY"/> <lev level="2" geo_role="COUNTRY_FIPS"/> <lev level="2" geo_role="COUNTRY_ISO2"/> <lev level="2" geo_role="COUNTRY_ISO3"/> <lev level="3" geo_role="STATE"/> <lev level="3" geo_role="STATE_ISO_SUB"/> <lev level="3" geo_role="STATE_FIPS"/> <lev level="4" geo_role="CITY"/> <lev level="5" geo_role="ADDRESS_FULL"/> <lev level="5" geo_role="ADDRESS_LINE"/> <lev level="5" geo_role="POSTAL_CODE"/> </hier>
These steps describe how to add the Federal Reserve Districts geographic role to the geo_services.xml file.
Open the geo_services.xml file. The default location is:
C:\ibi\srvnn\home\catalog\geo_services.xml
where nn is the release of your WebFOCUS Reporting Server. For example, 82 for version 8.2.
<geo_role id="FED-DIST" value_size="50" type="alpha" role_name="FEDDIST" role_name_title="FED District" role_format="FR_Distric" role_format_title="FED District Name" geo_type="geography"> <vocabulary_rules> <vocabulary>+%FR_Distric%</vocabulary> </vocabulary_rules> </geo_role
<hier id="US"> <lev level="1" value="United States" geo_role="COUNTRY"/> <lev level="1" value="US" geo_role="COUNTRY_ISO2"/> <lev level="1" value="USA" geo_role="COUNTRY_ISO3"/> <lev level="2" geo_role="USSTATE"/> <lev level="2" geo_role="USSTATE_ABBR"/> <lev level="2" geo_role="USSTATE_FIPS"/> <lev level="3" geo_role="USCOUNTY"/> <lev level="3" geo_role="USCOUNTY_FIPS"/> <lev level="4" geo_role="USCITY"/> <lev level="4" geo_role="USCITY_FIPS"/> <lev level="5" geo_role="ADDRESS_FULL"/> <lev level="5” geo_role="ADDRESS_LINE"/> <lev level="5" geo_role="ZIP3"/> <lev level="5" geo_role="ZIP5"/> <lev level="6" geo_role="FED-DIST"/> </hier>
<uri description="FedReserve Districts"> <returned_geometry>GEOMETRY_AREA </returned_geometry> <returned_georole>FED-DIST</returned_georole> <url type="esri" authorization="none" synonym=""> http://services7.arcgis.com/L95Wwv9OjRQ0tjAs/arcgis/rest/services/ FRDISTRICTS/FeatureServer/0</url> <parameters> <parm order="1" parm_name="FR_Distric" parm_georole="FED-DIST"/> </parameters> </uri>
You will now be able to select this role when using the Map As option the next time you start InfoAssist+, as shown in the following image.
WebFOCUS | |
Feedback |