topic Deleting Lines that are not assigned to the <Room Separation> subcategory in Revit API Forum

Deleting Lines that are not assigned to the subcategory

62BJW — Wed, 01 May 2019 20:26:59 GMT

I have code that deletes all lines in the document. I only want to delete the lines that are not on the <Room Separation> subcategory. I probably need to add something to my FilteredElementCollector but I can't figure out what. Thanks in advance.

                    //Lines
                    var linIds = new FilteredElementCollector(doc, vw.Id)
                        .OfClass(typeof(CurveElement))
                        .ToElementIds();
                    foreach (var lin_id in linIds)
                    {
                        doc.Delete(lin_id);
                        linCount++;
                    }

Re: Deleting Lines that are not assigned to the subcateg

recepagah12 — Wed, 01 May 2019 22:38:00 GMT

You can use LINQ to query the elements. With LINQ, you can check element's category.

Here is the code snippet.

// This filtered element collector collects all elements in the document except room seperation lines
var lines = new FilteredElementCollector(doc).OfClass(typeof(CurveElement)).Cast<CurveElement>()
        .Where(q => q.Category.Id != new ElementId(BuiltInCategory.OST_RoomSeparationLines)).ToList();

foreach (var line in lines)
{
     doc.Delete(line.Id);
}

I hope this helps,

Recep.

Re: Deleting Lines that are not assigned to the subcateg

jeremytammik — Thu, 02 May 2019 06:55:49 GMT

Dear Bernie,

Thank you for your query, and many thanks to Recep for his valuable help.

His suggestion can be improved upon.

Calling ToList at the end is a waste of time and space.

It requests a (totally unnecessary) copy of all the results from the filtered element collector.

You can iterate over the collector itself directly.

Furthermore, a built-in Revit filter will always be faster than LINQ post-processing.

In this case, you can use a negated ElementCategoryFilter:

https://apidocs.co/apps/revit/2019/6b8f4e3a-1975-7388-3848-462cf305d523.htm

Yet further, you might gain some additional performance by deleting all the elements in one single call rather than by stepping through them one by one.

For instance, like this:

  /// <summary>
  /// Delete all non-room-separating curve elements
  /// </summary>
  void DeleteNonRoomSeparators( Document doc )
  {
    ElementCategoryFilter non_room_separator 
      = new ElementCategoryFilter( 
        BuiltInCategory.OST_RoomSeparationLines, 
        true );

    FilteredElementCollector a
      = new FilteredElementCollector( doc )
        .OfClass( typeof( CurveElement ) )
        .WherePasses( non_room_separator );

    doc.Delete( a.ToElementIds() );
  }

I added this method to The Building Coder samples for you:

https://github.com/jeremytammik/the_building_coder_samples/compare/2020.0.145.2...2020.0.145.3

I hope this helps.

Best regards,

Jeremy

Re: Deleting Lines that are not assigned to the subcateg

recepagah12 — Thu, 02 May 2019 08:43:31 GMT

Hi @jeremytammik

Thank you very much for your valuable suggestion.

Also many thanks to pointing out the wrong side of my code.

Your solution is much elegant and faster.

Thank you again,

Recep.

Re: Deleting Lines that are not assigned to the subcateg

jeremytammik — Thu, 02 May 2019 10:07:00 GMT

Edited and cleaned up here:

https://thebuildingcoder.typepad.com/blog/2019/05/location-point-and-filtering-hints.html#4