How to delete polygons that do not intersect a line using ArcGIS for Desktop?

How to delete polygons that do not intersect a line using ArcGIS for Desktop?

I have a layer of polygons in which I only want to keep the polygons that are intersecting the blue line.

How do I erase/delete polygons that are not intersecting the line?

The selected polygon in the image is an example of one I want to delete since it is not intersecting the above blue line.

I'm using ArcGIS 10.1 for Desktop.

  1. Start editing
  2. Select by location the polygons that do intersect the line
  3. Switch the selection
  4. Delete polygons


  1. Select polygons that intersect line
  2. Export selection to new layer

Building on @phloem's answer, an automated way to do this would be:

Build a model and use the select layer by location tool on your inputs to do a normal selection to select the polygons that touch (intersect) the blue lines

Then add another select by location tool - but switch the selection method to 'SWITCH_SELECTION' to grab the polygons that do NOT intersect the blue lines

Then tack on the delete features tool to remove the polygons that do NOT touch the blue lines, leaving only the polygons that do:

Thanks for the note @phloem!

Remove points of polylines that are outside of polygon using Leaflet

I've draw polyline programmatically (not using leaflet draw) inside polygone using leaflet draw plugin on map, I want to keep only the points of polyline that are inside of polygone and remove those are outside. Do you have any idea how to do that using a leaflet plugin?. Any help is much appreciated. Thanks

I did research on difference method of **turf" library as @Sam suggested, so finaly I can apply this method on my drawing polygon and line, here is a code snippet:

This is a screenshot of the result:

Now I want to remove this part of line and keep only the section inside polygon, I tried to do that but not working. Can you help me please? Thank you

5 Answers 5

Delete from @A where, for each record in @A, there is a match where the record in @A intersects with a record in @B.

This is based on Paul White's blog post using INTERSECT for inequality checking.

To answer your first question you can delete based on join :

The second case is really strange. I remember similar case here and many complaints about this behaviour. I will try to fing that question.

You can use Giorgi's answer to delete the rows you need.

As for the question regarding why all rows were deleted, that's because there is no limiting condition. Your FROM clause gets a table to process, but there is no WHERE clause to prevent certain rows from being deleted from @A .

  1. Create a table (T) defining the primary keys
  2. insert all records from A into T (i will assume there are no duplicates in A)
  3. try to insert all records from B in T 3A. if insert fails delete it from B (already exists)
  4. Drop T (you really shouldn't . )

Giorgi's answer explicitly compares all columns, which you wanted to avoid. It is possible to write code that doesn't list all columns explicitly. EXCEPT produces the result set that you need, but I don't know a good way to use this result set to DELETE original rows from A without primary key. So, the solution below saves this intermediary result in a temporary table using SELECT * INTO . Then deletes everything from A and copies temporary result into A . Wrap it in a transaction.

The good side of this solution is that it uses * instead of the full list of columns. Of course, you can list all columns explicitly as well. It will still be easier to write and handle, than writing comparisons of all columns and taking care of possible NULLs.

Similar tools

Use Overlay Layers to combine two layers into a single layer using an intersect, union, or erase method. Other tools may be useful in solving similar but slightly different problems.

Map Viewer Classic analysis tools

If you are combining features of the same type into a single feature layer regardless of the spatial relationship, use the Merge Layers tool.

ArcGIS Pro analysis tools

Overlay Layers performs the function of the Intersect , Union , and Erase tools.

Intersect polygon with rectangle and create lines (section cut)

I need an algorithm to intersect a (potentially non-convex) polygon with a rectangle. The rectangle will be parallel to the xy-plane, but the polygon could be any orientation.

Furthermore, I don't just need a true/false result, but also the exact points where the polygon intersects the rectangle, so that I can draw lines where the polygon overlaps the rectangle. For non-convex polygons, this could result in two or more lines of intersection.

This would be for a section-cut module that can slice a set of polygons and create a 2D "cut" where the shapes intersect the "plane," specified by a z-value.

I'm developing in Java, so if Java3(2)D has any built-in methods to help, that would be ideal.

Any help/pointers in the right direction would be greatly appreciated!

Here's a picture. I want the red line as a result of the intersection:

How to delete polygons that do not intersect a line using ArcGIS for Desktop? - Geographic Information Systems

Vector Analysis II: Topological Overlay

The topological overlay processes lie at the core of the original ArcInfo toolbox. In fact, topological overlay is what ArcInfo and its predecessors, such as Odyssey, were originally designed to do. Topological overlay allows us to ask questions like "Where are locations that are on unstable soils, andwith a slope in the range of 25-40%, andthat were harvested within the last 15 years, andon low productivity sites, and what is their percentage of area with respect to the entire watershed?"

Topological overlay is a process whereby separate layers sharing the same spatial extent are merged in different ways. The landscape architect Ian McHarg developed an analog method, a precursor to the digital implementation within GIS . His approach was to take maps traced on sheets of acetate or mylar, and place one on top of the other, and tape the stack to a window or atop a light table. Areas of overlap were darker than areas that did not overlap. The GIS performs in a similar manner, except that the input and output is more accurate and precise, and easier to manage.

The reason these operations are known as "topological" overlay is because the overlay process includes the rebuilding of the topological relationships that make layers function. In the GIS, where lines intersect between one layer and another, vertices are created. Where lines or points share the same space as polygons, the lines and points inherit the attributes of the spatially corresponding polygons. New layers are formed which can take on the attributes or coordinate properties of input datasets. Some or all features from the input datasets are passed on to the output. Attribute values from both input datasets are passed on to the output dataset.

Topological overlay is different from the Select By Layer operations described in the last lesson. In the Select By Layer operations, ArcGIS only looks at the spatial overlap of the features of two layers, and creates a new selected set in one of those layers no new datasets are produced no attribute updates are made. In Topological overlay, new layers are created whose geometry and/or attribute structure are altered. Topological overlay allows us to find overlapping features, as well as to quantify the area or length of overlap.

Buffering is a separate topic from topological overlay, but is frequently bundled with overlay because more often than not the results of buffering are used in subsequent overlay analyses to quantify the properties of the landscape within a buffer area.

In ArcGIS, geoprocessing operations, including topological overlay operations, are accessible through ArcToolbox.

ArcToolbox exists as a dockable window within any of the other ArcGIS Desktop applications (ArcMap, ArcCatalog, ArcGlobe, ArcScene). The overlay and proximity methods for feature classes (shapefiles and geodatabases) are arranged within the Analysis Tools tree within ArcToolbox:

A similar set of operations is available for ArcInfo coverage data:

The following cartoon layers will be used to illustrate the functionality of each different topological overlay operation. The sample layers are Ring and Box. Note that the Ring layer has a numeric attribute, while the Box layer has a text attribute. Where the numeric value is undefined, ArcGIS will place a 0 where the string value is undefined, there will be no value at all.

Each of the overlay operations results in new datasets. For output datasets, feature geometry is almost always modified. In cases where geometry is modified, it is possible to update geometry attributes (e.g., area, perimeter, length). the recalculation of geometry, plus the joining of user attributes, is what gives the power to the overlay operations.

Topological Overlay Types

Appending is used to merge together multiple data sets that represent the same thematic data, but are contiguous. Here is an example that shows two individual shapefiles of Public Land Survey Sections. In the image below, you can see the 2 data sets (sections_north and sections_south note the full data sets are partially obscured by the forest outline).

After the Append, there is a single data set (sections).

When 2 layers are Unioned, all features from both input layers are combined. All attribute items from the input layer and overlay layer are included in the output. The order of inputs does not matter.

Wherever you see an intersection between lines in the output, there is a node. Each enclosed area you see is a separate polygon with its own record.

Note how the null areas from each of the input layers are either null (for a character item) or 0 (for a numeric item). In the output, outside the box, there are null values for the text field. Outside the ring, there are null values for the numeric field. Also note how all input features have been retained, but new polygons have been created at intersections of input polygons. Attributes are merged where there are areas of overlap. Where there is no overlap, only the input attributes are preserved.

Here is an example of a union of some forest stand and soils polygons.

Note how all of the features from both original datasets persist in the output dataset. Wherever there are areas of overlap, new polygons are created.

An identification of one of the polygons shows the output dataset to contain attributes from both input datasets (soils attributes in green, and stand attributes in red).

The Identity function maintains all features of the input layer, but takes features from the identity layer that overlap with the input layer. The output layer's coordinate properties are dependent on which of the inputs is the identity layer. This is very similar to the Union function, but it includes a clip to the polygon boundary of the input layer.

input layer

identity layer

output layer

input layer

identity layer

output layer

Note how in the identity function, order of precedence is important. In places where there is overlap, all attributes have been joined. Where there is no overlap, only input attributes have been retained.

Here is an example of an identity performed on National Wetland Inventory (NWI) as the input layer with stands as the identity layer. The output layer has the same spatial extent as the original NWI layer, but if you look carefully, you will see there are additional polygon boundaries, formed by the overlap of stand polygons on NWI polygons.

The attributes are also joined in an identity, as shown in the results of this identify:

The Intersect operation is similar to the other overlay commands, but only areas which are common between the two inputs are included in the output. Unlike in identity, in intersect the order of input layer and intersect layer does not matter.

The only areas that exist in the output are areas that are present in both inputs (similar to an intersection of mathematical sets). For these areas, all attributes from both inputs are preserved.

Here are the same input datasets as before, with an intersect performed on the stands and NWI layers. The output dataset (in pink) is spatially limited to the area in common between the input layers. The light blue in the background is the original NWI data set, but you can see the pink data set is clipped by the edge of the forest stands.

The intersected data also have attributes from both input datasets.

Update replaces overlapping parts of the input layer with features from the update layer.

As with Identity, order of precedence is important with Update. Only the attributes in the input layer exist in the output layer. Where there are no values for particular fields, the values will be null (null values are blank for string fields, 0 for numeric fields).

Here, the soils data have been updated by the lakes data. The new layer has new polygons from stands that have been added and overwritten any existing soils polygons. This image shows the original soils data.

And updated with the lakes:

Here one of the new polygons is selected. Actually there are two polygons due to overlapping of the update polygons on the original soils.

Clip clips out parts of the input layer with the outer shape of the clip layer. Only attributes from the input layer are retained.

Input layer

clip layer

output layer

input layer

clip layer

output layer

Clip's order of precedence also matters, as you can see from two sets of different images above.

Here are is the set of culvert inventory polygons created earlier for the Pack Forest area, clipped by the administrative boundary. Only the original inventory area attributes remain.

You can see that within the administrative area the internal boundaries are the same as the original data set, but the new data set is spatially limited by the administrative boundary.

An intersection of roads and the boundary would have created a dataset with the same spatial properties as this output, but boundary attributes would also have been placed in the output attribute table.

Erase removes parts of the input layer layer based on the spatial properties of the erase layer. Attributes from the input layer are passed to the output layer, and none of the erase layer's attributes are transferred to the output. As with some of the other topological overlay operations, the order of input and erase layer matters.

Input layer

erase layer

output layer

input layer

erase layer

output layer

Here is the soils layer erased, using the lakes as the eraser. Any areas in the soils layer that overlap with lakes polygons are erased. The output attribute table has the same structure as the input (soils) attribute table.

Feature geometry values

One of the main reasons for performing any type of topological overlay is to obtain quantitative measurements of the overlap between layers. Length of line features and area and perimeter of polygon features is an inherent property of the features, but these measurements are not always present in attribute tables, and only in some cases are the geometry measurements updated during overlay processing. Here is a synopsis:

1 Answer 1

I downloaded the sf formatted files from that site (, since the sf package is a bit easier to deal with.

What you're doing here is looking for the spatial intersection of the provinces with every other province. Then you filter out the intersections where it's just a province overlapping itself ( n.overlaps == 1 ). That way you only get the interior borders where one or more provinces touches another ( n.overlaps > 1 ), but not any province alone (which would be an external border).

This is an updated version of this excellent answer:

To remove the circled points (intersections of 3 provinces) in the map and dataset, you can use:

ArcGIS Pro: editing polygons?

I have hardly used GIS in the past 2 years, and trying to brush up as I might be able to use it at my job. I think most of what I'm going to need to know is importing data, transforming coordinate systems, and editing points and polygons. Not much analysis. My first request is for any suggestions on tutorials or videos to help with this. esri's catalog seems to focus on analysis, but I'm in a time crunch and really want to focus on prepping new data and editing. I've gone through many YouTube videos on editing features, but it's still not clicking.

Right now, I'm trying to edit polygons. I think I may be given a map of the US broken up into various boundaries. Some of these will be the size of Census blocks, some will be the size of counties or even states. There may be address or zip code point data. I may be asked to break a county into 2 polygons: the boundaries of a city in that county, and the boundaries of the county surrounding the city. What would be the best way to do this? I seem to not understand Split. I tried what she effortlessly does in this video, but it doesn't do anything.

The only thing I've gotten to work so far is:Add a city boundary layer to my map.

Use it to Erase the city from the my main map, with all the current US boundaries/polygons.

Go into the attribute table of the main map, and erase the whole county.

Copy and paste the two new polygons (city from the city layer and county with a city-shaped hole in it from the newly-created Erase layer) into the attribute table.

Remove/delete the Erase layer.

This seems amateurish, and I am concerned this is going to run into problems. Maybe after doing this a few times I'll have lines that don't quite match up? What is a better way?

Thanks for any suggestions!

Edit: I'm using a trial version of Pro 2.3

Update: I got Clip from Edit->Modify Features to cut a little hole out of a county and create two new polygons! Maybe this is a better way?

Where is your data coming from?

Right now, I'm just grabbing things from the Living Atlas and trying to remember/learn how to use the software. The update really changed a lot.

In future, I am assuming the data will come from the Living Atlas, if it's trustworthy? and also from government GIS offerings.

If you open the properties of the data you're using and look at the source, is it a URL or is it stored on your computer (like C:UsersYourNameArcGIS)? If it's a URL, that may be why you can't split the data -- a lot of times those hosted datasets won't let you edit the data. You have to have your own copy before you edit it. If you need downloadable data, ESRI might have some, or you can try googling your state/region + "GIS data". In the US, the Census Bureau has a lot of data you can use too.

Otherwise, the biggest thing I screw up with the split tool is not splitting the entire polygon. When I "draw" the split line, I usually start and end it outside the bounds of the polygon -- so like, if you were splitting the state of South Dakota into east/west halves, I start the split line in Nebraska and end it in North Dakota. If you have snapping turned on, you can also just snap to the boundary edges (like the southern South Dakota boundary + the northern South Dakota boundary), but sometimes I get sloppy with the snapping and it's just easier for me to go fully outside the polygon I'm trying to split.

It sounds like you're just trying to get comfortable with the data and the tools right now, so obviously feel free to do that manually. In a work environment though, if you were tasked with making many of the same type of edits -- like you needed to break a county into "city within county" and "county outside of city" for all of the counties in a state, youɽ be better off running some of the geoprocessing tools. If you had a county boundary dataset and a city boundary dataset, you could use the union tool, or you could do a combination of intersect (to get the city pieces with the county attributes added) and erase (to erase the cities out of the counties) and merge (to put the cities/donut holes back into the counties/donuts). A lot of my job is figuring out how to make what would otherwise be tedious, manual, and error-prone edits quickly with the suite of geoprocessing tools available, so while it's valuable and commendable that you want to understand the editing tools, I promise that at least some of the analysis tools are just as important and relevant to what you want to do.

And yes, the clip tool you found is another option (this is similar to but not exactly the same as the clip geoprocessing tool in the toolbox). In the older version of the program, there were options to either remove the piece that intersects or keep the piece that intersects. I assume the newer version you're using has something similar too. Just make sure it doesn't clip a layer you don't mean for it to clip, and play around with selecting and clipping different features to understand how it works. I've finally got a working knowledge of how to use the tool effectively, but it's confusing enough that I don't think I could explain it without the software right in front of me.

2. Replicate Alsan (2015)

We will learn how to:

1. Use the Spatial Join tool (Exercise 2)

2. Export attribute tables to Stata (Exercise 3)

3. Create grid cell polygons (Exercise 1)

Why grid cell polygons?

Grid cell polygons help merge these data with other data

Exercise #1: Overview

Create 20th-century Reanalysis data grid cell polygons

We will use 3 geo-processing tools for this exercise:

As in Lecture 1, we use these tools in Model Builder.

Exercise #1: Overview (cont.)

20th-century Reanalysis data

Spatial resolution: 2° x 2°

Africa: roughly spans within

$Rightarrow$ Create square polygons whose centroid is from (-20°, -40°) to (60°, 40°) at the interval of 2°

Exercise #1: Step 1

Create Fishnet

Output Feature Class: . Lecture2 emporaryfishnet.shp

Fishnet Origin Coordinate

X Coordinate: -21

Y Coordinate: -41

$Rightarrow$ Bottom-left polygon's centroid will be (-20°, -40°)

Create Fishnet (cont.)

Y-Axis Coordinate

X Coordinate: -21

Y Coordinate: -10 (or any value other than -41)

$Rightarrow$ Y-Axis will be perpendicular to the horizontal X-Axis

Number of Rows: 41

Number of Columns: 41

Create Fishnet (cont.)

Uncheck "Create Label Points"

  • Label points: unnecessary for our purpose
  • Model Builder will still show label points as an output from Create Fishnet. This is a bug.

Geometry Type: POLYGON

Exercise #1: Step 2

The Create Fishnet tool doesn't assign any coordination system to the output file

Ethnographic Atlas data uses geographic coordinate system

$Rightarrow$ Assign WGS 1984

How? We already learned this in Lecture 1 Exercise 6.

Exercise #1: Step 2 (cont.)

Define Projection (Data Management)

Input Dataset or Feature Class: fishnet.shp

Coordinate System: GCS_WGS_1984

  • Click
  • Navigate to Geographic Coordinate Systems > World > WGS 1984

Exercise #1 (cont.)

Now save and run the Model.

Overlay the Ethnographic Atlas data

20th Century Reanalysis data cell polygons should cover the whole mainland Africa.

Exercise #1: Step 3

Browse the attribute table of the output (cf. Lecture 1)

We don't see centroid coordinates to match with weather data.

$Rightarrow$ Use the Add Geometry Attributes tool

Exercise #1: Step 3 (cont.)

Add Geometry Attributes

To add the centroid coordinate values in attribute table

Input Features: fishnet.shp (2)

  • This is the output from Define Projection
  • Don't choose fishnet.shp (which is the output from Create Fishnet)

Geometry Properties: check CENTROID

Note: this tool overwrites the input file

Exercise #1 (cont.)

Now save and run the Model.

Browse the output and its attribute table.

Is everything as expected?

Exercise #2: Overview

Merge ethnic homelands with 20th Century Reanalysis cells

Ethnic homelands: polygons

How to match polygons with polygons?

  • One polygon can overlap with several polygons
  • Which one to pick? How to aggregate them?

One way to go: match polygon centroids with polygons

Exercise #2: Overview (cont.)

Polygon centroid

Mean position of all points on the polygon boundary

$Rightarrow$ Can be matched with a single weather data grid cell

Exercise #2: Overview (cont.)

1. Create ethnic homeland centroid point features

  • We have XY data in the attribute table of the ethnic homeland polygon ( . /input/tribalmap.shp )
  • Which geo-processing tools should we use?
    • hint: Lecture 1 Exercise 3

    2. Use Spatial Join to match ethnic homeland centroids with 20th Century Reanalysis grid cells

    We now add these processes to the Model for Excercise 1

    Exercise #2: Step 1

    Make XY Event Layer

    XY Table: . input ribalmap.shp

    X Field: tribelon

    Y Field: tribelat

    Spatial Reference: GCS_WGS_1984

    Leave the other options as they are.

    Exercise #2: Step 1 (cont.)

    Copy Features

    Input Features: tribalmap_Layer

    Output Feature Class: . emporaryethno_centroids.shp

    Exercise #2 (cont.)

    Now save and run the Model.

    Browse the output and its attribute table.

    Is everything as expected?

    Exercise #2: Step 2

    Spatial Join

    Target Feature Class: ethno_centroids.shp

    Join Features: fishnet.shp

    Output Feature Class: . emporaryethno_centroids_with_20cr2.shp

    Spatial Join (cont.)

    Join Operation: JOIN_ONE_TO_ONE

    Check "Keep All Target Features"

    Field Map of Join Features: leave as it is

    Match Option: INTERSECT

    Exercise #2 (we're done!)

    Now save and run the Model.

    • I deliberately repeat this slide so you will form the habit of saving the Model before running it.

    Browse the output and its attribute table.

    Is everything as expected?

    Why cell polygons for weather data?

    If we match ethnic groups with weather data cell centroids.

    Much quicker to match points with polygons by INTERSECT

    Export to Stata

    Now we want to export the attribute table of ethno_centroids_with_20cr2.shp to Stata

    3 ways to export the attribute table to the format readable by Stata

    Export to Stata (cont.)

    Table To Excel

    Converts the attribute table into an Excel file

    But Excel cannot handle more than 65535 rows.

    Export to Stata (cont.)

    Export Feature Attribute to ASCII

    Converts the attribute table into an ASCII text file

    This tool will automatically add centroid coordinates to the output ASCII file

    Unlike Table To Excel, must specify which fields to export

    Export to Stata (cont.)


    This Stata ado directly reads a shapefile's attribute table

    But it works only with polygons

    Exercise #3

    Export Attribute Table

    • Input Table (use drop-down menu): ethno_centroids_with_20cr2.shp
    • Output Excel File: . outputethno_centroids_with_20cr2.xls

    Exercise #3

    Export Attribute Table (cont.)

    2. Export Feature Attribute to ASCII

    • Input Feature Class (use drop-down menu): ethno_centroids_with_20cr2.shp
    • Delimiter: SPACE
      • Not COMMA, to avoid confusing with decimal mark

      Exercise #3 (cont.)

      Browse the exported tables

      ethno_centroids_with_20cr2.txt has two additional columns

      • Controling which fields to be exported (ArcGIS tends to create tons of garbage fields)
      • Dealing with 65535+ observations

      But Table To Excel is simpler to execute

      "Model" model for Lecture 2

      Look at lec2model.tbx/exercises1-3 in the downloaded data folder solutions4exercises

      Main features

      • General
        • Import/export spatial data into/from AutoCAD drawings
        • Publish to Google Earth
        • Search the location of geographic objects
        • Dynamic Background image Maps from Google Maps, Bing, OpenStreeMap, Mapbox, Ordnance Survey, NearMap, etc.
          • Configurable user Maps
            • XYZ / TMS, WMTS and WMS compatible
            • WMS multi-layer maps
            • Export/Import user Background Maps
            • From 3D Points selected in drawing
            • From a grid of 3D Points built by accessing Elevation service providers in any selected area
            • 2D or 3D Contours
              • Minor and major Contours
              • Contour labels. Optional label masks
              • Layer Separation and different color models
              • Contours attached to a Data Table
              • Data grid palette interactive and synchronized
                • Selecting objects and navigation tools in the grid
                • Editing data and columns
                • Columns sorting
                • Sorting data by column
                • Automatic column width adjustment
                • Direct export to CSV, TXT, etc.
                • Multi-table grid
                • Also shows some other data as the Blocks properties (Name and Attributes), Layer, geometric properties, etc.
                • Define, modify, rename and delete tables and fields
                • Recover data table structures from the drawing objects
                • Attaching objects to a table
                • Detaching objects from their tables
                • Choose or search data from available values in the fields
                • Buffers
                • Overlays
                • Dissolve
                • Create Centroids
                • Areas of influence (Voronoi diagrams)
                • Objects imported into a new or open drawing
                • Raster and vector objects
                • Smart Batch import
                • Basic target layer or new target layers using a field value
                • Use blocks for points and centroids
                  • Select the name of the Block according to the value of a field
                  • Block insertion parameters from field values
                  • Fill properties can be taken from fields values
                  • Objects exported to geospatial files or servers
                  • Export directly from any data source to any target
                  • Export (Publish) the current status and style of the drawing to Google Earth (one click)
                    • Raster and vector objects
                    • Manage your own shortcuts
                    • Access to spatial data files (SHP, GPX, KML/KMZ, OSM, PBF, LAS/LAZ, GPKG, CSV, TXT, ASC, XYZ, MIF/MID, TAB, E00, SQLite, SDF, GML, XML, JPF, PNG, TIF, etc.)
                    • Manage your User Data Sources
                    • Access to spatial database servers (SQL Server, PostGIS, etc.)
                      • Views and Tables
                      • Notes:
                        • GIS analysis functionality is only available in the 'Professional' edition
                        • 'Street View' functionality is only available in the 'Professional' edition
                        • Transforming the Coordinate System of the objects in a drawing functionality is only available in the 'Professional' edition
                        • Terrains and related objects functionality is only available in the 'Professional' edition
                        • 'Search Location' functionality is only available in the 'Professional' edition
                        • Data management (Structures, Queries, Direct editing, etc.) based on XDATA / Extended Entity Data (EED) is only available in the 'Standard' and 'Professional' editions
                        • Data grid is only available in the 'Professional' edition, although the overall data management (Structures, Queries, Direct editing, etc.) is also available in the 'Standard' edition
                        • 'Background maps' functionality is available in the 'Standard' and 'Professional' editions only
                        • Full export functionality (SPMEXPORT) is only found in the 'Professional' edition, although the functionality to export the current status of the drawing to Google Earth (SPMCREATEKML) is also available in the 'Standard' edition
                        • The Tasks technology is available in the 'Professional' edition only
                        • "MPolygons" are available for all compatible Autodesk products (even on basic AutoCAD)
                        • You can optionally prevent the automatic activation of the "Geolocation" Tab in the AutoCAD Ribbon, because it may interfere with the functionality of the new Background Maps and other applications or AutoCAD functions (use SPMOPTIONS)

                        To get a first preview of the application, please watch this video:

                        IMPORT video updated on May 2018

                        To experiment the EXPORT capabilities (on the 'Professional' edition), please watch the following videos:

                        To know how to BATCH IMPORT works, please watch this video:

                        To take a look at the TASKS technology (on the 'Professional' edition), please watch this video:

                        To learn how is working the DIRECT DATA EDITION and how to MANAGE the DATA STRUCTURE (on the 'Standard' and 'Professional' editions), please watch the following videos:

                        To know more about the attractive and useful dynamic BACKGROUND MAPS (on the 'Standard' and 'Professional' editions), please watch the following videos:

                        To know how to LABEL the objects WHILE IMPORTING, please watch the following videos:

                        To know how to Use the BLOCKS WHEN IMPORTING, please watch this video:

                        To know how to Create elevation 3D Points, Contours or Terrains, please watch this video:

                        Here you will find all the technical information available on the implementation as well as tutorials, additional data, etc.

                        Watch the video: Feature Dissolve