Version 2012 © 2012 KOREM. All rights reserved. mapworkspace logo is a trademark of Korem Inc. Visit us on the Internet at www.korem.com, or contact us at: KOREM - Denver 7000 East Belleview Avenue, Suite 260 Greenwood Village, Colorado 80111 USA Phone: 1 720 200-4488 Fax: 1 720 200-4323 Toll Free: 1 877 692-0306 – North America KOREM - Québec 330 St. Vallier Street East, Suite 240 Québec, QC G1K 9C5 CANADA Phone : 1 418 647-1555 Fax : 1 418 647-1666 Toll Free : 1 888 440-1MAP (1627) - North America MapInfo Professional is a trademark of Pitney Bowes Software in the United States. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. This product includes software developed by the Apache Software Foundation (http://www.apache.org). This product includes libraries developed by the Open Source Geospatial Foundation (http://www.osgeo.org/). Products named herein may be trademarks of their respective manufacturers and are hereby recognized. Trademarked names are used editorially, to the benefit of the trademark owner, with no intent to infringe on the trademark. Comments and suggestions are welcome. mapworkspace MapInfo Professional User Guide 3 TABLE OF CONTENTS INTRODUCTION 5 1 TABLES 7 1.1 Formats and Data Sources 7 1.1.1 Vectorial Data 7 1.1.2 Raster images 7 1.1.3 Grids 7 1.1.4 DBMS Connections (ODBC and Oracle Spatial) 7 1.1.5 Map Tile Servers 8 1.2 Content 9 1.2.1 Table Names 9 1.2.2 Fields 9 1.2.3 Seamless Tables 9 1.2.4 Selections and Dynamic Joins 10 1.3 Projections 11 2 WINDOWS 13 2.1 Map Windows 13 2.2 Legend Windows 13 2.3 Layout Windows 14 2.4 Graph Windows 14 2.5 Browser Windows 14 2.6 Redistrict Windows 14 3 MAPS 15 3.1 Layers Content 15 3.1.1 Symbols 16 3.1.2 Lines 16 3.1.3 Regions/Polygons 18 3.1.4 Text 18 3.1.5 Raster Images 18 3.2 Layer Control Options 19 3.2.1 Cosmetic Layer 19 3.2.2 Group Layers 19 3.2.3 Visibility 20 3.2.4 Edition Mode 20 3.2.5 Selection Mode 20 3.2.6 Automatic Labels 20 3.2.7 Display Options 21 3.3 Thematics 22 3.3.1 Thematic Type 22 3.3.2 Data Source 22 3.3.3 Thematic Parameters 23 3.4 Labels 29 3.4.1 Source 29 3.4.2 Display 29 3.4.3 Text Style 30 3.5 Projections 31 mapworkspace MapInfo Professional User Guide 4 mapworkspace MapInfo Professional User Guide 5 INTRODUCTION Here are a few recommendations addressing the MapInfo user who wishes to share his maps on mapworkspace. As mapworkspace does not support every MapInfo option and function, this document will guide the MapInfo user to work more efficiently and avoid a certain number of problems. These recommendations concern three aspects of a MapInfo work session: the tables (formats and content), the windows (map windows, graph windows, browser windows, layout windows and legends) and the map itself (layers, thematics and labels). We invite you to follow these recommendations in order to optimize your map's performances and ensure the integrity of your MapInfo ® workspace. We invite you to pay special attention to the following items: 1. Avoid the use of spaces, accented or special characters in file and column names; 2. Use native MapInfo tables or Vertical Mapper grids; 3. Use no selections or dynamic links; 4. Use properly registered raster images; 5. Reduce as much as possible the number of different projections used in your maps; 6. Display a map window which dimensions correspond as closely as possible to the one you are about to deploy in mapworkspace, to preserve your map's interactivity; 7. Avoid storing information in the cosmetic layer. If needed, save it to a MapInfo native table; 8. Make effective use of zoom layering on layers and labels; 9. Use automatic labelling, based on simple expressions. mapworkspace MapInfo Professional User Guide 6 mapworkspace MapInfo Professional User Guide 7 1 TABLES Tables opened and used by the workspace must absolutely follow these few rules. 1.1 Formats and Data Sources 1.1.1 Vectorial Data MapInfo tables should be composed of .tab, .map, .id and .dat files, with or without an .ind (index) file. Only .dat descriptive data file formats should be used. Other formats such as .dbf, .txt, .wk1, .xls or .mdb should never be associated with the workspace. ESRI Shape files (.SHP) included in a MapInfo workspace may be published with your map. 1.1.2 Raster images Raster image supported formats are: gif, .jpg, .jpeg, .tif, .tiff, .bmp, .grc, .grd, .mig et .jp2. Raster images must be properly registered. 1.1.3 Grids The MapInfo thematic grids (.mig) are fully supported. Values associated to these thematics may be displayed when using the Information and Legend tools. The Vertical Mapper numerical and classified grids are supported (.GRD or .GRC), but with a restriction: The Information and Legend tool do not allow displaying the information related to a classified or numerical grid. 1.1.4 DBMS Connections (ODBC and Oracle Spatial) Workspaces using database connections (ODBC or Oracle Spatial,) cannot be published on mapworkspace. mapworkspace MapInfo Professional User Guide 8 1.1.5 Map Tile Servers Recent MapInfo Professional versions allow the integration of Bing Maps and Open StreetMap (OSM) map tile server data into your maps. If you are using one or many OSM tile server layers in your MapInfo workspace, you can publish it on mapworkspace. However, the layer(s) will be systematically moved to the bottom of you map. Moreover, zoom layering, transparency and translucency settings will be deactivated. On the other hand, mapworkspace does not allow access to Bing Maps tile server layers. Your map should not contain any such layer or it would be blocked at publication. Also, be aware that as mapworkspace does not support multiple occurrences of the same map tile server layer, if your map contains two OSM layers, then the resulting mapworkspace map will contain only one OSM layer. Projection All maps published on mapworkspace and containing an OSM map tile server layer will be automatically reprojected into Popular Visualization CRS for Google (EPSG : 3857). However, reprojection of raster grids and images and of non-earth coordinates is not supported. If you are using such data, you must transpose your data in this projection before publishing your workspace on mapworkspace. Otherwise, you will not be able to benefit from this functionality. mapworkspace MapInfo Professional User Guide 9 1.2 Content 1.2.1 Table Names As usual, file names must only contain alphanumerical characters (no accent, space or special character). 1.2.2 Fields Field names must only contain alphanumerical characters. Do not use any accent, space or special character. LOGICAL fields are not fully supported. In fact, although a workspace containing one or many fields of logical type can be published without problem, such type of data should not serve as a data source for a MapInfo thematic map. Such thematic may display with errors on mapworkspace. “DATE” field types can be used, but may not work correctly in the following circumstances: Tooltips and Information tool will not work on this layer. Thematics may not display correctly. “TIME” and “DATE/TIME” fields are not supported and will be blocked at publication. 1.2.3 Seamless Tables Seamless tables are supported following the restrictions hereafter: When creating seamless tables: All base tables composing the seamless table should be saved in the same directory as the seamless table; The "No Path" option must absolutely be checked in the Seamless Manager Preferences. When using seamless tables in MapInfo: mapworkspace will be unable to use a seamless table if its base tables are not present in the MapInfo workspace. In consequence, you must open then in a “No View” mode. Proceeding this way will ensure mapworkspace MapInfo Professional User Guide 10 that even though they will remain invisible in the layer control, they can be called individually at any time with the Info tool. 1.2.4 Selections and Dynamic Joins SQL queries are not supported. If you wish to keep your query results and use them in your mapworkspace maps, they should be saved in a MapInfo native format (*.TAB). Use MapInfo’s File/Save Copy As option. A table must not contain any column resulting from a dynamic join between two tables or fields. Such a column is only temporary and cannot be used by mapworkspace. When using the Table/Update Column/Join function, make sure to update a pre-existing column and to save this new column in making a copy of the table (File/Save Table or Save Copy As). Not supported [...]... reduce the display precision This can be observed both in MapInfo and mapworkspace 11 mapworkspace MapInfo Professional User Guide 12 mapworkspace MapInfo Professional User Guide 2 WINDOWS It is important that only one map window be opened at a time in the workspace while mapworkspace will use only one Please note that mapworkspace considers as opened even a reduced window ( ) and will select by default... supported by mapworkspace, although if two legends are used in one map, a thematic and a cartographic, mapworkspace will use the cartographic legend as the default 13 mapworkspace MapInfo Professional User Guide 2.3 Layout Windows Layout windows are not supported in mapworkspace 2.4 Graph Windows Graph windows are not supported in mapworkspace 2.5 Browser Windows Browser windows are not supported in mapworkspace. .. supported in mapworkspace 14 mapworkspace MapInfo Professional User Guide 3 MAPS 3.1 Layers Content Layers may contain : points ; lines ; polygons text Object collections : Supported X Multi polygons X Multi lines / polylines X Multi points X Multiple object types - Not supported Raster images (see section 1.1.2 for a list of supported formats) 15 mapworkspace 3.1.1 MapInfo Professional User Guide. .. sections For better performance, the use of MapInfo symbols is recommended Logarithmic Transformation Option not supported 26 mapworkspace MapInfo Professional User Guide Individual Values The following restrictions apply : Style Supported under conditions mentioned in previous sections Apply Color Option not supported 27 mapworkspace MapInfo Professional User Guide Grid The following restrictions apply... supported 24 mapworkspace MapInfo Professional User Guide Bar Charts The following restrictions apply : Style: Supported under conditions mentioned in previous sections Stacked data : Option not supported Pen and brush style: Default values supported only Independent scales : Option not supported Logarithmic Transformation: Option not supported 25 mapworkspace MapInfo Professional User Guide Pie Charts... be rendered in mapworkspace It must be kept cleared and not be in Edition mode 3.2.2 Group Layers New MapInfo 10.0 group layer option is not supported in mapworkspace Although you can publish a workspace that uses the group layers, it will not be applied in mapworkspace and each layer will be displayed independently in the layer control 19 mapworkspace 3.2.3 MapInfo Professional User Guide Visibility... parameters will remain as defined in the MapInfo workspace The mapworkspace Information tool will work only on selectable layers 3.2.6 Automatic Labels Automatic labels are supported and will respect the labels parameters as set in the MapInfo workspace See the corresponding section of this guide for details 20 mapworkspace 3.2.7 MapInfo Professional User Guide Display Options The following display options are... kind of MapInfo thematic map It would not be displayed correctly in mapworkspace A thematic should not refer to anything else but a unique field Operations between tables or fields (Expression… or Join…) are not recognized by mapworkspace References to an ODBC (Open Data Base Connexion) should not be used Bi-varied thematics are not supported 22 mapworkspace 3.3.3 MapInfo Professional User Guide. . .mapworkspace MapInfo Professional User Guide 1.3 Projections It is important to reduce the number of different projections used for the various tables layered in a map The more different projections are used, the more time will be necessary to display the map Moreover, the use of too many projections can, at greater scale, reduce the display precision This can be observed both in MapInfo and mapworkspace. .. individual table as the one that is used for the raster image Please note that if you want to use the Google base map in mapworkspace, all raster images must be re-projected in « Popular Visualisation CRS (EPSG : 3857) » prior to being used in mapworkspace 18 mapworkspace MapInfo Professional User Guide 3.2 Layer Control Options Display and Label Options : Supported under the conditions mentioned in corresponding . Projections 31 mapworkspace MapInfo Professional User Guide 4 mapworkspace MapInfo Professional User Guide 5 INTRODUCTION Here are a few recommendations addressing the MapInfo user who wishes. precision. This can be observed both in MapInfo and mapworkspace. mapworkspace MapInfo Professional User Guide 12 mapworkspace MapInfo Professional User Guide 13 2 WINDOWS It is important. automatic labelling, based on simple expressions. mapworkspace MapInfo Professional User Guide 6 mapworkspace MapInfo Professional User Guide 7 1 TABLES Tables opened and used by the