Start Map Manager when you want to import maps from third-party sources or manage existing IBM Cognos map files.
Step
*
From the Start menu, click Programs, IBM Cognos 8, Map Manager.
You can now open a map file or import a map file from a third-party source.
Start Map Manager
Start Map Manager when you want to import maps from third-party sources or manage existing IBM Cognos map files.
Step
*
From the Start menu, click Programs, IBM Cognos 8, Map Manager.
You can now open a map file or import a map file from a third-party source.
Step
*
From the Start menu, click Programs, IBM Cognos 8, Map Manager.
You can now open a map file or import a map file from a third-party source.
The Report Studio Map Object
Maps are most often used to show geographical areas, but they can be used to show other spatial information, such as a floor plan in a building, seats in an airplane, or parts of the human body.
Maps are similar to crosstabs in the way their data is organized. The display is different, but maps show the intersection of data the same ways as crosstabs; for example, you can see the revenue for golf equipment in Canada.
A map in IBM Cognos 8 consists of a collection of layers. Each layer contains different information and acts like a transparency that is placed on top of the map. Each layer adds more information to the map. For example a map of the world may contain information related to countries on one layer and information related to cities on another level.
Report Studio maps provide the following three types of layers:
*
Region layer
Specifies the regions on a map to be differentiated according to values in the data source. For example, to show the revenue level for each country on a map of the world, choose Country as the region layer and then specify that the color of each country is based on the revenue value for that country. Regions can be set up for drilling through to other reports.
*
Point layer
Specifies the points to be placed on a map. The color and size of the points is based on the data that you select. For example, you choose to show cities as points on a map and set the color of each point by revenue and the size of each point by profit. Points can be set up for drilling through to other reports.
*
Display layer
You can show or hide items such as grid lines or capital cities. This layer is determined in the map file and not in the data source.
Note: If you intend to create CSV or XML output from your map, use only a point layer or a region layer. CSV and XML do not support the simultaneous use of both layers in the same map. Only one layer will be rendered in the output.
Maps are similar to crosstabs in the way their data is organized. The display is different, but maps show the intersection of data the same ways as crosstabs; for example, you can see the revenue for golf equipment in Canada.
A map in IBM Cognos 8 consists of a collection of layers. Each layer contains different information and acts like a transparency that is placed on top of the map. Each layer adds more information to the map. For example a map of the world may contain information related to countries on one layer and information related to cities on another level.
Report Studio maps provide the following three types of layers:
*
Region layer
Specifies the regions on a map to be differentiated according to values in the data source. For example, to show the revenue level for each country on a map of the world, choose Country as the region layer and then specify that the color of each country is based on the revenue value for that country. Regions can be set up for drilling through to other reports.
*
Point layer
Specifies the points to be placed on a map. The color and size of the points is based on the data that you select. For example, you choose to show cities as points on a map and set the color of each point by revenue and the size of each point by profit. Points can be set up for drilling through to other reports.
*
Display layer
You can show or hide items such as grid lines or capital cities. This layer is determined in the map file and not in the data source.
Note: If you intend to create CSV or XML output from your map, use only a point layer or a region layer. CSV and XML do not support the simultaneous use of both layers in the same map. Only one layer will be rendered in the output.
The Report Studio Map Object
Maps are most often used to show geographical areas, but they can be used to show other spatial information, such as a floor plan in a building, seats in an airplane, or parts of the human body.
Maps are similar to crosstabs in the way their data is organized. The display is different, but maps show the intersection of data the same ways as crosstabs; for example, you can see the revenue for golf equipment in Canada.
A map in IBM Cognos 8 consists of a collection of layers. Each layer contains different information and acts like a transparency that is placed on top of the map. Each layer adds more information to the map. For example a map of the world may contain information related to countries on one layer and information related to cities on another level.
Report Studio maps provide the following three types of layers:
*
Region layer
Specifies the regions on a map to be differentiated according to values in the data source. For example, to show the revenue level for each country on a map of the world, choose Country as the region layer and then specify that the color of each country is based on the revenue value for that country. Regions can be set up for drilling through to other reports.
*
Point layer
Specifies the points to be placed on a map. The color and size of the points is based on the data that you select. For example, you choose to show cities as points on a map and set the color of each point by revenue and the size of each point by profit. Points can be set up for drilling through to other reports.
*
Display layer
You can show or hide items such as grid lines or capital cities. This layer is determined in the map file and not in the data source.
Note: If you intend to create CSV or XML output from your map, use only a point layer or a region layer. CSV and XML do not support the simultaneous use of both layers in the same map. Only one layer will be rendered in the output.
Maps are similar to crosstabs in the way their data is organized. The display is different, but maps show the intersection of data the same ways as crosstabs; for example, you can see the revenue for golf equipment in Canada.
A map in IBM Cognos 8 consists of a collection of layers. Each layer contains different information and acts like a transparency that is placed on top of the map. Each layer adds more information to the map. For example a map of the world may contain information related to countries on one layer and information related to cities on another level.
Report Studio maps provide the following three types of layers:
*
Region layer
Specifies the regions on a map to be differentiated according to values in the data source. For example, to show the revenue level for each country on a map of the world, choose Country as the region layer and then specify that the color of each country is based on the revenue value for that country. Regions can be set up for drilling through to other reports.
*
Point layer
Specifies the points to be placed on a map. The color and size of the points is based on the data that you select. For example, you choose to show cities as points on a map and set the color of each point by revenue and the size of each point by profit. Points can be set up for drilling through to other reports.
*
Display layer
You can show or hide items such as grid lines or capital cities. This layer is determined in the map file and not in the data source.
Note: If you intend to create CSV or XML output from your map, use only a point layer or a region layer. CSV and XML do not support the simultaneous use of both layers in the same map. Only one layer will be rendered in the output.
Verb Types
Most objects in MDL have four verb types associated with them: Add, Delete, Make, and Update; for example, CatAdd, CatDelete, CatMake, and CatUpdate.
*
Add verbs add the object to the model. An error is issued if the object already exists. Examples for this verb type show you how to use it to create an object and specify its required settings.
*
Delete verbs remove the object from the model. An error is issued if the object does not exist.
*
Make verbs add the object if it does not already exist, and update the object if it does exist. Make verbs combine the functionality of both the Add and Update verbs. Examples for this verb type show the object definitions that are generated by Transformer when you save a model as an .mdl file.
*
Update verbs update existing objects. An error is issued if the object does not exist.
*
Add verbs add the object to the model. An error is issued if the object already exists. Examples for this verb type show you how to use it to create an object and specify its required settings.
*
Delete verbs remove the object from the model. An error is issued if the object does not exist.
*
Make verbs add the object if it does not already exist, and update the object if it does exist. Make verbs combine the functionality of both the Add and Update verbs. Examples for this verb type show the object definitions that are generated by Transformer when you save a model as an .mdl file.
*
Update verbs update existing objects. An error is issued if the object does not exist.
CatJoin
The CatJoin verb joins a category to its specified parent category. This verb is required when creating alternate drill-down paths, and is a useful means of making similar categories unique.
Note: Category object names differ between MDL and the Windows interface. MDL uses the category code as the object name. For more information, see "Locating Objects Uniquely". There is no Windows interface equivalent.
CatJoin is required when using alternate drill-down paths. It links a category in the convergence level with the parent in the alternate drill-down path.
The syntax is as follows:
CatJoin objCat[
Dimension objDim]
Parent objCat
Note: Category object names differ between MDL and the Windows interface. MDL uses the category code as the object name. For more information, see "Locating Objects Uniquely". There is no Windows interface equivalent.
CatJoin is required when using alternate drill-down paths. It links a category in the convergence level with the parent in the alternate drill-down path.
The syntax is as follows:
CatJoin objCat[
Dimension objDim]
Parent objCat
Verb Types
Most objects in MDL have four verb types associated with them: Add, Delete, Make, and Update; for example, CatAdd, CatDelete, CatMake, and CatUpdate.
*
Add verbs add the object to the model. An error is issued if the object already exists. Examples for this verb type show you how to use it to create an object and specify its required settings.
*
Delete verbs remove the object from the model. An error is issued if the object does not exist.
*
Make verbs add the object if it does not already exist, and update the object if it does exist. Make verbs combine the functionality of both the Add and Update verbs. Examples for this verb type show the object definitions that are generated by Transformer when you save a model as an .mdl file.
*
Update verbs update existing objects. An error is issued if the object does not exist.
*
Add verbs add the object to the model. An error is issued if the object already exists. Examples for this verb type show you how to use it to create an object and specify its required settings.
*
Delete verbs remove the object from the model. An error is issued if the object does not exist.
*
Make verbs add the object if it does not already exist, and update the object if it does exist. Make verbs combine the functionality of both the Add and Update verbs. Examples for this verb type show the object definitions that are generated by Transformer when you save a model as an .mdl file.
*
Update verbs update existing objects. An error is issued if the object does not exist.
CatJoin
The CatJoin verb joins a category to its specified parent category. This verb is required when creating alternate drill-down paths, and is a useful means of making similar categories unique.
Note: Category object names differ between MDL and the Windows interface. MDL uses the category code as the object name. For more information, see "Locating Objects Uniquely". There is no Windows interface equivalent.
CatJoin is required when using alternate drill-down paths. It links a category in the convergence level with the parent in the alternate drill-down path.
The syntax is as follows:
CatJoin objCat[
Dimension objDim]
Parent objCat
Note: Category object names differ between MDL and the Windows interface. MDL uses the category code as the object name. For more information, see "Locating Objects Uniquely". There is no Windows interface equivalent.
CatJoin is required when using alternate drill-down paths. It links a category in the convergence level with the parent in the alternate drill-down path.
The syntax is as follows:
CatJoin objCat[
Dimension objDim]
Parent objCat
.py? and .mdl Formats
You can save Transformer models in two formats: .py? and .mdl. You can only open models saved as .py? files in the Transformer (Windows) interface. However, you can open models saved as .mdl files in either the Windows interface or a text editor.
Each .mdl file is a plain-text representation of the model, and may be compatible with other versions of Transformer than the one used to create it. However, it loads more slowly than a .py?-format file because it recreates all of the Transformer objects each time it loads.
You can open models saved as .mdl files on any supported UNIX, Linux, or Windows platform, making this the preferred format to use in a mixed production environment.
The .py? format is a binary representation of the model. Although not compatible between versions of Transformer, it loads faster than the .mdl-format equivalent, even though it is larger, because the Transformer objects are not recreated when the model reloads.
As you edit a model, the size of the associated .py? file increases because information about the operations performed during model editing is retained in the file. Transformer uses this information when performing incremental updates and other subsequent cube operations. Lengthy descriptions of the appended operations can cause fragmentation of the binary file. We therefore recommend that you periodically save your .py? models as .mdl files.
Each .mdl file is a plain-text representation of the model, and may be compatible with other versions of Transformer than the one used to create it. However, it loads more slowly than a .py?-format file because it recreates all of the Transformer objects each time it loads.
You can open models saved as .mdl files on any supported UNIX, Linux, or Windows platform, making this the preferred format to use in a mixed production environment.
The .py? format is a binary representation of the model. Although not compatible between versions of Transformer, it loads faster than the .mdl-format equivalent, even though it is larger, because the Transformer objects are not recreated when the model reloads.
As you edit a model, the size of the associated .py? file increases because information about the operations performed during model editing is retained in the file. Transformer uses this information when performing incremental updates and other subsequent cube operations. Lengthy descriptions of the appended operations can cause fragmentation of the binary file. We therefore recommend that you periodically save your .py? models as .mdl files.
.py? and .mdl Formats
You can save Transformer models in two formats: .py? and .mdl. You can only open models saved as .py? files in the Transformer (Windows) interface. However, you can open models saved as .mdl files in either the Windows interface or a text editor.
Each .mdl file is a plain-text representation of the model, and may be compatible with other versions of Transformer than the one used to create it. However, it loads more slowly than a .py?-format file because it recreates all of the Transformer objects each time it loads.
You can open models saved as .mdl files on any supported UNIX, Linux, or Windows platform, making this the preferred format to use in a mixed production environment.
The .py? format is a binary representation of the model. Although not compatible between versions of Transformer, it loads faster than the .mdl-format equivalent, even though it is larger, because the Transformer objects are not recreated when the model reloads.
As you edit a model, the size of the associated .py? file increases because information about the operations performed during model editing is retained in the file. Transformer uses this information when performing incremental updates and other subsequent cube operations. Lengthy descriptions of the appended operations can cause fragmentation of the binary file. We therefore recommend that you periodically save your .py? models as .mdl files.
Each .mdl file is a plain-text representation of the model, and may be compatible with other versions of Transformer than the one used to create it. However, it loads more slowly than a .py?-format file because it recreates all of the Transformer objects each time it loads.
You can open models saved as .mdl files on any supported UNIX, Linux, or Windows platform, making this the preferred format to use in a mixed production environment.
The .py? format is a binary representation of the model. Although not compatible between versions of Transformer, it loads faster than the .mdl-format equivalent, even though it is larger, because the Transformer objects are not recreated when the model reloads.
As you edit a model, the size of the associated .py? file increases because information about the operations performed during model editing is retained in the file. Transformer uses this information when performing incremental updates and other subsequent cube operations. Lengthy descriptions of the appended operations can cause fragmentation of the binary file. We therefore recommend that you periodically save your .py? models as .mdl files.
Subscribe to:
Posts (Atom)