Blog

INT is pleased to announce the newest release of GeoToolkit.JS data visualization libraries and toolkit. This major release includes new 3D visualization capabilities—contour 3D, 3D shape highlighting, and better 3D seismic—and new rendering options.

As the use cases of IVAAP grow, the implementation of the data backend evolves. Past releases of IVAAP have been focused on providing data portals to our customers. Since then, a new use case has appeared where IVAAP is used to validate the injection of data in the cloud. Both use cases have a lot in common, but they differ in the way errors should be handled.

One of the most challenging data management problems faced in the industry is with seismic files. Some oil and gas companies estimate that they acquire a petabyte of data per day or more. Domain knowledge and specific approaches are required to move, access, and visualize that data. In this blog post, we will dive deep into the details of modern technology that can be useful to achieve speed up.

INT has been working with the Open Subsurface Data Universe™ (OSDU) consortium since the beginning of the OSDU forum in 2019. INT made IVAAP available as part of the Demo release of the OSDU platform. The OSDU is a standard data platform for the oil and gas industry which will reduce silos and put data at the center of the subsurface community.

Map-based search is an integral part of subsurface data visualization. In order to meet usability expectations, developers of subsurface applications in the cloud must add powerful map and map-based search functionalities. The GeoToolkit map widget simplifies the process, allowing users to get quick and clear insights using common web mapping services.

This release confirms IVAAP as a leader in the subsurface data visualization space, supporting Data Visualization and Data Management for Subsurface, Exploration, Drilling, or Production Applications in the cloud. Houston, TX — INT is pleased to announce the newest release of its HTML5 upstream visualization platform, IVAAP™ 2.6, accelerating the pace of our release cycle […]

Weatherford International plc (OTC Pink: WFTLF) announced a strengthened collaboration with upstream data visualization provider INT to provide next-level, real-time well visualization in both 2D and 3D. Weatherford will embed INT’s IVAAP framework into the Weatherford Centro™ digital well delivery software, advancing its data visualization capabilities.

INT has been a long-time pioneer by providing JavaScript components that empower developers to build geoscience applications that run in a browser. The GeoToolkit.JS libraries cut years of development time for any company creating a new application or replacing a legacy system. However, the added value of this kind of application is not just in accessing and visualizing geoscience data, it’s also in the integration of the company’s knowledge within this application.

Despite the advantages of 3D rendering and the trend of migrating applications to web browsers, there are various obstacles that developers have to face and overcome. The steep learning curve, the insufficient cross-platform support, and the difficulty of maintaining make WebGL a beast to work with. In a way, we want to keep the obstacles away from web developers, so INT provides Carnac3D, a subset of GeoToolkit, as an industry-leading graphical product.

Recently, INT announced our partnership with Bluware and our integration of Bluware’s OpenVDS format into IVAAP, our enterprise data visualization platform. We are very excited about this partnership, as well as our collaboration with OSDU. This new format was designed to empower users to browse seismic data in the cloud with high performance and lower cost.

IVAAP on OSDU R2 supports seismic visualization, data aggregation with unparalleled performance in the cloud to serve large seismic volumes using IVAAP’s HTML5 technology combined with OpenVDS format.

Interactive Network Technologies, Inc. (INT) a leader in advanced domain visualization in digital exploration and production (E&P) and Bluware Corp., the digital platform that enables the oil and gas industry to accelerate digital transformation initiatives and adopt cloud computing for subsurface data, are pleased to announce the integration of Volume Data Store (VDS), a data format with adaptive streaming technology for seismic data storage, into IVAAP, an upstream data visualization platform. 

When doing demos of IVAAP, the wow factor is undeniably its user interface, built on top of GeoToolkit.JS. What users of IVAAP typically don’t see is the part accessing the data itself, the IVAAP backend. When we designed the IVAAP backend, we wanted our own customers to be able to extend its functionalities

GeoToolkit is a suite of 2D and 3D data visualization libraries that display well log, seismic, contour, schematics, BHA, maps, and more in JavaScript. Released earlier this year, GeoToolkit.JS 2020 comes with various new features and significant improvements. Highlights from the latest release include: improved ArcGIS support, faster load times, new tools, multilateral schematics, new gridding algorithms, and improved memory for volumetric rendering.

INT is pleased to announce the latest release of its enterprise upstream visualization platform, IVAAP™ 2.5. This version includes new production dashboards to enhance analysis and monitoring. Support for curve dictionaries and aliases makes it easier to build powerful log templates. IVAAP now fully supports the display of raster logs in well and correlation views (with support for TGS SmartRASTER® format).

Feedback is key to the improvement of any software. INTViewer has many long-time users, and one piece of feedback that I sometimes receive is that “it takes too many clicks to reach an often-used feature.” Fortunately, with many years of real-world usage under its belt, the usability of INTViewer has been fine-tuned. These “missing” shortcuts are already built-in, I just didn’t do a good job communicating these improvements to our users. So here is our list of the 5 most overlooked INTViewer shortcuts.

As a non-developer living in a developer world, I wanted to understand more about why we develop our software to work with Kubernetes. So I sat down with INT’s Senior Product Manager Steven Reynolds and Senior Architect James Velasco to learn more about Kubernetes and the advantages of working with it.

2019 has been a year full of milestones. INT celebrated its 30 years and has made IVAAP available to all members of the OSDU consortium as part its demo release. But this year has seen many more achievements, and among them is the consolidation of INT products as a complete ecosystem, an ecosystem centered around geoscience data, built for the cloud.

Bluware Corp., the digital innovation platform for seismic data, is pleased to announce a strategic partnership with Interactive Network Technologies, Inc. (INT), a leader in multi-domain visualization in exploration and production (E&P). Bluware and INT are early members in the Open Subsurface Data Universe (OSDU), a forum focused on developing a standard that creates a common data platform for all exploration, development, and well data. The standard will transform the way subsurface data is captured, analyzed, and operated.

Working at INT for 10 years, what has made me show up every morning has been the deep technical aspects of the job, the products I have been able to work on, and the people I interact with. Frankly speaking, these 10 years were also possible because developers at INT are seen as an investment, not a cost. Unlike other companies, INT has a strong will to weather tough economic cycles without shrinking its staff. I have grown with INT, and we both keep growing together.

Cloud storage connectors, ArcGIS and PPDM integrations are part of the many new features of the latest release of IVAAP (2.3) which pushes the limits of what’s possible in Subsurface Data Visualization in web applications. This version has significantly developed support for visual-based data discovery using map-based search, and is fully integrated with ArcGIS, allowing explorers to search structured and unstructured data in a data lake or any other file repository. IVAAP supports elastic search as well as other search engines and is able to index and read any subsurface data types.

Programming is an activity that requires a special set of cognitive skills. While the industry has developed processes and tools to ensure the quality of software artifacts, the act of writing code is a craft in itself. Developers pride themselves on the “big picture” results they achieve, but the activity of programming is definitely a humbling experience: it’s easy to introduce bugs, and regardless of whether I catch them right away or later in the pipeline, I hate to be reminded I am inherently flawed and have introduced a defect. For this article, I will focus on simple methods to avoid bugs, not before or after you write code, but while you write that code.

One of the unique features of the IVAAP backend SDK is that you can develop your own data connectors and services with the IDE you are already familiar with. The data backbone of IVAAP is meant to be deployed in a cluster made of multiple nodes for scalability and reliability. However, despite the distributed nature of such a deployment, our SDK requires no particular plugin to compile or execute your code. The tools needed to develop a plugin for IVAAP’s backend are identical to the tools you would need to develop classic Java Servlets: a Java SDK (Oracle, OpenJDK), an IDE (Eclipse, NetBeans) and an application server (Tomcat, Glassfish).

Total and INT have recently announced a long-term corporate agreement that will give Total access to INT’s GeoToolkit, the most widely adopted JavaScript-based data visualization technology software in Oil and Gas. Total will also be able to take advantage of IVAAP, one of the leading Data Visualization software platforms for digital subsurface projects deployed in […]

Over the last few months, there have been a lot of activities and discussions with upstream majors on how to make subsurface data easier to search and discover and how to automate some of the geophysical and/or petrophysical workflows. This process has typically been very challenging. From a user experience perspective, the ideal scenario would be to do this from one system versus doing this very manually from current siloed applications. We’ve been able to do this successfully here at INT.

IVAAP was not just meant to be a web application “built for purpose”—we wanted it to be a platform that customers can extend on their own. With this goal is mind, the first component that we picked for IVAAP’s architecture was a “lookup” system. This system makes IVAAP easy to learn, yet versatile, and devops appreciate that they can leverage it when a fast turnaround is needed.

It’s been two years since Oracle announced the donation of the NetBeans source code to the Apache software foundation. This move was much more than a licensing change — it was a bit of a new beginning for NetBeans. With the release of NetBeans 10, now is a good time to look back and recognize the changes that this transition to Apache brought.

While some customers will use the portability of INTViewer to present their data, others will use INTViewer on a workstation, with multiple monitors. And instead of opening a handful of windows, they will open a few dozen. The typical use case for opening a large number of windows is when you want to monitor the multiple steps of a processing workflow. In such a use case where datasets are compared, it’s important that all visualizations share the same settings. INTViewer makes it really easy to open dozens of datasets at once. You can select a directory and open in one click all the datasets within that directory. But this is not where INTViewer’s productivity stops. Automatic synchronization facilitates the management of all these windows.

The purpose of IVAAP’s backend is to access data from many data sources and present this data in a unified manner to the IVAAP HTML5 client. Performance is key, and some data stores are faster to access than others. In a web service configuration, a smart caching strategy is required so that the same web/HTTP calls are not made to the same data store twice while a service request is being fulfilled, regardless of its complexity. This is where the concept of scope comes in.

As a new member of the software development team, I had no prior experience with development on IVAAP, INT’s HTML5 visualization framework for upstream E&P solutions. My first task was to add a data connector, so to gain knowledge of IVAAP and to understand more about the IVAAP software development kit, I used the IVAAP developer’s guide. I found this guide quite useful as it made the key points behind IVAAP easily understandable. Coding with IVAAP is actually easy, and I was surprised by several features of the platform and SDK that make it quite simple to learn.

I often have a hard time explaining to friends and family what exactly INTViewer does. The moment I use the word “seismic,” the listener's mind automatically shifts to the topics of seismic activity and earthquakes, and I need to explain oil & gas exploration technologies before I even get to the software. By then, I have lost my audience. Today, I’ll try a different technique: I’ll describe the capabilities of INTViewer that actually cater to earthquake mapping. I will show how you can use the built-in capabilities of INTViewer to map recent earthquake activities.

I often say that INTViewer is a bit of Swiss knife. It serves multiple purposes, and each company finds a different use. This makes it hard to decide which feature to highlight. In the past few years, as the industry moved to the cloud, we created a companion for INTViewer: INTGeoServer, which makes it easy to visualize data beyond the bounds of your network. This year, with the new release of INTViewer approaching, I will highlight the opposite feature of INTViewer: its ability to work offline, disconnected from the world.

In our previous blog, Simplifying the Learning Curve of the Seismic Unix Library, we described how INTViewer can leverage the SU library. This library is typically meant for Linux, but it can also be used on Windows. This walkthrough describes how to install the SU Library on Windows 10 to use the Seismic Workbench plugin.

Two decades after its creation, the Java runtime has finally become modular. A modular approach not only makes dependency management easier, but it also makes applications more efficient as unused modules don’t need to be loaded. The NetBeans Platform predates Java 9 and has been using its own module system for years. Since INTViewer is a desktop application built on top of the NetBeans Platform, I find that it is far superior to the Java 9 module system for my use cases.

With the explosion of storage capacity, cloud computing, and bandwidth availability, a trend has emerged in the oil and gas industry over the last few years. Data that was previously aggregated and discarded is now maintained and stored, creating an opportunity for the industry. Coupled with new advancements in machine learning and Al, this data availability is poised to drive more data driven decision making in well planning, drilling & completions, and well operations.

Traditionally, the oil and gas sector has been slower than other industries to adopt new software and technology. When the market is doing well, companies have little time or motivation to invest in change. When the market is bad, companies lack the appropriate resources and budget. Since 2015, the oil and gas sector has experienced significant changes. An aging workforce, low oil market price, and the pressure to transition to cleaner energy are among the many factors forcing the Exploration and Production industry to rethink how it works, recruits, trains, and operates in order to stay in business.

In this post we consider how to display data, which includes geometry and nonspatial information like names from ArcGIS ESRI services using the GeoToolkit.JS Map Widget and WMTS data from OpenStreetMap.

INTViewer provides a graphical user interface for the SU library, reducing the learning curve. The Seismic Workbench is a free plugin that has the documentation for the SU library built in, making it easy to find a particular command and all the parameters that this command requires. INTViewer builds the full command line for you based upon all individual commands selected.

Storing and accessing large, sometimes sensitive geoscience data is one challenge many top E&P companies face. Local data storage is one option. But what about data that is not stored locally? How do you access it quickly, and can you still use INTViewer?

In our latest Tech Talk, E&P Visualization in the Cloud, we featured IVAAP, our cloud-enabled visualization and analytics development platform. We showed how it can be used to monitor and analyze well data as a critical part of your digital transformation. Thierry Danard, our VP of Core Platform Technologies, presented some of the technical aspects of IVAAP, so we asked him a few questions after the talk to dig a bit deeper.

A major feature of INTViewer 5.2 is the Python integration. Our development team worked very hard to ensure that our customers can get started easily and be productive once they are hooked. One consistent user feedback was that the Python terminal lacked autocompletion. It could become tedious to have to type the full name of each class, each method or each variable. We took this feedback to heart and implemented autocompletion in INTViewer 5.2.

Presenting data to clients regularly poses many challenges, especially considering that today's datasets are more likely to exceed a petabyte or more. Slideshows that may take hours to create are often instantly obsolete and frequently don't fully answer your clients' questions. With one simple plugin, INTViewer transforms the art of showing data to your clients by combining the simplicity of a slideshow and the power of live data.

I have been using NetBeans daily for about 8 years, so I'd say I am pretty familiar … with the features I use all the time. Over the years, friends and colleagues have shown me that there are faster ways to get the job done. I have gathered in this post three shortcuts that I learned from others and that you can also use when you develop an INTViewer plugin.

In our blog post on Microsoft Azure, we describe various ways customers can move their data to the cloud. In the configuration where INTViewer is hosted on a remote server and needs to be accessed from a local workstation, a Teradici client is one solution. These configurations are increasingly popular with our customers. For performance […]

Horizon picking is a feature that INTViewer has included from the start. However, after discussing with several long-time users, I have found that the evolutions brought by each release can be missed. The release of INTViewer 5.2 is a good opportunity to tour basic picking options. First, a bit of terminology. The term “horizon” in […]

In our post, “Closer Look at Coordinate Conversions,” we allude to the capabilities of INTViewer with coordinate system conversions. One benefit of on-the-fly conversions is the ability to see your seismic data in context. In the example below, a time slice is reprojected to the coordinate system used by Google Maps.     Showing satellite […]

INTViewer is well-known for its seismic analysis capabilities. Among the less well-known plugins, there is a set that always impresses during demos: the microseismic plugins, a set of four plugins that allows INTViewer users to visualize microseismic events.

If you are already a user of INTViewer, the first thing you will certainly notice when you open INTViewer 5.2 for the first time is the new window system. The way windows are laid out on screen has changed, introducing tabs to browse through these windows.

INTViewer makes coordinate conversions virtually transparent to users. Users pick two Coordinate Reference Systems (CRS), one for their data and one for the visualization map, and the visualization updates automatically. How does INTViewer do it? The short answer is “it depends”. The long answer is that the strategy used varies based upon the CRSs selected, […]