Wednesday, November 13, 2013

The State of Mobile GIS Software

Over the past six months or so I've been doing a lot of casual testing of the various mobile GIS platforms available on the market today.  Right now is an ideal time to discuss the offerings because just in the past week we've had an update to a key application in this arena (Collector for ArcGIS), we are on the verge of having an interesting new hardware player enter the market (Garmin's soon to be released Monterra handheld GPS) and several vendors are dropping serious hints about where they see their products headed in 2014.

I was ramping up to do a lengthy blog post on this when I dropped by Alex Mahrou's always interesting RockyMountainGeo GIS blog and was surprised to see he had already done all my work for me.  Back in October Alex did a great overview of the current offerings in a posting titled Enterprise Mobile GIS Software Functionality.  All I can do is add minor updates to some of his information and add a few of my own observations.

I like the switchboard analogy!


The single biggest update is the newest version of Collector for ArcGIS (version 10.2) that was released last week for the iOS and Android platforms.  This version addresses one of the two biggest complaints about earlier versions of Collector - polyline and polygon data collection.  It also offers an improved user interface and well thought out workflows.  While the Android version still has some rough edges, the iOS version is a polished, smoothly functioning app that reflects ESRI's mature experience in developing for Apple's mobile operating system.  It is a very good app.

Where ESRI seems to be unnecessarily holding back is off-line data collection and editing, and data synchronization.  As Alex notes, ESRI informally promised that this feature would 'absolutely, positively' be incorporated into Collector before the end of 2013.  It now looks like we'll have to wait until sometime in early 2014, when ESRI plans for a significant overall upgrade to Collector, perhaps better positioning it within their enterprise software offerings.  In my opinion ESRI missed the ball on this one.  Incorporating off-line data storage and editing in the iOS and Android operating systems isn't hard to do; Trimble had it available almost six months ago in their initial release of TerraFlex.  I understand there are other issues at play here - background map data caching and the incorporation of operational layers (both something Trimble's offering lacks), but ESRI still could have incorporated basic off-line functionality in this new release and just built on it for the upcoming major release.

Trimble's TerraFlex is an app I tested back in June and was initially very impressed.  Where most of ESRI's mobile offerings (Collector, ArcGIS App, ArcGIS for Windows Mobile) require some expensive back-end infrastructure - ArcGIS Online, Portal or ArcGIS for Server - TerraFlex offers a far simpler mobile solution paradigm.  Everything is cloud based and single fee.  You pay your money and you get everything TerraFlex has to offer, and all for a relatively paltry price as compared to ESRI's mobile solutions in the same marketplace.  Of course, this easier to use solution comes at a cost (pun intended) - what the initial release of TerraFlex didn't offer was pretty extensive; no background map caching, no data editing either on the device or in the desktop interface, no operational layers, and some very limited data export options.  On the other hand, what TerraFlex does offer is pretty impressive given the price: off line data storage and sync, mature and stable apps not just on the iOS and Android platforms, but Trimble also had an app available for the Windows Embedded Handheld OS right out of the gate.  Trimble wasn't about to leave out the thousands of Trimble customers running their Juno handhelds who are still stuck with a dying Windows OS.  Kudos to Trimble on this.

Trimble indicates many of these shortcomings will be addressed in 2014, and Trimble seems poised to leverage what they do best - allow TerraFlex to incorporate high precision GNSS positions (including RTK-based solutions) into the data collection stream.  This could turn TerraFlex from a mere mapping grade data collector into a serious high precision data collection tool.

In his blog post Alex discusses Fulcrum.  To be honest, this is an application I've known about but have not had a chance to test.  Looks like I'll have to take it for a spin sometime soon.

So as 2013 draws to a close where are we at with mobile GIS solutions?  The best analogy I can think of is that of a ballplayer with a lot of potential who's just been called up to the majors.  His batting stats are getting better with each game, but he still has problems connecting with the ball.  The potential is there, he just needs more time. So it is with mobile GIS apps.  Most are still somewhat of a 'swing and a miss', but they are getting close to smacking the ball out of the park.  Whether it's off-line data collection with ESRI's offerings or TerraFlex's incorporation of cached maps, in-app editing or incorporation of high precision position feeds, 2014 is starting to look like the field will really mature and we'll get closer to the full promise of mobile GIS.

It'll be an interesting year!

Brian



  

Saturday, November 2, 2013

William J. Hudson's Pocket Transit History Site

Several times in this blog I've referenced an excellent pocket transit history site established by a gentleman by the name of William J. Hudson.  His site was the resource for historical information on the development of the pocket transit, its many variations and changes down through the years.  I considered it the best resource on pocket transits available anywhere on the web.

Unfortunately it looks like Mr. Hudson's site went off-line well over a year ago.  I first noticed it about six months ago while doing some research on a pocket transit I had just added to my collection.  Over the last few months I've been contacted several times either directly or through this blog about Mr. Hudson's site, asking if I knew when it might be available again.  Since I don't know Mr. Hudson and I've never communicated with him I had no way of contacting him to see when or even if he intended to reestablish his website.  It seemed a great resource for those interested in pocket transits was gone from the web forever.

Well, things don't really disappear from the web.  They just get archived.  I'm happy to report that I've stumbled upon an archive of the main page of Mr. Hudson's site hidden away in a dark corner of the internet.  Unfortunately none of the linked pages such as his serial number breakdown page were archived, so that resource appears lost.  But the main page is still chock full of useful information about the pocket transit's history, development and features.

I've linked to the internet archive for this page from the image below.  When you open the page you'll have the option to download the page and graphics as a zip file.

Click here to access the site archive

I'm glad to have access again to at least a portion of this great resource.  Mr. Hudson, if you read this, can we have your site back please?  Hundreds a couple of diehard pocket transit collectors really miss the information your site provided!

Brian

Thursday, October 31, 2013

Lies, Damned Lies, and Cartography

If you are a cartographer or geographer this is just too funny.


We do occasionally get wrapped up in discussions like this.  Seems lots of politicians and leaders want their town, precinct, district, state, country or continent to have pride of place.  Along the way things will get distorted.  That's the challenge of trying to depict curved surfaces (the earth) on flat paper, or on a computer screen.

Yes, there really is such a thing as a Peters Projection map, and here's a great discussion about why those with political agendas shouldn't be allowed to design things like map projections.

Want to know what your piece of ground really looks like in relation to the rest of the world?  Get a good old fashioned globe.

Sunday, October 20, 2013

A Tale of Two Trimbles

Earlier this year Trimble released its newest generation of the Juno data collectors to the market.  Unlike the previous generations of these devices (the original Juno S and the later Juno 3 series), the new Junos come in several different flavors depending on which business line within Trimble you purchase yours from.  Those purchased through Trimble Mapping & GIS distributors are labeled the Juno 5.  Those purchased through Trimble's Mobile Computing Solutions distributors are known as the T41.  They are all based on the same hardware platform.

To confuse things even more, you can get either device running different operating systems, either Windows Embedded Handheld 6.5 (aka, Windows Mobile) or Android 4.1.

Back in May my organization got its hands on a loaner 5D unit and I was initially impressed with the hardware but thought the Windows OS was holding the whole package back.  At the time I viewed it as an outstanding piece of hardware saddled to an operating system that badly limits the unit's performance and potential.  I was eager to get my hands on the T41, hoping that the current version of Android would unlock a lot of the performance potential of this device.  About a month ago my organization purchased one 5D and one T41 to test.  We were looking for an upgrade to our Juno 3D handhelds (very good devices, by the way) and were intrigued by the possibilities of the Android-based Juno T41; something we could run the ESRI ArcGIS and Collector apps on along with Trimble's new TerraFlex app.

The 5D (left) and the T41 (right)


When we received the units and began to test them I made a number of quick observations.  As I initially wrote back in May, the hardware is first rate. From the smartphone form factor to processor speed to screen resolution and clarity under a wide variety of conditions to the GPS module performance.  This is a seriously good piece of hardware.  Back in May I complained that the 5D lacked the ability to receive signals from the Russian GLONASS system.  I still feel it's a shortcoming of the unit, but in actual use it may not matter.  The overall performance of the GPS receiver in these new Trimbles is outstanding, with fast acquisition and the ability to hold signal lock under some very tough conditions like under full tree canopy cover.  The GPS performance is so good I'm not (too) bothered by the lack of GLONASS capability.

One feature we did not test, and probably never will, is the 5D and T41 performance as an actual cell phone. While a cell phone data plan would greatly enhance the usefulness of these devices our organization is not willing to pay the cost to get these units activated as cell phones.

Where the 5D and T41 stumble are the operating systems.  I've already touched on my issues with the Windows OS in my earlier posting, but let me expand a bit here.  I understand why developers like Trimble stick with Windows Embedded Handheld.  Trimble has over a decade of experience developing for the Windows Mobile environment.  Most of their field data collector and survey system software like TerraSync was developed specifically for the Windows Mobile environment.  I get it. Windows Embedded Handheld (WEHH) is stable and well understood and has proven itself in enterprise environments.  So has Windows XP, and like XP WEHH isn't getting any better with age.

It must be a terrible time to be an enterprise mobile software developer working in the Windows environment.  Microsoft is starting to release Windows 8 for mobile devices similar to the Juno, but by necessity these devices must connect with a compatible desktop computer for data transfer and application updates. Windows 8 on the mobile device isn't backwards compatible with earlier versions of Windows on the desktop, yet corporate America has yet to embrace Windows 8 and will likely be sticking with Windows 7 for several more years.  What's a developer to do? In Trimble's case they stick with what they know and what their customers seem to be demanding - don't give me anything I can't sync with Windows 7.  The problem with WEHH on the Juno 5D is that the software can't seem to take full advantage of what the hardware offers.  It's like putting square wheels on a Ferrari.  This comes to light when working with the 5D's camera.  The camera is a very good 8 megapixel unit with dual flash.  It takes great pictures.  Too bad the WEHH camera control software sucks. It's slow, difficult to configure and the controls are not intuitive.  It's like working with an early Windows CE-based smartphone, which is essentially what you have with the 5D running WEHH.  The issue of hardware 'throttling' really comes to light when you compare this 5D camera experience with the camera on the T41 running on Android 4.1. The camera experience on tht T41 is entirely different and far more satisfying because Android does a much better job of interfacing with the camera.  It's like you are working with an entirely different camera hardware module but it's really an OS performance issue.

Before moving away from the discussion of WEHH I do have to add that the performance of enterprise apps like TerraSync and ArcPad is very good on the 5D.  Everything works as advertised, and the additional processing power of the 5D along with the larger screen size and improved resolution (over the Juno 3-series devices) makes for a great experience in the field.  The new Trimble SatViewer application is also a great improvement over the old GPS Controller module found on other Trimble WEHH devices.

Now on to the T41.  While the performance of the 5D was something of an expected disappointment, the performance of the T41, and Trimble's vision of how the T41 fits into their overall product line, comes as an unanticipated and surprising disappointment.

I'll leave aside any discussion of the T41 hardware - everything good I've discussed about the 5D hardware applies to the T41.  Bottom line - the hardware is great.

At first glance Trimble's choice of operating system is also great.  The unit comes pre-loaded with Android 4.1.  I'm testing Android 4.2 on a Google Nexus 7 tablet and I'm about to admit that this version of Android is good enough to pull me away from my beloved iOS devices.  Android is not an 'enterprise' OS and can't run applications like TerraSync or ArcPad, but there are a number of very good lightweight apps like ESRI's ArcGIS and Collector apps and Trimble's own TerraFlex app that uses a cloud data storage paradigm.

The problem is that the T41 comes with Trimble's in-house version of Android 4.1.  It was developed using the open source version of Android and has not been certified under the Android Compatibility Program.  This means that the T41 can't get access to the Google Play Store for installation of any one of the thousands of Android apps available through that environment.  This includes ESRI's ArcGIS and Collector apps and even Trimble's own TerraFlex app.  Not even Google's own Google Maps, Google Earth or the GMail app can be installed on this device!  This is a serious oversight.  I know plenty of surveyors and GIS professionals who depend on Google Maps and Google Earth on smartphones to support things like work crew routing, initial survey reconnaissance, survey control recovery and other tasks, and use programs like Google Drive to access project documentation in the field.  There's also no reason you shouldn't be able to use GIS apps like ESRI's ArcGIS and Collector apps on this device.

Trimble's decision to not get this operating system certified is baffling.


No Android Compatibility
certification means
 no Google Maps,
no Google Earth,
no native GMail support,
no Google Drive support,
no ESRI or Trimble app support
and the list goes on...

Worse yet, Trimble makes regular mention of the Trimble App Store in their product documentation and even includes the link to this app store on the T41 when they ship the unit.  The problem is, other than two crippled Trimble apps - the free versions of MyTopoMapViewer and Terrain Navigator Pro - there's nothing else in this app store. You can download apps to this device from the Amazon app store, but most of the apps available there are either older versions of what's available on Google's app store or are formatted specifically for Amazon's Kindle devices.


Trimble App Store icon


What's in the Trimble App Store?
Not much

I honestly thought I was missing something here.  Surely Trimble has something better for the T41 that I just couldn't get to.  Perhaps a real app store that I just needed the right permissions to access or a software upgrade that would allow me to link to the Google Play Store.  My local distributor put me in touch with Trimble's Mobile Computing Solutions (MCS) tech support and I quickly found out that no, what I got is all there is.

Apparently Trimble views the T41 as an 'enterprise only' unit.  This means enterprises have to develop their own specific apps for it using the Trimble Android SDK.  This is an OK approach, but there is still no reason to not have the OS version certified by Google.  It's just stunning to think that Trimble would ship an Android-based data collector that can't access Google Maps, Google Earth or even run Trimble's own Android-based data collection app!

I have heard rumors that Trimble is re-thinking this approach to the T41 and may be working to get its version of Android certified by Google.  If and when this will happen I don't know - Trimble MCS hasn't been very forthcoming on the topic.

So where does this leave us when considering the 5D and the T41?  Taking into account the unit cost (about $1,800 each) and the operating system issues shared by both of these devices I have to say that they are not worth the investment, particularly when you consider that Trimble still offers a very capable handheld unit - the Juno 3D - at about half the cost.

If Trimble releases a version of Android that allows access to the Google Play Store I'll come back and do an updated review, but for now I simply can't recommend either of these devices.

Brian



Monday, October 14, 2013

Well Darn

What's an old topographer to do when he needs a few PDFs of historic topo sheets?


If this foolishness continues I may have to expand the Map Room to start stocking (more) paper maps.

Thursday, September 19, 2013

It's New! It's Revolutionary! It's...

Aerial photo scanning!




Damn, what's next?  Televisions that get programs from space?  Phones you can carry in your pocket? Computers that can talk to each other?

Why, I'll bet that by 2013 we'll even have cars that fly, just like George Jetson's!


Sunday, September 1, 2013

Thinking in 3D

This week at work, just for fun, I set up a stereoscope and slid some stereo photos underneath the mirrors. These photos are high resolution, large scale shots taken back in April when we had a new orthorectified aerial image of the airport developed.  I asked the contractor to send me a stereo pair from the project that I could play around with.  It's been years since I spent any time peering though the optics of a stereoscope and it was fun to look over the images and realize just how much a stereo view adds to one's ability to pick out details.



There was a time when analyzing stereo images was a critical skill in my field and other related fields.  But with the rise of commercial satellite imagery, the slow demise of wet process aerial film cameras and the development of digital imagery analysis systems like ERDAS Imagine and ESRI's improved raster management routines in ArcGIS there has been less and less call for hard copy stereo image analysis. Software routines now handle most analysis tasks.  Of course photogrammetrists still process, manage and analyze stereo imagery, but it's all done on high end digital systems these days.  The fields that used to derive benefit from hard copy stereo imagery - topography, geology, forestry, hydrology, even the US military - all seem to have lost their institutional 'feel' for the usefulness of stereo imagery analysis.

The issue was brought home to me this week when I invited a small group of GIS professionals and Engineering staff (both licensed civil engineers and engineering technicians) to drop by my desk to have a look at these stereo photos.  Most could not get the photos properly aligned underneath the stereoscope. Few recognized any real benefit from seeing the structures in stereo.  Most thought it was just a cute parlor trick. That's a shame because the stereo photos permitted quick and easy identification of features that are not readily apparent in the same 2D images.  Things like antenna masts and raised utility piping on the roofs of concourses, raised concrete pads and curbing in the aircraft gate areas and even small assemblies like receiver domes on the tops of aircraft fuselages stood out in clear detail when viewed in stereo.
.
So how does one use stereo photos for analysis?  Check out this blog posting from a while back.

Conducting stereo analysis using hard copy photos should be much cheaper and easier these days.  Years ago in the era of wet process film cameras making copies of stereo photos was time consuming and expensive. Someone had to pull a roll of film negatives, go into a darkroom and make prints one by one. With today's digital imagery systems all one has to do is download the image files from a server and print them out using relatively cheap but very high quality color ink jet printers.  The images I received from our contractor were full resolution TIFF files, each about 1.4 gigabytes.  I was able to subset just the areas I wanted to view and print them out at full resolution using only the image management software that comes with Windows 8.  Fast and cheap!

Federal and state governments are sitting on a gold mine of historical stereo aerial photos.  The Federal government (USGS, USC&GS, Soil Conservation Service, Department of Agriculture, Tennessee Valley Authority, Army Corps of Engineers, etc.) started using stereo aerial photography for mapping as early as the mid-1920s and over the course of the next 90 years proceeded to photograph virtually all of the United States in stereo.  Stereo aerial photography was the foundation of all of our topographic mapping activities through most of the 20th century and it remains so today.  Much of this photography is still held in individual agency archives or has been turned over to the National Archives. I'd love to see the National Archives digitize and post nationally significant stereo pairs of images online for downloading and viewing. Places like the Grand Canyon, Yosemite and Yellowstone or historic events like the Mount St. Helens post-eruption photos or levee breaches along the Mississippi River during the spring floods.  Even historic shots of our cities and suburbs that will help students understand how topography impacts issues like urban sprawl.

Humans view and relate to their world in three dimensions.  It's a shame that today we are relegated to investigating it via boring 2D computer displays.  I think it's time to bring back 3D image analysis!