If economic illnesses had physical instead of fiscal symptoms, the construction industry would have a harsh cough and aching muscles. For now, it’s working through the pain. If left untreated, however, its condition could become chronic. Perhaps even terminal.

As a result of myriad factors—including declining immigration, reduced funding for high school shop classes, and the lingering effects of the 2008 housing crisis—the construction industry is in the midst of a dire labor shortage. In August 2018, construction employers in the United States had 317,000 unfilled positions—the largest number of open construction jobs since the Great Recession. In September, the U.S. Chamber of Commerce’s quarterly Commercial Construction Index likewise showed that 94 percent of contractors are having a difficult or moderately difficult time finding skilled workers.

The consequences of inadequate labor are as acute as they are numerous. For one, buildings take more time and money to complete. Companies and communities, meanwhile, are unable to grow. Because they must do more with less, builders are tempted to take shortcuts, creating unnecessary risks that compromise quality and safety. But from necessity comes innovation: The construction industry is rapidly shifting to a new business model based on modular rather than conventional construction.

While conventional buildings are built entirely onsite, modular buildings consist of standardized components that are pre-fabricated in an offsite factory, then assembled in the field. Like structures made from toy LEGO bricks, modular buildings can be configured in any fashion, then customized with accessories and embellishments; the underlying components, however, are identical. With conventional buildings, contractors are limited by environmental conditions and linear construction in which each successive step must be completed before the next can begin. With modular buildings, construction takes place in a controlled environment, wherein processes that would normally unfold in succession do so in parallel. As a result, modular buildings can be completed faster, cheaper, safer, and with fewer workers.

Like the construction industry, the GEOINT Community has insufficient resources relative to demand for its services, which is growing rapidly thanks to an influx of geospatial data from small satellites, unmanned aerial vehicles (drones), and the Internet of Things.

“There’s more location information coming into organizations than ever before,” said Andy Dearing, CEO of geospatial software and services company Boundless. “What we see in the geospatial space is that organizations are trying to figure out how to scale their location enterprises to process all that data and make more informed decisions. Traditional proprietary technologies aren’t built to do that.”

Like builders, many geospatial practitioners are adding to their toolbox with a modular solution: open-source software, which is already changing the course of geospatial intelligence.

Open Evolution

Though it’s new to many organizations, open-source software isn’t new at all. In fact, it’s as old as computing itself. As early as the 1950s, computer hardware was distributed not only with free operating software, but also with its source code so bugs could be fixed and new functions could be added. This was thanks to early adopters, most of whom, as academics and researchers, were collaborative and open by nature. Only when computing became commercialized in the 1970s and ’80s did software become commoditized and “closed.”

As for the modern notion of open-source software, most developers trace its roots back to 1991. That’s when Finnish computer science student Linus Torvalds created Linux, a free and open-source operating system inspired by Richard Stallman, a computer programmer at the Massachusetts Institute of Technology (MIT), who, in 1983, established the GNU Project to create free and open software.

“Richard Stallman … was an early thinker and proponent of ‘free’ software,” said Richard Grady, president of Applied Geographics (AppGeo), a GIS consulting firm that has used open-source software since 2008. “He believed software should be free to run, free to study, free to modify, and free to share.”

In the GEOINT Community, open-source software has an unlikely grandfather: the federal government. In 1979, the U.S. Department of the Interior created the Map Overlay and Statistical System (MOSS) to help the U.S. Fish and Wildlife Service track and evaluate the impact of coal mine development on the environment. To maximize development speed and minimize development cost, the committee in charge mandated MOSS use as much code as possible from the public domain. The resulting product was the world’s first broadly deployed, vector-based, interactive geographic information system (GIS).

In 1985, the U.S. Army’s Construction Engineering Research Laboratory released the Geographic Resources Analysis Support System (GRASS), an open-source GIS software suite created to assist the military with land management and environmental planning.

“There were proprietary vendors that had GIS packages, but when the government approached them with [additional requirements] they said, ‘Sorry, that’s not really our thing.’ So the government decided to write its own software and put it out under an open license,” said open-source advocate Dr. Christopher Tucker, principal of Yale House Ventures.

Screenshot of the Geographic Resources Analysis Support System (GRASS) interface.

GRASS—whose code continues to underlie open GIS software more than 30 years later—laid the foundation on which all subsequent open-source geospatial solutions were built. A few of the most significant were: the Geospatial Data Abstraction Library (GDAL), created in 2000 for the purpose of reading and writing raster and vector geospatial data formats; GeoServer, launched in 2001 to facilitate sharing of geospatial data; PostGIS, released in 2001 to add support for geographic objects to the PostgreSQL (Postgres) open-source relational database; QGIS, an cross-platform desktop GIS application introduced in 2002; and Cesium, a JavaScript library developed in 2011 for use with 3D mapping applications.

“Open-source software used to be hard: A government had to decide to invest in a piece of software. A government had to decide to spin it out. And a government had to apply dollars and lawyers and developers,” Tucker said. “But by the mid-2000s you started seeing more and more developer infrastructure out there that made it easier for developers around the world to coordinate.”

It was a short leap from coordination to organization. In 2006, open-source developers established the Open Source Geospatial Foundation (OSGeo), whose annual Free and Open Source Software for Geospatial (FOSS4G) conference attracts more than 1,000 open-source developers and advocates every year.

Another powerful inflection point was the 2008 formation of GitHub, the web-based repository through which open-source software developers store and share their projects for consumption by the global developer community.

“GitHub made it super easy for communities of developers all around the world to collaborate,” continued Tucker, who calls GitHub a revolution in code management and IT software project management. “Every cool, smart kid realized that if they didn’t like their job and had a good idea, they could develop software on the side and create something amazing. That poured fuel on the fire.”

The brighter the fire burned, the more attention open-source software received. Now, the flames are so hot that even the most “closed” users like the Intelligence Community are creating and executing open-source strategies.

“The federal government is interested in having open and transparent conversations. Not just with words, but with code,” Dearing said. “They’ve realized, ‘We can’t do it all ourselves anymore. We need help, and there’s help out there.’”

Super Software

There are many reasons the GEOINT Community has embraced open-source software in both the public and private sectors.

For government users, the most attractive benefit is cost, according to Will Mortenson, lead for volunteered geographic information at the National Geospatial-Intelligence Agency (NGA), which in 2014 became the first U.S. intelligence agency to share open-source software on GitHub. “We’ve historically had more requirements than we could answer with our traditional budget,” explained Mortenson, who said open-source software is an affordable alternative to single-use solutions; while the latter must be built from scratch—usually at considerable expense—the former often meet most of NGA’s requirements out of the box, and can be customized to fill any gaps.

Achieving scale can also be cost-prohibitive.

More often than not, a hybrid environment works best because you can pick and choose where it makes sense to implement open-source technologies and where it doesn’t.
– Andy Dearing, Boundless

“With open source, the incremental cost of scaling up is near zero,” Grady said. “Because you’re not paying for software licenses, you can add users. And when there is no friction to adding users, there is much greater adoption and utilization of technology, and much greater sharing of data.”

Echoed former Boundless CEO Eddie Pickle, managing director of open-source programs at GEOINT services company Radiant Solutions, “In the ’90s, proprietary software was [synonymous with] interoperability. The way we moved data around and tried to solve problems together was having a lot of people rallied around using similar technology. But the development of the internet blew that ecosystem wide open. … You just couldn’t deploy a solution where you knew you were going to have to make everybody down the chain invest in proprietary software. There was nothing wrong with the software, but you just couldn’t predict how much of it you really needed. That led to the demand for open-source software.”

And licensing isn’t just expensive, it takes time. “When most people encounter free and open-source software, the tendency is to focus on the ‘free’ aspect: Why would you pay for software when you can get it for free?” said Peter Girard, chief technology officer at AppGeo. “Personally, I don’t find the free aspect of open-source software all that compelling. If something has value, I’m willing to pay for it. Why I favor open-source over proprietary software is because it gives me freedom. I don’t have to ask permission to use a piece of software. If I determine, for instance, that I need to use Postgres and PostGIS as my geospatial database, I just do it.”Open-source software also accelerates innovation by streamlining development. “There’s no value in building table stakes—things that every app has to do, like user management, payment gateways, and logging,” said Mark Curphey, vice president of strategy at CA Veracode, an application security firm that specializes in securing open-source software. “So over the years people have extrapolated that stuff into reusable code libraries and frameworks that everyone can use, which allows developers to focus on building differential features.”

If software development were a queue, open source lets developers skip to the front of the line.

“The barrier to entry … is very low, so you can get lots of grassroots adoption by integrators and engineers to try things out and prototype, which lets you move very quickly,” explained Cesium creator Patrick Cozzi, principal graphics architect at Analytical Graphics Inc., who said another advantage of open source is customization. “In the GEOINT space, in particular, the need for customization is often very high.”

Arguably the greatest benefit of open-source software, however, is the community of users behind it.

“When I’m contributing to open-source software, the maintenance and development of that software does not fall squarely on my shoulders,” said Scott Clark, a program manager at Radiant Solutions, where he specializes in open-source software development. “[PostGIS creator] Paul Ramsey did a great talk a few years ago and compared open-source software to a barn raising. When you wanted to raise a barn back in the day, the community would come out and help you build it because you couldn’t do it by yourself. That helped out the community, because the next time somebody else had to raise a barn they got help, too.”

Open-source software often has thousands of stakeholders, according to Grady, who said quantity of users typically correlates with quality of software.

“There is a tremendous amount of knowledge development in software,” Grady said. “Leveraging that knowledge is how we build on those who went before.”

The open-source community believes in the group so strongly that it even has a term for its potential: Linus’s Law, named for Linux creator Linus Torvalds.

“Linus’s Law states, ‘With sufficient eyes, all bugs look shallow,’” said David Egts, chief technologist for the public sector organization at open-source solution provider Red Hat. “What that means is: If you have a robust community of people working on your code, the level of innovation is going to be higher.”

In the GEOINT space, in particular, the need for customization is often very high.
– Patrick Cozzi, Cesium

From a GEOINT perspective, having a large and diverse community with which to share code also makes it possible to evangelize and evolve the profession. NGA, for example, is using open-source solutions to increase GEOINT adoption globally.

“Geospatial technology applies to a whole set of various problems that don’t just span across the IC and DoD,” said Ben Foster, NGA’s product manager for mobile development and operations. “By open sourcing the stuff that we’re producing, we’re lowering the barriers of entry [into GEOINT services] for a lot of our international partners.”

Added Cozzi, “Once you make something open-source, anyone can pick it up. Cesium, for example, is used by NGA’s Map of the World web client in the GEOINT world, but it’s also used by Mozilla for mixed reality, by the Toyota Research Institute for autonomous driving simulation, and by Bentley Systems for CAD/BIM fusion with geospatial data. The list goes on and on, and each of those different types of users brings use cases and perspectives into that core platform to improve it.”

A Hybrid Approach

Despite the boom in open-source software adoption, proprietary software—also known as commercial off-the-shelf (COTS) software—still has many advantages. For one, the “free” in “free and open-source software” often refers to freedom, not cost. So while many open-source solutions are gratis, not all of them are. Plus, open-source software typically does not come with technical support, so organizations may have to hire experts to assist with implementation, integration, and ongoing administration. Costs can therefore be unpredictable relative to proprietary solutions.

Vendor viability is another concern. Compared to open-source providers, which are often vulnerable to acquisitions, mergers, and failures, proprietary vendors tend to have more stability and longevity, and can therefore promise greater continuity.

If you have a robust community of people working on your code, the level of innovation is going to be higher.
– David Egts, Red Hat

With open-source, the developer community controls the product roadmap. Often, this results in features and capabilities that users want. Sometimes, however, solutions veer in undesirable directions. Therefore, proprietary vendors may give individual users more control in pursuit of their unique requirements.

Given their respective strengths, the best solution for GEOINT needs lies in neither open-source nor proprietary software exclusively. Rather, it’s applying the best of both using open platforms and standards.

“We don’t recommend ripping out and replacing proprietary solutions.

We advise people to put open-source technologies alongside proprietary technologies because there are ways to implement and integrate,” said Dearing of Boundless, whose core business is providing commercial support for open-source geospatial software. “More often than not, a hybrid environment works best because you can pick and choose where it makes sense to implement open-source technologies and where it doesn’t.”

The upside of a hybrid approach is evident in one of open-source software’s unlikely proponents: Esri. Though its GIS software is the definition of COTS, the company nonetheless has welcomed open-source philosophy in order to enhance its proprietary offerings, leveraging the best of both.

One way Esri participates in the open-source community is with open specifications, which it co-develops as a participant in the Open Geospatial Consortium (OGC). “Esri has made a strong commitment to being an open platform, meaning we are very focused on standards and making sure those standards support an open ecosystem,” explained Ben Conklin, defense and intelligence industry manager at Esri.

Open standards enable interoperability between closed- and open-source systems.

“We see this a lot in the GEOINT Community today—both open-source and commercial software, working hand-in-hand through the interoperability of open formats and open standards,” Cozzi said.

Esri also supports open-source projects as a user whose feedback contributes to fixes and updates that benefit the entire user community. Its software, for example, supports the Red Hat Enterprise Linux and SUSE Linux open-source operating systems, as well as the Postgres open-source database. It also incorporates numerous open-source tools, languages, and libraries. And the company regularly shares via GitHub its own open-source applications that help users customize and extend its proprietary GIS software.

Though there’s no denying the potential merits of open code, the sum of Esri’s efforts is something Conklin believes is more powerful: open community. “To me, the most important aspect of open source is the idea of a community built around software, where many people contribute to it and many people benefit from it,” he said.

Enabling the Future

An open community approach must be similarly embraced by the larger GEOINT Community as it builds capacity for the next generation of GEOINT services.

“Geo problems are geo problems. Those problems won’t change, but the scale of the data that people can apply to those geo problems is about to go off the charts with the Internet of Things, autonomous vehicles, signals intelligence—you name it,” Pickle said.

Therein lies the promise of open-source software: By leveraging the size and diversity of the global developer community, GEOINT enterprises faced with complex data management problems can develop solutions quickly, creatively, and cost-effectively.

“Think about the benefits open source provides. You’ve got a cost cap because there’s no license for the software, you’ve got the ability to quickly develop systems because the source is open, and you can collaborate in an unlimited fashion,” Pickle continued. “Now think about the problems of the future—data fire hoses coming into distributed systems that have many users with varying needs. You just can’t solve them without open source.”

Layered on top of breakthroughs in automation, artificial intelligence, and cloud computing, the potential is overwhelming.

Concluded Grady: “The global community of developers harnessing the cloud and machine learning, and applying it to new real-time data feeds? Wow. Look out.”

Featured Image: OneSky, a situational awareness app for UAVs, uses Cesium, an open-source library for 3D mapping. (Credit: Cesium)

Related


Posted by Matt Alderton