Import and allocation of spectral sound levels to point sources

Import and allocation of spectral sound levels to point sources

The import and allocation of spectral sound levels to a set of point sources in a CadnaA project can be carried out using the database functionality. In this case, two databases located within the same EXCEL book will be needed:
  1. Sound Level Databasewhich will contain the database of spectra to be imported into the local Sound Levels library.
  2. Database of point sourceswhich will refer to the sound levels of the imported library for allocation to the respective point sources of the project. It is important that the ID_SRC field contains the same value as the ID of the point sources included in the CadnaA project and that the ID_Spectr value is assigned to it.

NOTE: the parameterFREQ is the field where the dominant frequency is selected if global values have global values. But if this column has a "space" as value, it switches between "global values" > "spectrum".


Let us take an example with 2 point sources defined in a CadnaA project:

(1)Define and assign to each of the sources its corresponding ID:





2)Define databases in the same Excel. For each database, a range of data must be defined.

In this example, it is given the namePwl_datato the range of data of sound levels:


The data range of point sources is given the name(Data):


(3)Define the database to be imported into the CadnaA project throughFile/Database/Defin, sby choosing the Excel Sheet in the directory where it is located.



Then select the Object Types, by checking the "Import object type" option in both cases, select the corresponding data range using the "Table" parameter and assigning each database parameter. The allocation must be made independently for each type of object.

Point source
Select(Data)within the "Table" parameter and assign:
- Id: id_src
- LW_LI: ID_Spectr
- Freq: freq




Sound Levels
SelectDatawithin the "Table" parameter and assign:
- BEZ: Name_spectr
- ID_spectr
- BEWERT: Weighting
- STYPI: type
- SIN_31 to SIN_8000: f31 to f8k
- DISTANCE: Distance
SPHEREPART: Sphere



4) Press OK and Import databases byFile/Database/Importselect the two options that will appear:




If the configuration of each of the point sources is accessed, it can be verified that spectral levels have been imported correctly, moving from a single Band point font to a Spectre Type:



It can also be verified that all spectral sound levels have been imported into the local sound level library:






    • Related Articles

    • Change the color of buildings by exceeding sound limits

      It is common for different areas with their respective soil uses, each having sound limits for the different time intervals (Day, Afternoon and Night). For example, like the project below: To represent the building of a particular color, depending on ...

    • Import bitmap from Google Maps

      The functionality of importing maps from Google Maps is only possible by enabling the API, and Google has made it paid for a few years. Alternatively, maps can be imported from OpenStreetMap. You can see the import process in the following video: We ...

    • Import DXF files into SONarchitect

      To import a template in DXF format, you must first create a new project or have open a project in which work has begun. It will then have to be placed in the Drawing mode option and activate the "Plants" tab (where the different Plants of the ...

    • Overlap the DUT Frequency Response at different generator levels

      In this article we will explain how to simultaneously measure and visualize the frequency response of a DUT (Device Under Test) for different generator output levels of our Audio Precision analyzer. 1) After programming the Signal Path Setup within ...

    • Import insul constructive elements of Insul to SONarchitect

      To move constructive elements from Insul to SONarchitect, the following steps must be taken: 1) In Insul, please contactExport/SonArchitect(located in the top toolbar). The following window will open: 2) Define your identifier in the fieldDescriptor, ...