Confused With Conflation? Let’s Clean Up the Mess.

Let's Set Things Straight with an Example.


Are you confused with conflation?

When you have two conflicting data sets, conflation resolves conflicts by preserving the most accurate one.

Confused no more.

Let’s set things straight with an example.

Do You Need Data Conflation?

Certain industries are most prone to using conflation. To name a few, transportation and construction often have conflicting data sets.

When you have different authority groups (national, local and private sector), data is often collected differently. Whether it’s captured at different scales or in the field, it comes down to how the geographic data was collected.


In the two road data sets above, the red polylines are most accurate. However, the yellow data set has more attribute information.

So you want to move attributes from another polyline data set to another. What to do?

If you want to mix these two road data sets together, then you would use some of the conflation tools. When using ArcGIS, the conflation tools are under the Editing Toolset.

Conflation Toolbox

Edgematch End Points

When you have two counties with disconnected lines at the borders, you should use the edgematching tools to connect them.

In the case below, there are disconnected lines at the border. This is a case when you’ll need to use some of the conflation tools.

Conflation Is Needed

In order to conflate these two data sets, you should use a two-step combo. First, you’ll have to generate edgematch links. Secondly, you’ll actually move those end points connecting the two data sets.

In this step, you generate edgematch links and see where those connections are made geographically.

Edgematch Links

Tip of the Century: Before you begin the next step, make a copy of the data set you want to conflate.

For the data set you want to conflate, you’ll edgematch features by moving each endpoint automatically.

Edgematch Move Endpoint

Alternatively, you can choose to edgematch features by adding a whole new section and vertex like in the example below.

Edgematch Add Segment

Finally, you can physically adjust all the vertices and truly conflate data sets.

Edgematch Adjust Vertices

After running the two-step process, we have a fully conflated roads data set. All the end points will match along the boundary saving time.

Rubbersheet Two Data Sets

While edge matching is good for end points, rubbersheeting conflation matches a whole load of vertices.

As you can see in the example below, these two data sets are not aligned.

Conflation Rubbersheeting

The first step to take is to generate rubbersheeting links as displayed with arrows.

Conflation Rubbersheeting Links

Again, make a copy of the data set you want to conflate.

When you rubbersheet feature, you are physically moving all those vertices from one data set to another. Depending on the rubbersheeting links, you should get similar looking features using either one of the linear and natural neighbor methods.

Conflation Rubbersheeting

Finally, you can transfer attributes from one data set to the other.

Cleansing the Ruins

We live in a data world.

It’s quite common for repetition of data sources.

While the ideal solution is for everyone to work together from the start, conflation works by resolving conflicts by preserving the most accurate one.

Have you ever done conflation? What works best and worst, let us know with a comment below.

Be the first to comment

Leave a Reply