Archive for June, 2009

Tab Tip – Building a Query in XMap

June 26, 2009
A version of this article was originally penned for the April 2007 edition of the DeLorme Professional Newsletter. When it was suggested that we include an updated revision for the June 2009 edition, it transpired that most of the original content still applies. So, with apologies to long-time subscribers, the following article is recycled.
The query function, which is included in both the Enterprise and Editor versions of XMap, offers both attribute and spatial querying. Queries are used to quickly identify specific records in your data and to uncover the spatial relationship between objects within different data layers. Note that queries that have been built using Enterprise or Editor are transferred with the corresponding openspace layer or through the synchronization process to users of XMap Professional. However XMap Professional cannot be used to create a query.
Read More…
A query is built by following a few simple steps:
1. After clicking the Query button on the left side of the GIS tab, select the layer to be queried from the Layer drop-down list.
2. Choose an attribute to query by clicking the cell immediately below the Attribute column heading. A drop-down list shows all of the attribute fields for that layer.
Note that the first item on the list is GEOMETRY. Select this option if you are creating a spatial query. This process will be discussed in greater detail below.
3. After selecting an attribute field, select the query Operator from the drop-down list in the adjacent cell. Depending on the data type, query operators may include “CONTAINS”, “IS EMPTY”, <, and =, among others. For instance, a query to find property owners by name within a parcel layer will be set up as follows:
Layer: Tax Parcels, Attribute: Owner, Operator: EQUALS
4. In the next cell, type or select the search criteria, which will reflect the name or value being sought. A drop-down list will offer a sample of the values that are present within the selected attribute field.
Optionally, select the User Input check box and leave the Criteria field blank, which allows unique query criteria to be entered each time the query is run. This function is particularly useful when sharing a layer with a user of XMap Professional either through an openspace file transfer or using the synchronization process as it allows them to customize the search parameters.
5. Use the Logical Operator option to build a more complex query by establishing multiple search criteria either on the same field or on different fields within the layer. For instance, by choosing the AND option, an additional line can be added that further filters the query results. The parcel query might then read like this:
Attribute: Owner, Operator: EQUALS, Criteria: Smith, Logical Operator: AND
Attribute: Value, Operator: > Criteria: 100000
In this case the query would return a list of all of the properties owned by someone named Smith that have a value of grater than $100,000. Additional lines can be added to a query as needed.
The process of building a spatial or geographic query is similar to building an attribute query. Selecting GEOMETRY from the Attribute list, as noted above, offers a unique list of query operators including, “IS CONTAINED BY”, “INTERSECTS”, and “WITHIN A DISTANCE OF”, as well as their inverses. This allows a subset of objects within a layer to be generated based on their spatial relationship to objects in another layer or based on a determined distance from a selected location or from the map center.
A powerful search option is to create a query that is a combination of both spatial and attribute query criteria. Using the parcel example again, the query could be built as follows:
Attribute: Owner, Operator: EQUALS, Criteria: Smith, Logical Operator: AND
Attribute: Value, Operator: > Criteria: 100000, Logical Operator: AND
Attribute: GEOMETRY, Operator: IS CONTAINED BY, Criteria: City School District
In this example the query results would be further limited to those that fall with the City School District polygon as delineated in a second openspace layer.
It is common for the spatial query function to be used in conjunction with XMap’s buffer tool. A buffer is polygon of a user-specified radius created around an object or group of objects within a layer. The Buffer dialog box, which is accessed by clicking the Tools button in the Workspace, offers the option to create buffer areas around all objects in a layer or just those that have been selected or queried.
As an example of the combined use of the buffer and spatial query tools, a pipeline manager can create a map and generate a list of properties that fall within a mile of his pipeline. To accomplish this he would first create his one-mile buffer polygon then build a spatial query as noted above using IS CONTAINED BY as the operator and the newly created buffer layer as the criteria.
The query function is one of the fundamental data management tools within any GIS. In XMap, the combination of buffering, attribute and spatial querying provides an efficient and effective way to filter or highlight critical objects within a layer.
A version of this article was originally penned for the April 2007 edition of the DeLorme Professional Newsletter. When it was suggested that we include an updated revision for the June 2009 edition, it transpired that most of the original content still applies. So, with apologies to long-time subscribers, the following article is recycled.
The query function, which is included in both the Enterprise and Editor versions of XMap, offers both attribute and spatial querying. Queries are used to quickly identify specific records in your data and to uncover the spatial relationship between objects within different data layers. Note that queries that have been built using Enterprise or Editor are transferred with the corresponding openspace layer or through the synchronization process to users of XMap Professional. However XMap Professional cannot be used to create a query.

Query1

A query is built by following a few simple steps:
  1. After clicking the Query button on the left side of the GIS tab, select the layer to be queried from the Layer drop-down list.
  2. Choose an attribute to query by clicking the cell immediately below the Attribute column heading. A drop-down list shows all of the attribute fields for that layer.
    Note that the first item on the list is GEOMETRY. Select this option if you are creating a spatial query. This process will be discussed in greater detail below.
  3. After selecting an attribute field, select the query Operator from the drop-down list in the adjacent cell. Depending on the data type, query operators may include “CONTAINS”, “IS EMPTY”, <, and =, among others. For instance, a query to find property owners by name within a parcel layer will be set up as follows:

    Layer: Tax Parcels, Attribute: Owner, Operator: EQUALS

  4. In the next cell, type or select the search criteria, which will reflect the name or value being sought. A drop-down list will offer a sample of the values that are present within the selected attribute field.
    Optionally, select the User Input check box and leave the Criteria field blank, which allows unique query criteria to be entered each time the query is run. This function is particularly useful when sharing a layer with a user of XMap Professional either through an openspace file transfer or using the synchronization process as it allows them to customize the search parameters.
  5. Use the Logical Operator option to build a more complex query by establishing multiple search criteria either on the same field or on different fields within the layer. For instance, by choosing the AND option, an additional line can be added that further filters the query results. The parcel query might then read like this:

    Attribute: Owner, Operator: EQUALS, Criteria: Smith, Logical Operator: AND
    Attribute: Value, Operator: > Criteria: 100000

    In this case the query would return a list of all of the properties owned by someone named Smith that have a value of greater than $100,000. Additional lines can be added to a query as needed.

Query2The process of building a spatial or geographic query is similar to building an attribute query. Selecting GEOMETRY from the Attribute list, as noted above, offers a unique list of query operators including, “IS CONTAINED BY”, “INTERSECTS”, and “WITHIN A DISTANCE OF”, as well as their inverses. This allows a subset of objects within a layer to be generated based on their spatial relationship to objects in another layer or based on a determined distance from a selected location or from the map center.
A powerful search option is to create a query that is a combination of both spatial and attribute query criteria. Using the parcel example again, the query could be built as follows:
Attribute: Owner, Operator: EQUALS, Criteria: Smith, Logical Operator: AND
Attribute: Value, Operator: > Criteria: 100000, Logical Operator: AND
Attribute: GEOMETRY, Operator: IS CONTAINED BY, Criteria: City School District
In this example the query results would be further limited to those that fall with the City School District polygon as delineated in a second openspace layer.
It is common for the spatial query function to be used in conjunction with XMap’s buffer tool. A buffer is polygon of a user-specified radius created around an object or group of objects within a layer. The Buffer dialog box, which is accessed by clicking the Tools button in the Workspace, offers the option to create buffer areas around all objects in a layer or just those that have been selected or queried.
As an example of the combined use of the buffer and spatial query tools, a pipeline manager can create a map and generate a list of properties that fall within a mile of his pipeline. To accomplish this he would first create his one-mile buffer polygon then build a spatial query as noted above using IS CONTAINED BY as the operator and the newly created buffer layer as the criteria.
The query function is one of the fundamental data management tools within any GIS. In XMap, the combination of buffering, attribute and spatial querying provides an efficient and effective way to filter or highlight critical objects within a layer.

XMap Q&A – My company has a well established GIS; why would we need XMap?

June 26, 2009

 

One of the recurring themes that you will often read in DeLorme’s XMap informational literature is that XMap is equally well suited as a standalone GIS application or as an extension to your existing GIS infrastructure. As XMap continues to evolve, more and more emphasis is being placed on improving the interoperability with third-party GIS software and databases and on simplifying the exchange of data between the different platforms. Seen in this light, XMap functions as a bridge between your current GIS setup and those who need access to the data on an ongoing basis, namely your field staff or mobile workforce.
Before considering this question in the context of the current versions of XMap, it is worth taking a look back at DeLorme’s first venture into the world of GIS in the early versions of XMap.
DeLorme’s strength in the field of mapping technology has always been founded on the inherent mobility of its software. Companies with large field-based workforces were quick to recognize this and were equally quick to ask for additional functionality to support their field operations. One of the most frequent requests was for a tool to integrate corporate GIS datasets into this mobile mapping platform. DeLorme acquiesced with the release of XMap version 3, which offered a simple function for importing shapefiles as draw layers. The intention of this feature was simply to provide an easy-to-use and affordable means to display GIS data in the field. For this reason, the early versions of XMap were particularly appealing to GIS administrators.
Read More…
Since those early days, XMap’s development has followed two paths. A vast array of functionality has been added to allow XMap to serve as a self-contained spatial data management tool, typically for relatively small scale operations. Concurrently the XMap development team has spent a considerable amount of time designing the efficient data distribution capability that has been adopted by numerous large-scale GIS departments.
XMap is not intended as a replacement for your current GIS software, instead it adds value to your GIS investment by extending its reach. In the office, the Enterprise version of XMap is used to import and stage your data in preparation for distribution. It can even pull layers directly from your ArcSDE databases. XMap’s integrated Database Manager application is then used to set up the subscription process by which selected layers will be assigned to an individual or group as appropriate. 
In the field, the Professional version of XMap provides easy, read-only access to these GIS layers with a simple click of a button. This synchronization process is initiated by the field user and it ensures that they have the latest version of each layer to which they are subscribed.
Perhaps the most appealing function of the XMap suite for GIS administrators is the redlining tool that is included in XMap Professional. As a component of the synchronization process, this easy-use-annotation feature allows field workers to communicate with their GIS administrator using a variety of markup tools. These redline layers are automatically delivered to the central database with each synchronization, allowing the data administrator to correct or update the master layers as necessary.
Most GIS managers will agree that a fully functional GIS is one in which all vested parties have access to the necessary data. XMap can play a key role in this process by simplifying the distribution of data and by providing an easy-to-use and affordable GIS viewer for field operatives.
Telecom_1One of the recurring themes that you will often read in DeLorme’s XMap informational literature is that XMap is equally well suited as a standalone GIS application or as an extension to your existing GIS infrastructure. As XMap continues to evolve, more and more emphasis is being placed on improving the interoperability with third-party GIS software and databases and on simplifying the exchange of data between the different platforms. Seen in this light, XMap functions as a bridge between your current GIS setup and those who need access to the data on an ongoing basis, namely your field staff or mobile workforce.
 
Before considering this question in the context of the current versions of XMap, it is worth taking a look back at DeLorme’s first venture into the world of GIS in the early versions of XMap.
 
DeLorme’s strength in the field of mapping technology has always been founded on the inherent mobility of its software. Companies with large field-based workforces were quick to recognize this and were equally quick to ask for additional functionality to support their field operations. One of the most frequent requests was for a tool to integrate corporate GIS datasets into this mobile mapping platform. DeLorme acquiesced with the release of XMap version 3, which offered a simple function for importing shapefiles as draw layers. The intention of this feature was simply to provide an easy-to-use and affordable means to display GIS data in the field. For this reason, the early versions of XMap were particularly appealing to GIS administrators.
 
Since those early days, XMap’s development has followed two paths. A vast array of functionality has been added to allow XMap to serve as a self-contained spatial data management tool, typically for relatively small scale operations. Concurrently the XMap development team has spent a considerable amount of time designing the efficient data distribution capability that has been adopted by numerous large-scale GIS departments.
 
XMap is not intended as a replacement for your current GIS software, instead it adds value to your GIS investment by extending its reach. In the office, the Enterprise version of XMap is used to import and stage your data in preparation for distribution. It can even pull layers directly from your ArcSDE databases. XMap’s integrated Database Manager application is then used to set up the subscription process by which selected layers will be assigned to an individual or group as appropriate. 
 
In the field, the Professional version of XMap provides easy, read-only access to these GIS layers with a simple click of a button. This synchronization process is initiated by the field user and it ensures that they have the latest version of each layer to which they are subscribed.
 
RedlinePerhaps the most appealing function of the XMap suite for GIS administrators is the redlining tool that is included in XMap Professional. As a component of the synchronization process, this easy-use-annotation feature allows field workers to communicate with their GIS administrator using a variety of markup tools. These redline layers are automatically delivered to the central database with each synchronization, allowing the data administrator to correct or update the master layers as necessary.
 
Most GIS managers will agree that a fully functional GIS is one in which all vested parties have access to the necessary data. XMap can play a key role in this process by simplifying the distribution of data and by providing an easy-to-use and affordable GIS viewer for field operatives.

Reseller Spotlight

June 26, 2009

One of the daily challenges faced by DeLorme sales, marketing, and customer service staff is addressing the needs of all the industries that we serve. Because of its flexible nature, XMap has been adopted by a wide array of businesses and organizations, all of which bring their own requirements to the table. While DeLorme staff members can justifiably claim to have a high level of proficiency when it comes to understanding the workings of XMap, the application of the technology for a specific market can be considerably more demanding.

Thankfully, DeLorme has developed a network of Value-Added Resellers (VARs) who are much more familiar with the industries and territories that they serve and can interpret and apply the capabilities of XMap accordingly.

Over the coming months, the DeLorme Professional Newsletter will include a series of articles on some of our key VARs that will provide an insight into their business focus and sphere of expertise. If you are interested in the application of XMap within their particular industry, you are encouraged to contact them directly. If would like more information about becoming a Value-Added Reseller of XMap, please contact the XMap team at 1-800-293-2389 or email prosales@delorme.com.

 DDSI_logoOur first reseller in the spotlight is Tulsa, Oklahoma-based Downtown Design Services, Inc. (DDSI). DDSI has been serving the oil and gas, electric transmission and distribution, fiber optic, and telecommunications industries, as well as municipalities and local governments since 1999. DDSI’s customer base is dispersed throughout the U.S. but especially in Oklahoma, Texas, Colorado, Kansas, New Mexico, and Wyoming. Offering drafting and design services, GIS data management, conversion and collection, DDSI provides their clients with superior service in a timely, cost-effective manner, meeting their clients’ goals and objectives.

“Having handled the pipeline corridor mapping for multiple gas gatherers across the United States in both CAD and GIS environments for many years, we found the DeLorme XMap GIS suite to be an ideal tool for companies wanting to implement or supplement their GIS,” said Tim Harrison, company president. “With one particular client, we had used AutoCAD to maintain their mapping system for many years. By introducing and implementing XMap GIS, as well as the Earthmate PN-Series GPS receiver, we have enabled them to push data to over 150 users across the region, thus allowing them to update their system on a daily basis.

DDSI specializes in converting existing CAD, DeLorme Street Atlas USA, or hard copy data to GIS. The company also provides client-specific implementation, training, and support of XMap.

For more information on DDSI’s GIS data conversion, management, or collection services or any other drafting and design needs please visit their Website: www.downtown-design.com

Earthmate PN-20 Helps Bellingham Mountain Rescue Locate Lost Hikers

June 26, 2009

The following is a first-hand account of a successful rescue operation in the Glacier Peak Wilderness of the Cascade Range in Washington State. Justin Mitchell, the Operations Leader for Bellingham Mountain Rescue, describes how the Earthmate PN-20 GPS receiver proved its mettle in extreme conditions.

S&R_WashOn August 27th, 2008, just before midnight, I received a call from Don, an operations leader from the Skagit Mountain Rescue team. They needed some help from Bellingham Mountain Rescue for two climbers reportedly stuck on a ledge somewhere near Spire Point. The climbers were near the end of completing the “Ptarmigan Traverse,” a five-day thru hike in the North Cascades and were stuck on a ledge in bad weather with 100 ft visibility, not knowing exactly where they were.  I called and woke up one of our SAR deputies from the Whatcom County Sheriff’s Office (a pleasure to wake them up instead of what is typically the reverse) to let them know we’d been requested. I then got to work putting a team together and downloading maps to my PN-20. Spire Point is located quite a way into the North Cascades, and with the normal road/trail system being washed out, I knew there was going to be quite a bit of bushwhacking and/or route-finding. It also meant our chances of getting back in there and finding them quickly without helicopter support was slim.

We met at “base operations” at the Concrete airport the next morning to discuss our options. Volunteers showed up from Skagit, Tacoma, and Bellingham mountain rescue teams. Despite the long distance involved, a team would go in by foot since the weather did not look favorable for a helicopter. The Bellingham team would continue to help at base ops but be on hot standby in the event a helicopter option became available. We were able to communicate with the stranded climbers a couple of times via cell phone and the situation was not good—they were extremely cold, wet, and showing signs of hypothermia. The cell phone, however, did provide us with a lat/long to start off with via its E911 feature. The coordinates did not initially make sense, although I was able to enter them into my PN-20 using a variety of different formats, until finally noting that they had come in via the degrees decimal format. Bingo—the coordinates put them near the summit of Spire Point (degrees minutes format N48° 19.042′, W121° 4.247′). So from there, we were able to come up with some possible scenarios and hone in our initial search area.

Luck was on our side. Although the mountains were still socked in, the weather was clearing somewhat and a Navy helicopter arrived to possibly help. We collectively gathered around our USGS maps and came up with a plan—we would follow the valleys in towards Spire Point, keeping well under the cloud ceiling, and try one of three different “insertion points” on alternate sides of the mountain for a drop off. And from there, we’d climb up near the top of Spire Point as quickly as we could to search for the climbers. This was clearly our best option given the time it would take for the first team to get in there on foot. Moreover, another weather system was on its way in and promised to bring worse weather than this one. As we loaded onto the helicopter, I entered the three insertion points as waypoints into my PN-20, wondering if we’d even get to use them.

Itswoot_LakeThe flight in was interesting. We followed roads and valleys into the area, keeping a close eye on the weather ceiling. And one by one our hopeful insertion points were shut out by the bad weather. All the while, though, I sat next to the side door of the helicopter with my PN-20, keeping track of where we were relative to our insertion points. As we exhausted our last option, though, I asked the pilot to head back west and try another option. I had seen a small lake on the topo map of my PN-20 that just might be accessible via a small side valley. We rounded the corner into the valley and I asked the pilot if he’d be comfortable poking his nose just over the trees at the head of the valley. We were just below the ceiling but he agreed since it was basically our only hope. As we skimmed over the trees, Itswoot Lake appeared with a perfect little landing zone on the south end of the lake (N48° 17.870′, W121° 5.319′).

The rotor wash on the Seahawk helicopter (basically same as a Blackhawk but in Navy terms) was tremendous as they took off and accelerated the wetness of the rain. We quickly donned foul weather gear, oriented ourselves with a map and compass, and headed up the mountain. Visibility was minimal, and the higher we got up Itswoot Ridge, the more rainy, windy, and cold it got. None of us had ever been here before either so our maps, compass, and altimeters were crucial to route-finding. And although we’ve trained ourselves not to rely on a GPS, the PN-20 and its integrated maps were outstanding for confirming our location and route. We got up to just under the summit of Spire Point and set up camp on the Dana Glacier in the dark. Our voices were hoarse from yelling and whistling, and our bodies were tired and hungry from battling the elements. We felt pretty good about the progress we’d made but also knew first hand the weather these climbers had gone through. We went to sleep with hopes of finding survivors in the morning.

Morning came quickly and the winds had calmed down a bit, but visibility was still quite challenging. As we loaded up our tents, we resumed our yells and whistles, and to our surprise heard a very faint yell back! Tracking the direction of the yells was difficult because of various echoes involved, but we made our way north along the Dana Glacier and eventually found the lost climbers cold, wet, but otherwise alive, and very happy to see us (N48° 19.384′, W121° 4.115′). As we fed them some hot food, they explained how they’d huddled in their one remaining sleeping bag all night and were going to head back down the north side of the mountain if help had not arrived by that afternoon.

We gathered all their stuff and headed back down the way we’d come up, meeting the other rescue team along the way. A helicopter soon arrived to take us and our rescued subjects back to warmth, safety, and their loved ones.

I shudder to think of the consequences if we hadn’t have found them when we did, especially given the colder and more intense weather system that was hitting the area the very next day. The expert flying provided by our local Navy base was certainly key to us succeeding with this mission, but equally as important was knowing exactly where we were at all times via the maps on my Delorme PN-20. I truly believe it contributed to two saved lives, and I look forward to even better capabilities on the PN-40.

For more information on Bellingham Mountain Rescue, visit www.wcsar.org/bmrc/.

To read more about the Earthmate PN-Series GPS receivers, click here.

DeLorme Releases Updated Topographic Map Data for XMap

June 26, 2009
DeLorme recently announced the availability of the 2009 edition of its XMap USA Topographic Data [link: http://shop.delorme.com/OA_HTML/DELibeCCtpSctDspRte.jsp?section=10063]. This unique dataset offers users of XMap, DeLorme’s three-tiered GIS suite, a highly-detailed and customizable base map with topographic coverage for the U.S. and road and street data for Canada and Mexico, all on a single DVD.
This latest release of the XMap USA Topographic Data includes a significant number of updates and other improvements including:
Over 300,000 new roads and streets in the U.S.
Detailed road and street coverage for Canada and major roads in Mexico
200,000 new places-of-interest
Over 4,000 new trails
Enhanced map colors for superior cartographic display
Improved horizontal accuracy
Because XMap USA Topographic Data is in vector format, map features can be turned on or off as needed, providing an optimized backdrop for managing and displaying your GIS layers or other map data.  Unlike raster-based topographic maps, XMap USA Topographic Data is scalable so the optimal concentration of map features is displayed at every zoom level.
As an integrated component of the XMap suite, the XMap USA Topographic Data adds value to the software by enabling key features and functions including:
3-D terrain modeling
Elevation profiling
Customizable contour and shaded relief display
Road and trail routing, as well as in-vehicle navigation
Address geocoding
With over 30 years experience developing and managing spatial datasets for use in a broad range of mapping products, DeLorme has earned a well-deserved reputation for the quality of its map data. The XMap USA Topographic Data 2009 offers XMap users the foremost North American map dataset available today.
DeLorme map data is also available for use in third-party GIS applications in a variety of formats, including ESRI shapefile or geodatabase. For more information, call 1-800-293-2389 or contact ProSales@delorme.com.

DeLorme recently announced the availability of the 2009 edition of its XMap USA Topographic Data. This unique dataset offers users of XMap, DeLorme’s three-tiered GIS suite, a highly-detailed and customizable base map with topographic coverage for the U.S. and road and street data for Canada and Mexico, all on a single DVD.

Topo_09This latest release of the XMap USA Topographic Data includes a significant number of updates and other improvements including:

  • Over 300,000 new roads and streets in the U.S.
  • Detailed road and street coverage for Canada and major roads in Mexico
  • 200,000 new places-of-interest
  • Over 4,000 new trails
  • Enhanced map colors for superior cartographic display
  • Improved horizontal accuracy

Because XMap USA Topographic Data is in vector format, map features can be turned on or off as needed, providing an optimized backdrop for managing and displaying your GIS layers or other map data.  Unlike raster-based topographic maps, XMap USA Topographic Data is scalable so the optimal concentration of map features is displayed at every zoom level.

As an integrated component of the XMap suite, the XMap USA Topographic Data adds value to the software by enabling key features and functions including:

  • 3-D terrain modeling
  • Elevation profiling
  • Customizable contour and shaded relief display
  • Road and trail routing, as well as in-vehicle navigation
  • Address geocoding

With over 30 years experience developing and managing spatial datasets for use in a broad range of mapping products, DeLorme has earned a well-deserved reputation for the quality of its map data. The XMap USA Topographic Data 2009 offers XMap users the foremost North American map dataset available today.

DeLorme map data is also available for use in third-party GIS applications in a variety of formats, including ESRI shapefile or geodatabase. For more information, call 1-800-293-2389 or contact ProSales@delorme.com.


Follow

Get every new post delivered to your Inbox.