Work on that data.
Save the project.
If desired... Export parts of the project, like raster images or vector drawings, into other formats. Export a drawing to a shapefile, or an entire project to an ESRI geodatabase, for example.
Already running a Manifold session? For a quick launch, right-click on the Manifold icon in the Windows taskbar and choose Manifold System 9.0.
Manifold launches with a new, blank project. A project saves everything in the Manifold desktop in a .map format file. Nothing is faster than opening a Release 9 Manifold .map file. It opens instantly. Download samples of .map files from the Examples page.
File - Open will open a Manifold .map project file.
File - Link lets us view and edit data "in place," within the original file. Linked data stays in the original source.
File - Export copies data from a Manifold project into some external file format, like copying a drawing into a shapefile.
The fastest way to work is to import data into Manifold and then save everything in a Manifold .map project file. Manifold .map files open instantly, even when they are hundreds of GB in size.
Try to keep all of your GIS data - drawings, images, tables, ...everything - in Manifold .map format files. That is much faster and more reliable than using legacy formats like shapefiles, or using more modern but slow formats like GPKG. Migrate the data you use into Manifold .map storage from other formats. Export to legacy formats for interoperability, but enjoy the unbeatable speed, reliability and convenience of Manifold .map projects for your own work.
A big difference between Manifold and classic GIS: Manifold itself is a super-fast DBMS that can store huge data inside the Manifold project. Traditional GIS packages usually do not have an internal database - they have to leave their data outside the project, stored in the same file formats, like shapefiles, in which the data was provided. That is much slower and more limiting than importing into Manifold.
Manifold also can link to external data in the original format if we want, but Manifold users usually import data into a Manifold project, to run super-fast without the limitations of formats that may be OK for interchange, but which cause slow downs and reduced capabilities when used for operational storage.
When a classic GIS package "adds" a vector layer from a shapefile, that data stays in the shapefile. The package has to read / write the data back and forth from the shapefile when viewing or editing. Besides being slow, that limits what can be done with that layer to the limitations of shapefile format.
When we "add" a vector layer from a shapefile to Manifold with File - Import we copy data from the shapefile into the Manifold project. Once the data is in Manifold there is no connection back to the original shapefile, so there is no shapefile involved getting in the way of fast, modern GIS. If ever we want to save a drawing into a shapefile, we can do that using File - Export to export it into a shapefile.
In Manifold we can use File - Link to leave data in the original source format if we want, and work with it in-place the way classic GIS packages do, but even faster and better. Manifold performs faster linking to formats like an ESRI geodatabase or a PostgreSQL/PostGIS database because Manifold itself is a fast, parallel DBMS: it can operate a connection to an external database faster than slow, single-threaded clients like ArcGIS Pro or QGIS.
Import tables, drawings, images and other data to the project. That brings the data into Manifold and stores it within the project for maximum speed and maximum capabilities. Imported data has no connection to the original source. Manifold can read virtually every format and data source in existence. See the Big List of Formats and Data Sources topic for the huge list.
Link data from outside sources. That makes the data available within the project as if it had been imported, but leaves the data stored outside of the project. This is what legacy packages like QGIS do when they "add" a layer. Links leave data in-place in its original source. Most formats are slower and more limited compared to importing into Manifold, but Manifold uses many technical innovations to get better speed with linked files.
Create a Data Source. A more sophisticated, flexible way of linking data from many different formats and sources. This is how we connect to database servers like Oracle or to web servers like Google and Bing.
Link an existing Manifold .map file into the project. Use data stored in other .map files with zero overhead and no performance hit. Maintain huge archives of data in .map files and link whatever you want into your project.
Multiple sessions: Launch Manifold more than once with different projects. Copy and paste between different sessions.
Create new stuff. Use automatic tools like queries and scripts to create new components, or create them manually with editing tools. Now that you have Manifold, use it for everything.
Projections - When importing or linking, Manifold automatically reads the projection, if specified. If no projection is specified, launch Assign Initial Coordinate System in the Contents pane to specify the correct initial projection for the imported or linked component. See the Example: Import a Shapefile topic for an easy example. Projection and Coordinate System are synonyms in this documentation.
Double-click a component to open it in a window. Right-click a component for a useful context menu. Press the F1 Help function key to launch a quick reference web page for navigating and other commands in that window.
A Manifold project contains tables, images, drawings, labels, maps, data sources, queries, scripts, and more. These are called components. That is just a generic, neutral word that means "an item in a project." When we import data from GIS formats, we create components like tables, drawings, and images.
Tables - All data within Manifold is stored in a table in one form or another. Opening a table window shows a table in classic row and column presentation. A drawing or an image is just a display window that shows geometry data or raster tile data that is stored in some table. That is why when we see a drawing or image in the project we will usually see a similarly-named table from which it takes its data.
Drawings - Vectors. A visual display of vector data stored within tables. Data can be stored using a variety of geometry types. The same data from the same table can be seen in multiple different drawings using different styles, and the same drawing can be open in multiple windows with different selections and views in each.
Data Sources - Data linked into a project from an external source, which could be a file, a file database, a database serve or a web server, covering virtually every database and file type encountered in database or GIS work.
Images - Rasters. A visual display of raster data stored within tables as tiles. Tiles can use a wide variety of different data types and channel combinations. All rasters are called images in Manifold, even those which are terrain elevation rasters or other non-photographic data rasters.
Labels - Annotations, using text and symbols, created manually or created automatically from fields in a drawing's table.
Layouts - A composition on virtual sheets of paper, for printing to a PDF or physical printer. Layouts are made up of frames, each of which can show components such as maps, drawings, images, labels, or text frames.
Locations - Locations save a particular geographic location with an associated scale, thus saving a given view in a map or other window to which we can return with one click. Locations are just snippets of JSON text that specify lat / lon coordinates and scale, easy to change, create automatically, edit and manipulate.
Maps - A window that shows a stack of layers. Each layer in map is a drawing, image or labels component. Maps can use different projections than their layers. Maps will reproject their contents on the fly as needed to display them in the map's projection. Maps take zero space, because they are just windows that show other components as layers.
Queries - Written in SQL, queries manipulate data and projects, for example, creating new tables and other components, performing calculations, altering the structure of databases and tables, and extracting, editing and analyzing subsets of data. Many Manifold dialogs and facilities, like the Create Map dialog or any of hundreds of Transform or Select templates, will automatically create queries for us, if we want. That's a great way to learn how to use SQL in real life ways.
Scripts - Manifold includes built-in support for scripting in eleven different languages with six to eight always available and the remainder easy to install. Scripts provide custom capabilities and can automate virtually anything.
Comments - Text saved and displayed in a comments window provides a simple but convenient way to save notes about a project or to save text as a scratch pad. For tips on editing Comments, see the Editing Queries, Scripts and Comments topic.
Folders - We can organize our project by using folders.
Double-clicking a component opens it in a window, with a title tab at the top. Double-click another component open and it will appear with its own title tab. Click a title tab to switch to that window.
Windows with layers, like Maps, will open with one or more layer tabs at the bottom. Click a layer tab to make it the active layer, for editing or selection. Double-click a layer tab to turn it off and on. Right-click a layer tab for a useful context menu. Too many layers for tabs? Click on the Layers pane to see them all.
Undock a window or a pane by Shift-clicking the name tab. Dock it again by Shift-clicking the title bar.
Resize and position undocked windows anywhere on the Windows desktop. Use two or three monitors to have plenty of Windows desktop, for big windows, and to see the Project, Layers, and Contents panes undocked all at once.
Layers pane - Shows all layers in a map, all fields in a table, and all frames in a layout. Allows us to quickly turn items off and on, to set layer transparency in a map or field width in a table, and to group layers or fields or layout frames into folders. The Layers pane is more convenient than tabs when there are many layers in a map, or many fields in a table, or many frames in a layout.
Contents pane - Shows information on the active component, and it provides sub-panes to manipulate that component. Sub-panes include:
Component pane - Shows coordinate systems (projections) and allows us to assign, repair, or change a coordinate system.
Record pane - Shows attribute info for objects, allows editing field contents or coordinates, and allows setting Style for individual items.
Select pane - Many point-and-click templates to select exactly what we want.
Style pane - Choose colors and symbology for a drawing, do thematic formatting, choose channels and display options for image, and colors, text and symbology for labels.
Transform pane - Many point-and-click templates to analyze, transform, and geoprocess data in vector drawings, raster images, and data of all kinds in tables.
Shift-click the title tab to undock the Project pane, the Contents pane, or the Layers pane, so they can be resized and repositioned anywhere on our Windows desktop. This allows the panes we use most often to be floating in view at all times.
Upcoming builds will move some sub-panes out from within the Contents pane into being their own, independent panes, like the Project and Layers panes.
Cursor mode buttons appear in the main toolbar for an open window: Click the mode button to enter that mode. The mode persists for that window until we click a different button. Buttons to create areas, lines, or points will be enabled for drawing layers. The tracker tool for measuring is in the mode button, too.
The default mouse cursor mode is navigation. Pick another mode to create points, lines or areas in drawings, or to use the Tracker tool for measurements.
Click and drag to pan the view. Right-click and drag to zoom box.
Double-click to open a component.
Right-click and drag to draw a zoom box.
Click and drag to move the view.
Wheel mouse to zoom in and out.
Back and Forward arrows on the toolbar go back and forward in views.
Zoom buttons on the toolbar will zoom to fit, zoom out and zoom in.
Undock / Dock a tab by Shift-clicking the name.
Press the F1 Help function key when a window is open to get a list of keyboard shortcuts available for that window. If we try out some other modes, like the Tracker, a keyboard shortcut back to default navigation mode is Shift-Esc.
Manifold supports both Windows styles of keyboard shortcuts for main menu items: Ctrl key shortcuts as well as classic access key shortcuts begun by pressing the Alt key.
Clicking a main menu heading will show Ctrl key short cuts. Pressing the Ctrl key and O key simultaneously is the same as launching File - Open.
For keyboard enthusiasts, Manifold supports standard Windows access keys: Press the Alt key and keyboard shortcuts for the menu items will be underlined. Press the arrow buttons on the keyboard to cycle through menu items, and either press the access key shortcut, like V for View, or cycle to the menu item and press Enter to pick it. We can cycle to View and then press Enter to open the menu, and see the access key shortcuts for commands within that menu. For example, pressing Alt and then V and then C will launch a new Command Window. If a menu includes multiple commands with the same access key, pressing it cycles between these commands without invoking them. Cycle to the command desired and press Enter.
In Windows 10, Manifold honors Windows settings for access keys as specified in Settings - Ease of Access - Keyboard or in the Windows Control Panel, always showing access key characters underlined in menu items, or showing them only when commanded with an Alt.
In the beginning we spend most of our time viewing data. As we learn more we will want to make measurements using the Tracker, or to edit drawings by creating points, lines or areas.
The drop-down menu on the mode button lets us choose a different mode, offering choices depending on what window is active. When working with a drawing, if we choose Create Line the mouse cursor user interface switches from Navigation mode into Create Line mode.
The mode button always shows what mode applies for that window.
Different windows can have different modes, with one window being in Create Line mode while another window stays in Navigation mode. As we switch between windows the mode button will automatically switch to show the mode for that window. The drop-down menu for the mode button will show appropriate choices for whatever is the active window.
For example, if a layout window is active the drop-down menu for the mode button will show choices that work only for layouts.
Tables: All data in Manifold is kept in tables. Tables can be huge in Manifold, hundreds of GB.
Table windows show tables in a classic, row and column presentation. When tables are big we work with them using queries. Tables can contain geometry data for vector drawings and tile data for raster images.
The Layers pane makes it easy to manipulate layers in maps or fields in tables when there are very many layers or fields.
Data from the same table can be used at the same time in many different drawings, labels or images.
Different drawings, labels or images all can use different Styles.
Image servers and other web servers show the entire world with godlike power. We often use them for background layers in maps.
Interactive Edits: Edit tables, edit drawings and edit images in windows. Drawings and images visualize data from tables. To edit a drawing or an image, the table it visualizes must be editable and must have an index. If a table has a light gray background in all of the columns it is not editable. See the Editing Tables topic.
Contents pane: Shows key information about whatever window or layer is active, and opens panes providing editing and formatting. Use the Contents pane to assign an initial coordinate system or to reproject a drawing or image into a different coordinate system, to view field values for objects, to support editing and much more.
Transform Pane: Endless capabilities for manipulating data using point and click templates or SQL expressions. The power of SQL for everyone.
Select Pane: Select records and objects using point-and-click templates or SQL expressions. Save and recombine selections. Superb, intuitive selection of exactly what is desired.
Scripts: We can do anything with SQL. We can do even more with programming.
Viewer is read-only. Viewer cannot save, export, or print.
Save the project in a .map file with File - Save or File - Save As.
Export tables, drawings or images to many different formats.
File - Export Project to save a project in archival, maximally compressed .mxb format.
Linked items and data sources are automatically updated either immediately or when we save the project, depending on the data source.
Convert an entire linked data source, like an entire PostgreSQL server, in a single step into Manifold .map project format by right-clicking on the data source and choosing Export, to export to a .map project. Manifold will automatically harvest all the drawings, images and tables and create a .map project that stores them all.
Switch to a different project by, choosing File - Open or File - New. Manifold will prompt to save any changes before closing the current project and moving on to the next project.
Print a map, drawing, image, or labels window to PDF or hard copy using Print Preview, which creates a virtual layout on the fly that can be immediately printed.
Exit Manifold using File - Exit or by clicking on the red X button in the upper right corner. Manifold will prompt if any changes have not been saved.
Watch the videos in the Gallery page.
Read the topics in the Basics chapter.
Enjoy the Examples
Participate in the georeference.org user forum.
Master the main dialogs:
Automate your work
A great way to learn SQL with Manifold is to ask Manifold to automatically write SQL for you and then to copy and adapt what Manifold creates. See the SQL Example: Learning to Union Areas in SQL from Edit Query topic for an example. Use the web and read books on SQL. It's easy to learn and incredibly powerful.
The terms projection and coordinate system are used as synonyms by Manifold.
Getting it right on import: When importing data, Manifold will use whatever coordinate system the source says should be used for that data. Most modern formats used in GIS will automatically specify the coordinate system to be used. But older formats won't do that, so we have to assign the coordinate system when we import from those formats.
The Component pane of the Contents pane tells us at a glance if a coordinate system has been assigned OK. When a data source specifies the coordinate system to use, Manifold displays the coordinate system in black color. If the coordinate system is shown in red color, we must click the coordinate system picker button and choose Assign Initial Coordinate System. Do that immediately after import whenever a coordinate system appears in red text.
Manifold shows the coordinate system in black color, as in the Latitude / Longitude coordinate system seen above at left, when the component has been created with coordinate system information or if it has been imported from a format that specifies the coordinate system to use. When a component has been created without specifying the coordinate system or it has been imported from a format that does not specify projection information, Manifold will show the default Pseudo Mercator coordinate system as a placeholder in red color.
Tech tip: What projection is used by data can be difficult to determine sometimes. When downloading data from the web or other sources, always look for any accompanying notes or metadata information that says what projection is used for the data. If we have no idea what projection is used and the file is older data, a good guess would be Latitude / Longitude. For example, shapefiles that do not have a .prj file attached to specify what projection they use are often in Latitude / Longitude projection.
For a complete, step-by-step example, see the Example: Assign Initial Coordinate System topic.
Manifold applies the default projection listed in the Tools - Options dialog when creating new components. The factory default projection used by Manifold is the WGS 84 / Pseudo-Mercator (EPSG:3857) coordinate system that almost all web servers use. Newer GIS packages, like ESRI's latest ArcGIS offerings, also use Pseudo-Mercator as a default.
When we create a new, blank map, it too begins life using the Pseudo-Mercator projection. The map then automatically takes on whatever projection is used by the component that is the first layer added to the map.
Manifold uses Pseudo-Mercator by default because the modern way to do map backgrounds is use web servers to automatically generate the background map layer, and web servers like Google, Bing, or OpenStreetMap use Pseudo-Mercator. It makes sense to use that same projection by default for new components and maps in Manifold too. Many newer GIS packages also use the same WGS 84 / Pseudo-Mercator (EPSG:3857) projection by default, for example, ESRI's latest ArcGIS Pro products.
Another big reason to use Pseudo-Mercator as a default is that the units of measurement are sane, linear units: meters. That makes it more difficult for beginners to goof up measurements, as routinely happens when people use Latitude / Longitude without realizing that the units of measurement in Latitude / Longitude are degrees, which change size depending on latitude.
Older GIS packages often use Latitude / Longitude as a default. We can change the default projection in the Tools - Options dialog to Latitude / Longitude if we like, or to some other projection, like some State Plane projection mandated by our organization, if that is what we use most frequently.
Manifold, including Viewer, understands and can work with over 7500 coordinate systems, including all coordinate systems and transformations specified by the vast EPSG system, and the DBMS-specific SRIDs of major database systems. Manifold also knows essentially all transformation methods between coordinate systems, including all grid-based transformations (NADCON, HARN, HPGN, NTv2) known to EPSG, with over 170 transformation grids available for different parts of the world. Manifold also allows specifying custom coordinate systems, for endless more choices. We can use Reproject Component to reproject from any system to any other system, including sophisticated transformations of vector or raster data.
When importing from or linking to a data source that conveys coordinate system information Manifold will automatically use the coordinate system specified for the data, including any projections specific to the data source, such as SRID designations of coordinate systems used by a particular data source. See the Projections topic to learn how to work with projections in Manifold.
Some file formats utilize accessory files such as "world" files, or .PRJ files to convey coordinate information for formats, such as shapefiles, which do not automatically convey coordinate system information. When reading formats Manifold will automatically read coordinate system information from accompany files, if they exist, in the following order: "world" files, .PRJ files, .XML files (Manifold System 8.00 accessory file) and .MAPMETA files (Manifold accessory files). In the event of conflicting coordinate definitions the last read file wins, since the read order is in order of more rigorous definitions.
Manifold maintains coordinate system information in JSON format to enable easy interoperability with third party code. When exporting data to a file Manifold will write a .MAPMETA accessory file saving the JSON coordinate system information in plain text. When exporting to shapefiles, Manifold will automatically write a .prj file with projection information as well.
The usual way to work with drawings and images in Manifold is to add them as layers to a map. A map is just a viewport into whatever layers we have added to it. A map can have whatever projection we want, and it will automatically reproject on the fly, for display, the layers it contains from whatever projections they use into the projection used by the map. If we have a drawing in Latitude / Longitude and we want to see it in Pseudo-Mercator along with a Google Satellite background layer, we do not need to reproject the drawing. Instead, we simply drop it as a layer into a map that uses Pseudo-Mercator, and the map window will reproject the drawing on the fly for display in Pseudo-Mercator along with the Google layer. The reproject on the fly process happens so fast in Manifold that we can pan and zoom interactively without any delays.
When we want to reproject a drawing or image into a different projection, that is easy to do. In the Component pane we click on the coordinate system picker button next to that component, and we choose Reproject Component. The Reproject Component dialog lets us choose a new projection, either with a single click from a list of Favorites in the dropdown menu, or by clicking More... to choose the projection we want from many thousands of available projections from the full Coordinate System dialog. See the Reproject Component topic for step by step examples and full details.
Importing or linking a file will create Manifold infrastructure for what is coming in. For example, import an image from some file format like JPEG or TIFF and Manifold will create two components: a table component for the data plus an image component that displays the data in the table. Import an ESRI shapefile and Manifold will create a table for the data plus a drawing component that displays that data. The variety of data Manifold can import includes virtually every format and data source in existence. See the Big List of Formats and Data Sources topic for the huge list.
Importing a .csv file with one table in it will create a table. Importing or linking a file database like an .mdb could create hundreds of tables, queries and other components at once. Connecting to an enterprise class DBMS might involve thousands of items, neatly organized within the hierarchical structure of the DBMS as revealed by Manifold.
Launch 32-bit Manifold
Choose File - Import.
Browse into the folder where the file is located.
Click on the filename.
Press the Import button.
Launch either 64-bit or 32-bit Manifold
Choose File - Import.
Browse into the folder where the file is located.
Click on the filename.
Press the Import button.
Manifold uses Microsoft facilities to connect to all Microsoft Office formats, including legacy Office formats such as .db, .html. .mdb, .xls,and .wkx, together with newer Office formats such as .xlsx and .accdb. If Manifold cannot import from such formats, that means the Windows system we are using is missing the necessary facilities. Please see the Microsoft Office Formats - MDB, XLS and Friends topic for a solution.
Launch either 64-bit or 32-bit Manifold
Choose File - Import.
Browse into the folder where the file is located.
Click on the filename.
Press the Import button.
If necessary, launch Assign Initial Coordinate System from the Contents pane to specify the coordinate system used.
Modern GIS data formats will specify the projection used by the data. When a format provides projection information Manifold automatically will utilize that information to correctly set the projection used by the data.
When importing GIS data from a file format which does not provide projection information, when we open that drawing or image Manifold will warn us that was imported from a spatially-clueless format by showing the coordinate system read-out in red text in the Contents pane.
That tells us we must launch Assign Initial Coordinate System from the Contents pane to assign the initial coordinate system manually.
ESRI shapefile format uses 1970's technology but it is still the most widely used GIS format for interchange. A "shapefile" is an ensemble of at least three files, ending in .shp, .shx and .dbf, and, if we are lucky, a fourth file ending in .prj.
If a shapefile has a .prj to specify the projection, Manifold will read the .prj and the shapefile will be imported using the correct projection automatically. If a shapefile does not include a .prj file, we must specify the projection the shapefile should use. If we fail to do that the shapefile might look OK but it will be junk data that will waste our time later on.
Choose File - Import.
Browse into the folder where the shapefile is located.
Click on the filename that ends in .shp
Press the Import button.
For a step-by-step illustrated example, see the Example: Import a Shapefile topic. See the SHP, Shapefiles topic for additional discussion. See the Example: Detecting and Correcting a Wrong Projection topic for what happens when a shapefile is imported with the wrong projection.
As a practical matter, Manifold can address such large memory that usually we will run out of physical resources on a machine, like storage space, before we hit Manifold size limits. However, some limitations may be touched by users of very large data. See the Limitations topic for a current list.
Nothing is faster than Manifold / Radian .map format - Watch the YouTube videos to see the eye-popping speed of the Radian engine .map format used by Manifold Release 9.
.mxd Format - Manifold .mxd is a highly compressed, archival format that Manifold opens automatically and converts to .map format. See the Projects and .map Files topic.
Three Letter Extensions - Most file names in Windows end in what is called a three letter extension, which is usually three letters at the end of the file name following a dot . character. The three letter extension is one way Windows at times (but not always) keeps track of what a file is supposed to be. Unfortunately, by default Windows hides the three letter extensions of files and instead tries to associate files with icons of whatever program is normally associated with that file. This is confusing when working with the many file formats that Manifold and similar products utilize.
Therefore, please turn off the hiding of extensions by Windows. A typical way to do so in most versions of Windows would be from Windows Explorer, choose Tools - Folder options, press the View tab and then in the Advanced Settings pane ensure that the Hide extensions for known file types is unchecked. Press the Apply to Folders and then press OK. You will then be able to see extensions such as .map and others. See also the Essay on three letter extensions and why the default hiding of them by Windows is such a bad thing.
Why import and then work? Consider image formats: there are hundreds of different image formats, all with their own limitations. Instead of forcing us to learn a hundred different ways to work with images, taking into account the limitations of each format, Manifold does a conversion when bringing an image into Manifold so we only need to learn about images in Manifold. To export that image out to some other format Manifold will do a conversion outbound. When an image is imported into Manifold, it is no longer a JPEG or PNG or TIFF image. It is a Manifold image. If we want to save it as a TIFF Manifold will convert it into a TIFF on the way out.
Why create a table to import some small JPEG? Because everything is stored in a table in Manifold, even small images from a JPEG. That means nothing is hidden in some secret handshake form. All data is there in a table where the SQL you already know allows you to get your hands on the data and do what you want with it. Don't know SQL yet? That's missing a great opportunity to slice and dice data with the greatest of ease. You'll learn quickly enough (it's easy) and until you learn you can use Transform pane templates without knowing any SQL at all.
About .map files - Manifold stores data in .map format project files. A Manifold .map file can be interchanged by all Manifold products that are built upon Manifold's hyper-speed Radian engine. ".map" stands for Manifold Project, the file database format used for all Manifold database and GIS products. In a time when disk space is endless and cheap and human time is limited and expensive, .map files are designed to be as fast as possible and not as small as possible. Saving a big table or image in a .map file will usually result in a bigger file on disk than other formats but almost always the result will be far faster operation.
Important: When opening a .map file created by earlier Manifold products, such as Release 8, Manifold Release 9 always converts a pre-9 .map file into 9 .map file format. Using File - Save or File - Save As thereafter will save the project as a Manifold .map file which Manifold products before Release 9 (such as Manifold System Release 8 or prior) will not be able to read. Use File - Save As to save to a new name in Radian .map format without altering the original, pre-Radian .map file name.
Important: Linking a pre-9 .map file or creating a new data source based on a pre-9 .map file will also cause that .map file to be converted into 9 .map file format. Make a backup copy of any pre-9 .map files you wish to retain in the old format before you open them or use them in a Manifold project.
MAP files and MXB files - For everyday work we want our projects to open instantly, save instantly and operate at eye-popping speed. When exchanging data or saving archives for long-term, rarely used storage we want our projects to be as compressed and as small as possible. To serve both needs Manifold has two formats for project files: super-fast MAP and super-compressed MXB.
Manifold .map format provides phenomenal speed and capacity for everyday work. Manifold .map projects open instantly, save instantly and can be nested with links within projects to other projects with zero loss of performance. Manifold .mxb files are highly compressed files that archive a project in the most compact possible form. They are perfect for creating the smallest possible project file for exchange over Internet or for archival storage.
Manifold ODBC driver - The Manifold ODBC driver makes it easy for other applications to read/write Manifold .map files as well. See, for example, the Example: Create an ODBC Data Source with Windows topic and similar examples.
The Manifold ODBC driver is automatically installed when installing Manifold using a Windows Installer installation package, but it is not automatically installed when running a portable installation. When using a portable installation we must install the Manifold driver using the Help - About dialog. See the Installations topic for a quick guide to using portable installations and to installing the Manifold ODBC driver.
Dataports: A dataport is a Manifold module that interacts with file formats, databases and other sources of data. When we import data from a given file format, say, from shapefiles, we are calling the dataport for shapefiles.
Please note: While it may be convenient to leave data within original formats, such as shapefiles as often encountered in GIS, doing so means living within the limitations imposed by those formats. Older formats may be fine for small amounts of data but when larger amounts of data are involved they can be slower than Manifold .map files and they often have limitations such as no ability to mix vector types, limits on data types, limits on size or other limits.
Using .MAPCACHE can deliver impressive speed even with older formats but even so using Manifold .map format is almost always faster, usually much faster, for larger files and .map format does not suffer from the content limitations of older formats.
Read-only layers - Projects can contain read-only components. For example, an image layer from a Google web server will be a read-only layer in our maps (Of course - Google does not let us edit the images and maps that Google Maps serves.) For example, we can create a data source from a database and check the read-only box to make everything we bring in from that database, such as drawings or images, read-only. Some formats are always read-only when linked into a project. When the focus is on a read-only layer, commands that require writing, such as a Paste command or buttons to create areas, lines, or points, will be disabled, since they cannot be used.
Copying and pasting between sessions - When copying and pasting between different Manifold sessions remember to copy all parts of a component. An image component, for example, is just a display module to show the contents of the associated table which stores the tiles for that image. To copy an image from one Manifold session to another we must copy and paste both the image as well as the table for that image.
Docked and Undocked - Manifold allows us to undock panes and windows, to resize them and to move them around our Windows desktop as we like. Shift-click the title bar of a docked window or pane to undock it. Shift-click the caption bar at the top of an undocked window or pane to dock it again. We don't have to keep undocked Manifold windows and panes within the boundaries of the main Manifold desktop.
Reserved names - All names starting with mfd_ (case not significant) are reserved for use by the system. Names for fields, indexes, constraints, tables, components other than tables, properties... everything. Do not name anything beginning with mfd_ or MFD_ or in any upper or lower case combination of those characters.
Mnemonic names - It helps to name data sources to know their origin at a glance. In the example recommended above we use Books MDB as the name of a data source so at a glance we are reminded the data source is an .mdb file having to do with books.
But if we forget, hovering the mouse cursor over a data source displays a tooltip that shows the origin. If the data source has information in the Description property the description will be shown in that tooltip instead.
Saving Data Sources - The Project pane tracks any unsaved changes for data sources that support saving, including the root .map file itself. Data sources with unsaved changes will be displayed using a different icon that shows an asterisk * in the lower right corner of the icon. Making changes via a script to a data source that supports saving may require a few seconds before the icon is updated. If a data source does not support saving the icon will not change and the Project pane context menu command for that data source will not include a Save command.
Manual data entry - The idea of manually creating components and manually inputting data is not so far-fetched as it may seem. For example, we can create points in a drawing by clicking on locations in a drawing in a map using a lower layer (a satellite image or map from a web server) as a guide. Whether we are marking trees, fire hydrants or archeological relics it is often possible to rapidly click and create hundreds of points or areas or other features per day. Over a surprisingly short period of time many thousands of records can be accumulated as the result of manual data inputs.
Table Nomenclature - When writing about tables we will often use the words row and record interchangeably and also the words column and field interchangeably.
CPU Parallelization - Manifold automatically runs parallel for internal Manifold tasks and for Transform pane templates and similar operations, using all of the CPU cores available in your system in parallel. When writing queries manually using the Command Window make sure to add a THREADS SystemCpuCount() command to the query to automatically parallelize the query to use all CPU cores in your system.
GPGPU - Manifold automatically uses NVIDIA GPUs for massively parallel computation. NVIDIA GPUs of Kepler class or more recent which NVIDIA supports with CUDA are required. See the GPGPU topic for details.
Open a .map file from a command prompt - For users who want to use a batch file to launch Manifold or Viewer with a particular .map project file, Manifold supports the usual Windows way of opening a file as a command line argument for the opening program: Running manifold.exe myproject.map will launch Manifold and open myproject.map in Manifold. Use double quotes around the file name if there are any special characters or spaces in the .map file name. For example, we would write manifold.exe "-this is my latest project.map".
Projects and .map Files
Importing and Linking
User Interface Basics
How to Edit a Single File
View - Panes - Project
Assign Initial Coordinate System
Examples - Do not miss! Browse through the many examples for step by step tutorials.
Example: Project Pane Tutorial - In this example we take an extended tour of the Project pane, engaging in a variety of simple but typical moves that are illustrated step by step.
Example: Import a Shapefile - ESRI shapefiles are a very popular format for publishing GIS and other spatial data. Unfortunately, shapefiles often will not specify what projection should be used. This example shows how to deal with that quickly and easily.
Example: Closing without Saving - An example that shows how File - Close without saving the project can affect local tables and components differently from those saved already into a data source, such as an .mdb file database.
Example: Spectacular Images and Data from Web Servers - A must see topic providing a gallery of views illustrating how Manifold can use web servers such as imageservers and other free resources to provide a seemingly endless selection of spectacular background maps, satellite images and GIS data with nearly zero effort.
Example: An Imageserver Tutorial - An extensive tutorial showing step by step how to add new data sources that are imageservers, how to show them as layers in a map, how to create a new drawing that matches the projection of the map and how to trace over what is seen in an imageserver layer to create an area object in the drawing.
Example: Reproject a Drawing - An essential example on changing the projection of a drawing, either within the drawing itself, or by changing the projection of a map window that shows the drawing and on the fly reprojects the drawing for display.
Where Manifold Data is Stored
Accessory Files Created
The MAPCACHE File
Keyboard and Mouse Quick Reference
For Maximum Reliability