By way of laying the groundwork for describing the XMap to Google procedure, let’s begin by developing a simple hypothetical scenario. You have been tasked with capturing the location of, and collecting critical information about several sites, and you have been informed that your data must be presented in such a way as to make it available to the required stakeholders. On the assumption that the target audience is not GIS aficionados, your options are limited to a static printed map or a more universal online data delivery mechanism, which is where Google comes in. In composing this article, it is hoped that you can translate this simplistic scenario into a real-world application that reflects the typical workflow in your workplace.

To begin the process, the requisite GIS layer is created in XMap and populated with all of the required attribute fields. For our simple scenario, the point layer will include fields for the site name, type and an arbitrary numeric value to be assigned to each point.

To begin the process, the requisite GIS layer is created in XMap and populated with all of the required attribute fields. For our simple scenario, the point layer will include fields for the site name, type and an arbitrary numeric value to be assigned to each point.

Next, an XMap Form is created that will allow the data collection to be performed using a handheld Earthmate PN-Series GPS receiver. Step-by-step instructions on how to create XMap Forms are available here.
This empty layer is then deployed to a PN-Series device and all of the site information is recorded using the Waypoint button and the subsequent form. When complete, XMap’s merge function efficiently integrates this field-collected data into the original layer.

That’s the easy part; now we need to share our data.

Before exporting a KML file it is a good idea to assign a label to each object in the layer. The absence of an assigned label will result in Google applying a generic name to each point. In this case the field called Site Name will be used as a label. Click the Tools button in the GIS Workspace and select label to choose the label field.

The symbology applied to a point layer in XMap is not carried through to either Google Earth or Google Maps so there is no need to customize the symbol type before generating the KML file. The style applied to lines and polygon layers is recorded in the KML file and therefore your symbology selection for these data types will be reflected in the Google map.

To generate the KML file, simply click the Layers button in the GIS Workspace and select Export… In the resulting dialog box, use the Save as type dropdown list to select OGC KML format and type a name for your file. Unlike a shapefile, all of the constituent parts of a KML including the geometry and the attributes file are contained in a single file.

Google offers two choices for importing and displaying KML files, Google Earth and Google Maps. While they share many of the same functions and interface features they differ in terms of the platform within which the maps and data are rendered. Google Earth is a downloadable application while Google Maps is a browser-based tool. In both cases, the actual maps are delivered via the web.

For this scenario we will describe the process of creating an interactive map containing our collected points within Google Maps. This will allow us to share the data by simply sending each party a URL instead of requiring each recipient to install a local version of Google Earth. This procedure requires that the person creating the map has a Google account (or a Gmail address).

Follow these steps to publish your XMap-created points:

1. Type http://maps.google.com/ into your web browser.
2. On the left of the page, click the My Maps link. First time users will be prompted to login; returning visitors will see a list of previously created sites.
3. Type a name for your site and, if necessary, type a brief description.
4. Select the appropriate privacy settings. Normally Unlisted is the preferred option as this ensures that only those with access to the URL will see your data.
5. Click the Import button and in the resulting dialog box, click the Choose File button.
6. Select the KML file previously created in XMap. Note that there is a 10MB limit per file which, for large layers, may necessitate segmenting the original GIS data into several sections. Multiple KML files can be uploaded to each map.
7. Click the Upload from File button. The Google map automatically redraws to display your points and a list of the records is generated on the left side of the screen
8. Click a point on the map to display the attributes for that point and, when in Edit mode, to manually adjust the symbolization.
9. Click the Done button to create the map

Each Google Map is assigned an unique URL which can be emailed to all of the required recipients. Use the Email button at the top right corner of the map window or click the Link button to copy the URL. Web developers can even use the included html code to embed the map into an existing web site.

View PN-40-Collected Data in Google Maps.

A description of the development and management of a GIS is often condensed into a simple three-step process: data collection; data processing; and data sharing. The PN-Series GPS receivers are ideally suited for the first stage; XMap provides a powerful set of tools for stage two; and with the inclusion of KML support in XMap 7 Google’s online mapping services offer a readily available option for stage three.

Fortunately, the solution to this temporary predicament is usually quick and painless. The panic button is not needed.

The problem stems from the fact that XMap employs a Microsoft SQL database to store GIS data and occasionally, for reasons often too complex and bewildering to explain here, XMap refuses to “talk” to SQL and vice versa. The problem is easily solved by reintroducing both parties.

This reintroduction can be initiated in XMap from either the Manage Layers or the Import Layer window, both of which are accessed by clicking the Layers button above the Workspace table. In either case, select Other from the database drop-down list to display the Attach Database window.

Usually, the errant SQL server will be listed in the server drop-down list and will appear as either (LOCAL)\XMAP* or [your computer name]\XMAP* (* represents the version of XMap on your computer). If this is the case, simply select the server from the list, make sure Windows Authentication is checked, and click the Connect button. After a few seconds, the database list will display all of the XMap databases on your local server. For new XMap users, this list will be limited to the preconfigured database entitled DeLormeSampleDB. After selecting this or any other available database, click the OK button and continue importing or managing your layers as before.

It is likely that most of you can now stop reading this article and go back to work, secure in the knowledge that you have solved your database connection problem. However, there is a small group of you who will probably want to read on for the simple reason that your server list in the Attach Database window is conspicuously empty and you could not perform the succeeding steps.

If you are one of those unfortunate XMap users, there is an additional but very simple step that must be taken. In the blank server window, type (LOCAL)\XMAP* (* should be either 7, 6, or 5 depending on the version of XMap that was first installed on your computer and, correspondingly, the version of SQL that was created) and continue with the steps outlined above.

On rare occasions, the two solutions described will fail to rectify the database connection issue; this is usually because the SQL service is not running. Often, this problem occurs after an update to your operating system during which Windows fails to restart the service. The solution for this problem takes place outside of XMap.

1. From the Start menu, right-click My Computer and select Manage.
2. Click the plus sign next to Services and Applications and click Services.
3. In the Services window, right-click SQL Server (XMAP*) and choose either Start or Restart.

Your database should now be available in XMap.

If the XMap instance of SQL is not listed in the Services widow, you will need to reinstall it from your XMap install disk. Instructions are available here.

Thankfully, the solutions for the common XMap database connection problems are reasonably straightforward and usually the disconnection problems will not reoccur.

The word Geographic obviously means that it relates to location; Information tells us that there is some sort of data related to that location; and, finally, System implies that we are dealing with more than just a map or even mapping software—but, rather, a multi-faceted process that allows us to consider the data in the context of its location. Therefore, a GIS is simply a system for analyzing information as it relates to location.

So can it be argued that a map generated using the Draw tools in XMap or any other DeLorme software is a GIS? Certainly the Draw tab provides a variety of tools placing points, lines, and polygons on the map and for customizing the symbolization of each object. What’s missing is the ability to assign data or attributes to these objects. The flag on the map might convey to the viewer that there is an item of interest at that location, but it will not paint the complete picture by offering access to the relevant data about that item.

In most cases, the step up from simple mapping to a fully-fledged GIS is fairly straightforward. If you have already taken the time to create a draw layer that shows the location of your data objects, you are halfway there. All you need to do is import the draw layer into the GIS tab in XMap, then either manually add as many different attribute fields as you need or, better yet, import and link existing data in such formats as Microsoft^® Excel, Access, or even text, and then automatically assign each row of data to the appropriate point.

Before long, you will realize the benefit of having your data geographically assigned in this way. Through processes such as classification and querying, you will be able to discern patterns in your data that would otherwise have gone unnoticed. Furthermore, data stored in a GIS format can be easily shared through a common database connection, within which permission settings will allow varying levels of access. This helps ensure that everyone in your organization has the latest versions of your data.

To read more about the benefits of a GIS click here.

If you have a question that you would like to have answered in the DeLorme Professional Newsletter XMap Q&A section, send it to newsletter@delorme.com with XMap Q&A in the subject line.

At the risk of jumping in at the deep end, this article will bypass the XMap Forms setup process and discuss the use of this technology in real world situations. If you would like to read more of the background information, refer to this article from the November 2009 newsletter or visit the XMap Forms page on xmap.com.

The following are some examples of XMap Forms at work in a variety of fields.

Oil and Gas Pipeline Inspection and Maintenance

One of the challenges in the energy sector is that a lot of work is done in remote and often inhospitable environments. DeLorme has addressed some of the specific concerns of the oil and gas industry by developing GIS tools that are ideally suited for field technicians and that provide a mechanism for collecting and submitting data to a central GIS. XMap’s synchronization tool, which offers an efficient means to transfer updated, location-specific data to work crews at the jobsite, becomes even more powerful when those same technicians can remotely collect information about their field assets and automatically integrate this data in to an Enterprise database at the corporate office.

In this context, XMap forms functionality transforms the Professional version of XMap from a field data viewer into a powerful data collector. These field-based personnel do not need to have an intimate knowledge of the workings of a GIS; instead, they simply fill out the required information about a pipeline at each location using preconfigured dropdown lists and simple text entry. XMap Forms, as an add-on feature of the synchronization process, empowers field technicians to become direct participants in the process of building and maintaining the company’s GIS infrastructure.

Natural Resource Management and Habitat Monitoring

When considering the protection of areas of environmental concern, two key questions must be addressed: Where is it? and What is it? Thankfully, the form-based data collection on the PN-Series GPS receivers can help answer both questions. GPS has long been an important component of the field biologist’s toolkit. When collecting data on such things as nesting sites, it is critical to note specifically where each nest is located as well as any additional site-specific information. Most GPS receivers offer limited data collection functionality and usually allow only a label and a brief comment to be assigned to each collected waypoint. Any additional information must be hand-written and manually assigned to each point back at the office or lab. Needless to say, this process is highly susceptible to human error and to the creation of incorrect data that may impact any derived scientific study.

The PN-Series GPS receivers are comparable to many handheld GPS devices on the market today in terms of price and ease of use. The distinction lies in the fact the entire process of field data collection, including the collection of a complete set of attributes for each point, can be performed in the field. The structure of the data collection form ensures that each attribute is consistent and it allows the resulting data to be directly integrated into a GIS, eliminating the need for any manual transfer of additional detail from handwritten notes.

Crime Mapping and Evidence Collection

In recent years, GIS has found a firm foothold in the field of criminal investigation and forensic analysis. It is often the spatial nature of the collected evidence that provides the essential clues for solving the crime. To ensure this process works effectively, evidence must be accurately cataloged, preferably onsite, so a robust location-based data collection device is essential. The PN-Series GPS receiver works well in this situation because it is rugged, waterproof, and compact. Furthermore, using XMap Forms offers the means to create a complete database of information about the crime.

Criminal investigators are usually called into action at a moment’s notice, so having a preconfigured form is strategically important. Because forms reside on the external SD card inserted into the PN-Series device, a library of different forms can be created and the appropriate form activated for a given situation.

Highway Maintenance and Repair

Anyone who lives in the northern tier states of the U.S. or any similar cold climate zone will attest to the fact that the roads take a beating in the winter months. Come spring, work crews are quickly deployed to patch the potholes and, if necessary, resurface the pavement. Before this work is undertaken, a thorough inspection process must be performed to ascertain which areas are of most concern and to document the level of damage, often with accompanying photographs.

XMap Forms deployed on a laptop computer in the inspection vehicle is ideally suited for this task. Each damage location can be quickly assigned as a GIS point and, using a series of preconfigured attribute fields and drop-down lists, the relevant information can be attached to each location. Photographic evidence can also be associated with each collected point after uploading images from a digital camera. The form interface offers a simple upload button which copies the photograph or any other file into the GIS database.

After the inspection work is complete, XMap’s synchronization function automatically transfers the points and the accompanying photographs to the department’s GIS administrator. With immediate access to this information, maintenance managers can allocate resources quickly and effectively.

Utility Pole Data Collection

To the layperson, all utility poles seem to be the same, but to a utility technician, each has its own characteristics and hardware configuration. Cataloging this information is essential for maintenance planning, service upgrading, and emergency preparedness. Collecting data on utility poles can be a laborious and time-consuming process, but using XMap Forms on either a laptop computer or on a PN-Series device, the process is not only faster but much more accurate.

Many of the attributes associated with a utility pole inventory will be consistent for each pole. For instance, most of the poles might be owned by one specific utility agency or company, so it is inefficient to manually add this attribute for each point. XMap Forms offers a simple solution for this. If necessary, each field can be assigned an initial or default value in XMap, which means the form can be pre-populated with the most common values and edited only if needed.

While most poles are likely to be adjacent to a road, allowing the collection of data by vehicle, there are occasions when the technician is required to venture off-road to gather the necessary information. In such situations, XMap Forms on both the in-vehicle laptop and on the handheld PN-Series GPS receiver can be used to populate a single GIS layer with pole data. At the end of the day, the technician simply merges the data from the PN and the computer and a complete GIS dataset is created.

These scenarios describe some typical uses for XMap Forms technology; however, there is virtually no limit to the ways in which this innovative data collection tool can be put to work. As always, we want to hear from you. If you are interested in sharing an account of how you use XMap Forms, please email prosales@delorme.com with the details.

Several factors complicate this task:

• The field area in California’s Mojave Desert is topographically complex
• It has been heavily dissected by faults, which have obscured many of the geologic relationships between the different sedimentary layers
• Research first began in this area a century ago and in the intervening years, many museums and universities collected large numbers of fossils and numerous geologic maps have been created. Needless to say, accessing and analyzing all of this data is time-consuming.

On his first research trip into the field, Ian was armed with little more than a topographic map and an old handheld GPS receiver, whose limited functionality simply allowed him to determine his location as a set of UTM coordinates.  Due to the topographic complexity of the area, Ian found it difficult to maintain his positional reference on the map, so his first year’s field work was not very productive. Ian needed a better GPS receiver that provided field access to his GIS data.

Back at OSU, Ian built a GIS database for his area of study using ESRI’s ArcMAP. This helped organize and synthesize the years of collected data and maps that have been accumulated by various research and exploration teams. Before his second trip, Ian discovered the Earthmate PN-40 GPS receiver, the latest device from DeLorme. It offered mobile access to aerial imagery and USGS topographic maps downloaded from the online DeLorme Map Library. Since the USGS topographic maps downloaded from Map Library are scanned and geo-referenced versions of the same paper quadrangle maps he had carried during his previous field trip, it was like having a “you are here” dot that he could use to quickly determine his location on the map.  This significantly decreased the amount of wasted time on the second trip, but there was still a disconnection between his field work and his ESRI GIS research.

While Ian was on his second research trip, DeLorme introduced the Earthmate PN-40 ESRI Extension, which proved to be the final piece of the puzzle. This extension generates a raster image of a map view in ArcMAP, which is then uploaded to the PN-40 as a base map. This was an ideal solution for Ian as he was able to generate a single file, which incorporated the relevant GIS layers and provided an extremely useful alternative to the standard aerial imagery or topographic maps. This inexpensive tool provided an easy way for Ian to utilize the work he had performed in ArcMAP in a field environment. Ian also used DeLorme’s XMap to import ArcMAP-generated shapefiles and convert them for direct transfer to the PN-40.

“With the PN-40 I was able to access a hundred years worth of field data and digitized geologic maps,” said Ian after his latest research trip, “All while standing on top of a ridge being pummeled by a cold December wind. Access to this much information on the ground allowed me to quickly assess the validity of previous researchers interpretations, making it possible to do the sort analysis in the field that historically had to be done at the end of the day back in camp, or more commonly back in the lab. Currently, I’m digitizing more maps and can hardly wait until spring when I can get back out into the field with the Earthmate PN-40 and the PN-40 ESRI Extension.”

This type of utility in a small, easy-to-use, handheld device is the sort of thing that could barely have been imagined just a few years ago. The combination of ArcMAP and the Earthmate PN-40 provides a powerful GIS data management tool and field-based access to GIS layers.

For more information on the Earthmate PN-40 and the ESRI extension, visit: www.delorme.com/esri

The target of this article is for those XMap users who fall somewhere in the middle: organizations that are large enough to realize the importance of sharing data among their workforce but small enough to get away with not hiring a full-time I.T. manager. Judging by the calls that are received by XMap technical support and product specialists, this group represents a sizable percentage of XMap users.

Sharing GIS data often involves the simple act of exporting, delivering, and subsequently importing Openspace layers. Under this scenario, each user of XMap is their own data manager and their local version of SQL acts as a single-user data repository.

While the export/import process is a reasonably effective data distribution solution in situations where data is shared on an occasional basis, it does have its limitations and potential drawbacks if layers are continually changing hands:

• It is time-consuming and inefficient
• It requires the action of the data host to physically extract the data; if that person is unavailable, others cannot access the data
• Multiple versions of a particular layer might accumulate in each user’s database causing confusion and possible storage capacity issues
• Most importantly, edits made by each individual user will not be reflected in other users’ versions of the layer

An obvious solution is to develop a more collaborative working environment in which a single version of each layer is maintained and updated in a universally accessible location. A prerequisite for developing this type of data management model is to have all of the required users on some sort of network. This network does not have to be overly complex and for small organizations, it can be easily set up using off-the-shelf hardware.

Once the network has been established and the required users have been granted the appropriate access, a shared XMap database can be created. For this process, there are two possible approaches:

• All users can be given access to an existing XMap database on an individual’s computer
• A new instance of Microsoft SQL can be installed on a dedicated computer or server.

The benefit of the first option is that no additional hardware needs to be purchased and no additional databases need to be built and maintained. The shortcoming of this approach is that it doesn’t solve the problem of accessing data when the owner of the host database is away from the office.

If it is feasible, dedicating a continually accessible computer to act as a central SQL server is a much better approach. How is this instance of SQL installed and how is the requisite XMap database created? Thankfully this part is easy.

As previously mentioned, all versions of XMap include by default, an instance of Microsoft SQL on the same hard drive on which the software was installed. During the installation process, SQL is installed before XMap itself. This version of SQL is freely distributed by Microsoft so there is no limitation or license restriction applied to its distribution. Therefore, the simplest way to install SQL on the server is to insert the XMap disc in an available DVD drive and allow the installer to run the prerequisites. After a few minutes, the installer will ask for an XMap license number at which point, the installation can be terminated using the Cancel button. The XMap-ready instance of SQL remains, in spite of the fact that the software itself was not installed.

Using any connected version of XMap, a database can now be created and access granted to all XMap users. The simplest way to create a database on this new server is to create, import, or copy an existing layer. Instead of adding the layer to a local database, choose New under the Target Database dropdown list, type the name of the server (usually [computer name]\XMap7) and type a database name.

Other XMap users can then access the layers in this database by selecting Manage from the Layers menu in the GIS tab and choosing Other from the Source Database dropdown list. After typing the server name as noted above and clicking the Connect button, a list of available databases on the server will be displayed. Back in the Manage Layers window, the available layers can now be added to the Workspace.

This collaborative environment requires a certain level of workflow management to ensure that multiple users are not trying to simultaneously edit the same records. In such cases, the edits performed by the last user to click the Commit button will be the ones applied to the layer. Thankfully XMap includes several tools to help administer this workflow process.

The Database Manager, which is accessed from a button in the Workspace in XMap, allows the administrator to offer database permissions and assign roles (Server User, Database Creator, or Server Administrator) to each user. It can also be used to initiate the database synchronization process that allows GIS layers to be automatically delivered to the local database on each user’s computer so they can work in a disconnected environment.

The layer Check-out/in process can be utilized to assign data within a specified geographic area to an individual user who can subsequently edit, add, or delete records within the limits of that area. While this data is checked-out, the corresponding area in the original layer is locked for editing ensuring that multi-user concurrent editing is avoided.

If an individual user simply wants a copy of a centrally stored layer to work on independently or to take into the field, the easiest way to achieve this is to create a duplicate version of the layer in a local database. To do this, select the required layer in the Workspace, click the Layers button, click Create, and choose Copy Layer. In the resulting window, make sure the local database is selected from the Target Database dropdown list.

Setting up a shared working environment is not a difficult process for small companies or organizations. For XMap users, the benefit of being able to effectively share data and centrally administer key GIS layers results in a more efficient workflow.

For more detailed information on XMap from the I.T. perspective, read the XMap Admin Guide.

Creating XMap Forms
First and foremost, you need a copy of XMap 7 GIS Enterprise or XMap 7 GIS Editor to create XMap Forms. However there is a caveat. XMap Forms can only be developed in a layer which resides within an Enterprise database, which can only be created using the Enterprise version of XMap. If, as a user of XMap GIS Editor, you have access to such as database within your company or organization, you are all set. If you are a standalone Editor user, you will need to upgrade to Enterprise to create XMap Forms.

If your intended use of XMap Forms entails simply creating forms as a convenient mechanism for adding, deleting, or editing records in your own layers, you need read no further. XMap provides all you need. If, on the other hand, you intend to deploy XMap Forms to your field technicians or mobile workforce, or if you plan on collaborating with other XMap users through the use of XMap Forms, read on.

XMap Forms on the Earthmate PN-40
As previously noted, XMap forms can be used on the Earthmate PN-40 or in XMap. If you intend to use the handheld GPS receiver for data collection, you need to purchase a device for each user. However a single copy of XMap can be employed to distribute forms and any corresponding data to multiple PN-40s and subsequently to upload and manage field-collected records. Typically this process is initiated by individually connecting each device via the included USB cable to the computer on which XMap is installed. Data collected remotely can also be emailed in gpx format to the administrator and manually merged into the master GIS layer.

XMap Forms in XMap Professional
It should be noted that XMap Professional cannot be used to create or manage XMap Forms. Forms created with the Enterprise or Editor versions of the software can be used in XMap Professional. The only way that form-based data collection or editing can be initiated in XMap Professional is through the layer synchronization process. In other words, if you simply export an Openspace layer in which a form has been created, and import that layer into XMap Professional, the form will not be accessible and data cannot be edited in any way. In order to unlock the form, a valid forms license must be purchased for each end-user. This small investment significantly increases the value of XMap Professional by transforming it from a GIS data viewer to a field data collector and editor.

XMap Forms licenses are administered through the Database Manager, which also controls access to synchronized layers for each user. A company will typically purchase a forms license for each copy of XMap Professional, however it is also possible to reassign a license to a different XMap user, which in turn will disable the forms functionality for the original user.

To summarize, XMap Forms functionality in XMap Professional requires a copy of the Enterprise edition of the software to establish synchronization and to create the form, a copy of XMap Professional for each end-user, and a forms license.

XMap Forms in XMap GIS Editor or XMap GIS Enterprise
Unlike with XMap Professional, layers containing XMap Forms can be manually shared among users of the Enterprise and Editor versions of the software without the need for synchronization or a forms license. If a layer containing a form is exported in Openspace format, this layer and the accompanying form will be available to anyone using XMap GIS Editor or Enterprise.

XMap Forms provides a user-friendly facade for your GIS layers and significantly simplifies the process of remotely collecting and editing GIS data. In certain instances, XMap Forms can be used right out of the box. If forms capability is to be utilized by a remote workforce make sure you include the required forms licenses in your purchase.

For more information and pricing, visit www.xmap.com/forms or call 1-800-293-2389

It is worth noting that the widespread adoption of XMap by wind energy companies was not because DeLorme proactively sought out this opportunity but rather that wind power companies sought out XMap. It was a perfect fit. XMap offered just the right level of GIS functionality, it was affordable, and it could be quickly learned by anyone with basic computer knowledge. As the word spread, XMap became the mapping application of choice for hundreds of wind energy companies in the U.S. and beyond.

Far from being specialists in the industry, DeLorme has learned a lot from working with wind energy companies. Much of this learning comes from direct contact with our customers and from asking the fundamental questions about how they use the product. The following applications, summarized from customer conversations, are typical for XMap in the wind energy industry.

Wind Potential Analysis
The most important consideration when planning a wind energy project is the availability of wind at the appropriate strength and consistency. This wind potential has been analyzed and mapped by wind resource specialists and the resulting data is usually available in shapefile format. The National Renewable Energy Lab offers a version of this data for most U.S. states at no cost. Shapefiles can be imported into XMap and the classification tool can be used to develop thematic maps showing areas of maximum potential.

Property Research and Acquisition
Property ownership information is becoming increasingly important for a wide variety of GIS applications. Local governments are responding to this demand by developing and updating digital parcel databases. When planning a wind energy project, the ownership and status of the targeted and adjacent properties are crucial considerations that could potentially derail a project before it starts. XMap offers two alternatives for creating a property layer. In those areas where digital files like shapefiles are available, you can simply import the layer. Unfortunately, many wind projects are planned in more remote areas where such data is not available; the alternative is to scan any available paper maps and use XMap’s ImageReg tool to create a geographically referenced raster or image layer as a base map.

Terrain Analysis
In the wind industry, terrain is an important factor in the project planning process. Topography can have a marked impact on the local wind patterns, which can cause problems with turbine installation. Also the terrain has a direct impact on some of the logistical decisions related to transportation, construction, and other project challenges. The topographic base map in XMap includes a digital elevation model which allows the representation of terrain through contours, shaded relief, 3-D modeling, and linear profiling all of which contribute to a more complete picture of the project site.

Optimal Turbine Placement
Factors to consider when choosing a turbine site include surface and sub-surface geology, proximity of obstructions, access to transmission infrastructure, accessibility for maintenance, and much more. XMap’s GIS functionality allows the simultaneous consideration of numerous layers of relevant information to aid in this problem solving or decision making process.

Impact Analysis
While harvesting the wind is generally considered to be a clean source of energy, it still exerts an impact on the environment and often on the surrounding community. Fragile ecosystems are sometimes threatened during construction and operation, turbines are installed close to avian migration paths, for some, the visual or audible impact can be problematic. XMap’s buffer tool is used extensively in this type of analysis where a defined area around a project or conversely, around an adjacent habitat can be mapped and potential problems addressed to help mitigate any disputes.

Infrastructure Planning
The visible aspect of the construction of a wind project is obviously very conspicuous; however, the wind turbines are only half of the story. Developing a wind farm also entails developing roads, local transmission lines, maintenance facilities, and more. XMap’s CAD tools provide a straightforward way to map this infrastructure and to share the maps or data layers with contractors or construction crews

Community Outreach and Collaboration
A vital aspect of any wind energy project is engaging the local community. Often this outreach effort involves the presentation of the project details through maps and other printed materials. XMap’s printing functions provide the tools necessary to produce professional quality maps of any size incorporating imagery, GIS layers, topographic maps, and any other available data.

Compliance
After speaking with many wind energy companies, it has become abundantly clear that one of the biggest hurdles to the success of a wind project is regulatory compliance. XMap plays a role in overcoming this obstacle by providing the means to import, overlay, and analyze the appropriate data to ensure compliance. It also offers efficient presentation and data delivery tools to ensure that the supporting documentation and reports are supplemented with the highest quality maps.

Project Management
After construction is complete and a project is brought online, XMap continues to play a role. Turbine performance, maintenance schedules, and repairs can all be managed using XMap’s spatial database functionality. The new embedded document tool is ideally suited for this type of work. Reports, schematics, photographs, and virtually any other type of file can be assigned to a specific point on the map and can be retrieved, edited, and saved as needed.

Industry Research
At a much higher level, XMap is a perfect tool for conducting research on the wind industry itself. For example, it can be used to analyze the distribution of wind farms across the country and to visually represent the production capacity in each state. Information garnered from such studies can help pave the way for future wind energy development.

At DeLorme, we continue to learn from the expertise of our customers in the field of wind energy and in many other industries. This knowledge inspires us to design and develop products that provide value, encourage productivity, and promote efficiency.

Synchronization
XMap’s synchronization process provides a simple tool for field personnel to automatically receive updates to GIS layers to which they have subscribed. The initial setup involves assigning access to the Enterprise database for each required user or each member of a designated Windows® group. This process is managed using XMap’s Database Manager application, which can be accessed from the Workspace in the GIS tab. A subscription file is generated and sent to each user for the purpose of establishing synchronization between their local XMap database and the central database. This process is initiated by simply double-clicking the file after it has been received.

Each user or group can be assigned a unique combination of layers by the data administrator and this selection can be modified at any time without the need to update the subscription file. For instance, if a field worker is reassigned to a new territory, the data administrator can simply clear the check boxes for the layers to which he or she was previously subscribed and then select the layers that are appropriate for their new assignment. Next time synchronization is initiated, the old layers will be removed and the new layers will be added to their Workspace.

Synchronization was originally designed as a means for field technicians to receive continually updated layers in a read-only format. In other words, regardless of which version of XMap is being used, the database that is automatically created to receive the synchronized layers does not offer editing functionality. However, the process does enable a redlining function that allows onscreen mark-ups to automatically be submitted to the Enterprise database during synchronization. These redline layers are essentially draw layers that can be scrutinized by the GIS manager to help ascertain if the referenced GIS data should be updated.

With the introduction of the optional XMap Forms capability in XMap 7, synchronization has assumed a higher level of functionality. If XMap Forms is enabled for a database user and a preformatted form is deployed along with a synchronized layer, the field worker can edit or collect new data points and can assign attributes based on any constraints that have been imposed by the data administrator. Edits to the data are then automatically applied to the original layer in the Enterprise database during synchronization. XMap Forms transforms synchronization from a remote data viewing function to a full data collection tool.

Data Check-Out/In
The data check-out and check-in process was developed to provide multiple XMap users the means to concurrently edit a single layer by assigning a specific geographic territory to each user. Multiple check-outs can be created from a single layer however their geographic coverage cannot overlap. When an individual is working within a defined territory, no one else can update any of the GIS objects within that area until that section is checked in.

The act of checking out a portion of a layer creates a new subset of the original layer that can be copied to a remote database while locking the assigned territory in the original layer. The new layer inherits all of the properties of the original including the available attribute fields, the classification and symbolization settings, and any queries that have been created. Most importantly, the recipient of a checked-out layer has full control over the geometric characteristics and the attributes of the layer and can add, delete, or edit points, lines, or polygons. For this reason, the check-out/in process typically involves the transfer of data between the Enterprise and Editor versions of XMap. There is limited value in checking out a layer to a user of XMap Professional because that application does not provide the requisite editing functionality.

The data check-out process is managed using the Check-out/in function in either the Enterprise or Editor versions of XMap, although the originating layer must be in an Enterprise database. A scalable grid is used to select specific tiles of data on the map and after the new layer is created, the assigned grids are highlighted to indicate their contents and cannot be edited or concurrently checked out to another XMap user.

The checked out layer must be assigned to a database other than the one containing the original layer. A data administrator can either create a new database on the same SQL server or, with the appropriate permissions, can create the layer in the local database of the end user. After this new layer has been created, the remote XMap user can update the geometric and attribute values of the layer within the assigned geographic limits.

Before an updated section of a layer is checked in, the data administrator can add it to their workspace to ascertain the quality of the work. If it is deemed acceptable, they can simply click the Check-in button to replace the original data with the updated features from the checked out layer. If it is not acceptable, they can click the Cancel button, which restores the layer to its original form and unlocks the formerly locked area. In either case, the checked out layer is automatically deleted from the remote database.

Which Data Distribution Mechanism Works Best?
There are advantages to both data transfer processes and the decision as to which to choose depends on several factors:

Synchronization may be a better solution if:

• The number of targeted field users is relatively large as data can be simultaneously distributed to many individual users
• There is likely to be more than one person working within a specific area
• The field workers are using XMap Professional
• The data layers in question are frequently updated
• The data manager wishes to control the editing of the layers through the deployment of XMap Forms
• The administrator wants to enable the field workers to initiate the transfer process when they are in a connected environment rather than manually assigning and collecting the appropriate layers from each user

Check-out/in is worth considering if:

• The number of users is relatively small and the transfer process can be initiated manually
• The data manager wishes to provide full editing control for all data types
• The field workers have access to either XMap GIS Editor or Enterprise
• There is a need to protect the data while one individual is working in an area to avoid potential conflicts
• The administrator wishes to see and verify the data edits before the field-collected information is merged into the original layer

What these components of XMap have in common is that they were both designed to streamline the flow of information within an organization and ultimately to make the task of sending and receiving data significantly more straightforward for GIS managers.

The delivery of maps in vector format offers several advantages over raster data products, such as aerial imagery or scanned paper maps:

• The data is much smaller so a wider geographic coverage area can be delivered per megabyte of storage
• The data is updatable so periodic edits and corrections are relatively straightforward
• The data display can be manipulated by the end user

XMap users have several customization options that can be utilized to create a base map that is tailored to the needs or requirements of the project at hand:

Map Features

The Map Features tab in the Option dialog (accessible from the toolbar) offers two levels of control depending on the degree of customization required.

• The main window offers a concise list of map feature types that can be checked on or off as needed. This list includes points of interest, minor roads, and map grids.
• By selecting the Use Custom Map Features option at the bottom of the window, the base map contents can be fine tuned to a greater degree. Individual types of lines, points, and polygons can be displayed or hidden using the appropriate check boxes. A common approach to map feature customization is to initially disable all objects in the base map by selecting the None button and then individually turning on the features that are needed.

Map Features settings are recorded in the current XMap project so it is possible to create template maps containing various combinations of features by creating and saving several projects.

Contour Display

In the topographic base map in XMap, contours are dynamically generated from the underlying digital elevation model. If required, the contours can be removed from the map using the Map Features settings as noted above. Alternatively, the interval or space between adjacent contours can be adjusted to accentuate the elevation in relatively flat terrain or to reduce the concentration of contour lines in mountainous areas. Note that the contour interval is automatically optimized at different zoom levels so it is usually not necessary to make manual adjustments.

If necessity dictates, the contour properties can be adjusted in the Map Data tab by expanding Reference Data, then expanding Topography and right-clicking on Contours. In the resulting window, the first setting allows the selection of Low Density, High Density, or Custom contour spacing as well as the selection of the zoom level at which contours first appear. If Custom is selected, the next window provides the opportunity to set the contour interval within specified zoom levels. It also offers the option to establish the major contours at each zoom level, which stipulates which contour lines are labeled on the map.

The next window in the Contour Properties dialog box offers the option to adjust the overall zoom level range for contours. The final window is used to select the map views in which the contours will be displayed.

Shaded Relief

The pattern of shaded relief or terrain shadow is employed by XMap to emphasize the topography and, as with contours, it is generated dynamically from the digital elevation model. The shaded relief pattern can be adjusted to imply an alternative light source position so the simulated shadow falls on a different side of each mountain or hill.

To make this adjustment, right-click Shaded Relief in the Map Data tab and click Properties. The first screen in the Shaded Relief Properties window has settings to change the sun bearing and inclination or angle above the horizon, as well as the brightness range for the shadow effect. As with the contour settings, the next screens provide the option to choose the zoom level range and map selection within which the shaded pattern will appear.

Map Colors

Under the Display section of XMap’s Options window, there are three Map Colors options. Topo Colors, the default setting displays all topographic features as well as land cover information; Street Colors mirrors the map view in DeLorme’s Street Atlas USA—with no contours, shaded relief, or land cover—for a simple street view; the High-Contrast Colors option renders the map with darkened features and is intended for in-vehicle use, especially when driving at night when the brightness of the screen can be distracting.

Magnification

Also contained within the Display Options window, the Magnification drop-down list can be used to alter the size of the features, text, and symbols on the map. The most common use is to increase the magnification so that objects appear larger and text is easier to read, especially on a small screen with a high screen resolution. Note that on the GPS tab in the Options dialog, a check box offers the option to automatically magnify the map when GPS tracking is enabled.

Layering

There are two ways to adjust the layering hierarchy on the map depending on whether the layer in question is raster or vector. By default, the layering sequence starts with base map vectors at the bottom followed by raster layers such as aerial imagery, and GIS and draw layers on top. Often it is necessary to display specific features from the base map on top of a raster or a GIS layer or to adjust the layering hierarchy of specific GIS layers.

To adjust raster layering, locate the layer in question in the Map Data tab and right-click to select Properties. If necessary, click Next to display the Data Positioning window and, using the drop-down list, select the feature class that you wish to display on top of the raster layer. Note that because of the hierarchical structure of the base map data, the chosen selection will also include those objects that appear above it in the list. For instance, if Roads is selected, Town Borders, Business POIs, etc, will also appear. If these additional features are not needed, they can be filtered using the Map Features settings noted above.

By default, this layering behavior will be applied to the selected data throughout its entire zoom level range; however, it is also possible to establish a different layering sequence for a specified zoom level range.

GIS layering is controlled from the Layering section of the GIS tab. As each new layer is imported or created, it is assigned a z-level value of 4500. By increasing or decreasing this value, the position of the selected layer can be moved up or down relative to other GIS layers or to features in the base map. The process of adjusting the layering can be performed by simply typing a new z-level value or by clicking and dragging a selected layer in the layering list and dropping it at the appropriate position in the hierarchy.

The inherent flexibility of XMap’s topographic base map means that it is possible to create a truly unique map view as a foundation for clearly representing and emphasizing user data layers.