Names: placeholder, missing and overly long names
Summary
Every object in an IFC file has a name. It is the first thing a person sees in a viewer, a schedule, a maintenance system or a search result, and often the only thing they read before deciding whether this is the pump, the bearing or the fire door they are looking for.
The report checks names in two ways on the Consistency page. Placeholder or missing names counts elements whose name says nothing: empty, only a number, or only the name of the IFC class. Overly long / symbol-heavy names counts names that have grown into strings of export parameters, codes or URL-encoded characters that no person can read.
Neither check judges whether names follow your naming convention; the report does not know it. They catch the names that are clearly unusable for anyone.
Where you see it in the report
| Place | What it shows |
|---|---|
| Consistency page, checks Placeholder or missing names and Overly long / symbol-heavy names | For example 42 (1.3%) placeholder names and 0 overly long / symbol-heavy names. |
| Consistency page, card Naming | The share of elements that are named and that carry a placeholder, the counts behind both checks, and the share of unique names. |
| Consistency page, card Overly long and symbol-heavy names | Shown when there are any: examples with their length and what makes them hard to read, such as 148 chars (>100), 3 URL-encoded tokens (e.g. %20). |
| In short page, It’s an IFC file, but is the content any good? | Placeholder names can appear among the facts behind the Defined answer. |
| Potential page | The action of each check that scores below 80, with the points it would add to Overall quality. |
Placeholder or missing names
An element counts as having a placeholder or missing name when its name is:
- empty;
- only a number, such as 12 or 3.5;
- only the name of its IFC class, with or without “Ifc”, in any case: a wall named IfcWall or Wall, a beam named beam.
All elements are counted except openings; spaces, storeys and the other parts of the spatial structure are not. A name such as Wall 1 or Basic Wall:Generic - 200mm is not a placeholder by this rule: it is weak, but it says something.
The score is 100 minus 5 points for every 1% of elements with a placeholder or missing name, so 4% gives 80 and 20% or more gives 0. The check has a weight of 1 and belongs to the Consistency dimension. The action in the report is Replace default names with a naming convention.
Unique names
The Naming card also shows the share of unique names: the number of different names divided by the number of named elements. It is not scored. A low share is normal when names describe the type (Wall 300mm) rather than the individual object, and it says nothing bad about the model. Where each object needs its own identifier, such as a pump number or a door number, IFC has a separate attribute for it, the tag, and many owners ask for a unique tag rather than a unique name.
Overly long / symbol-heavy names
A name counts as overly long or symbol-heavy when it is longer than 100 characters and also has at least one of these:
- URL-encoded characters, such as %20 for a space;
- 10 or more symbols: anything other than the letters A to Z, digits and spaces, so accented letters count as symbols too;
- symbols making up 15% or more of the name.
Such names usually come from an export that glues parameters together (family, type, size, phase, an internal ID), from a conversion that encodes characters it does not understand, or from a script that writes a whole description into the name. Elements are counted, and so are the project, sites, storeys, spaces and facilities.
The score is 100 when there are none. Any such name brings it down to 50 at most, minus 2 points for every 1% that the number of such names makes up of the number of elements, down to 0 at a quarter or more. The check has a weight of 1 and belongs to the Consistency dimension. The action in the report is Clean up concatenated parameters, type definitions, and URL-encoded characters in object names.
The checks at a glance
| Check | Score | Weight |
|---|---|---|
| Placeholder or missing names (Consistency) | 100 minus 5 × the percentage of elements with a placeholder or missing name, down to 0. | 1 |
| Overly long / symbol-heavy names (Consistency) | 100 with none; with any, 50 minus 2 × the percentage affected, down to 0. | 1 |
Consistency checks count for three quarters in the Overall quality score. The full list of checks is in What we check.
Why names matter in operation
- People search by name. A technician looking for a valve, or an asset manager filtering a list, types a word. Objects called IfcFlowController or 17 can only be found by opening each one.
- Systems copy the name. Asset registers and maintenance systems usually take the object name as the description of the asset. A placeholder name becomes a placeholder description in every work order.
- Long names break lists. Schedules, labels and mobile screens cut off long names, so the part that tells two objects apart may never be shown. Encoded characters (%20) make names hard to read and to search.
How to fix it
- Agree on a naming convention for objects in the information requirements, and say which attribute holds what: a readable name, a unique tag, and the type for the product description.
- Ask the author to fill names in the authoring tool, or to map a meaningful parameter to the IFC name in the export settings, instead of the default.
- For long names, map only the parameters that a person needs to the name, and put the rest in properties, where they stay searchable without cluttering the name.
Upload the corrected file with Examine a model to see the effect.
Frequently asked questions
Many of my objects share the same name. Is that a problem?
Not for these checks. Shared names are normal when names describe the type. Use the tag when each object needs its own identifier.
Does the report check our naming convention?
No. It only catches names that are empty, a bare number, the class name, or overly long and symbol-heavy. Whether names follow your convention needs your convention.
Why are spaces not counted for placeholder names?
The placeholder check counts elements: walls, pumps, beams and the like. Spaces, storeys and the rest of the spatial structure are not elements in IFC, so a room named only 1.04 is not marked down. The long-name check does include them.