OZmap

It's essential to pay attention to the mandatory information in each one of the tables when performing data importation. In this article, you can learn the specificities regarding the importation of each equipment category.

Poles

The table for importing poles has the following format: 

• Name: optional. Specifies the name of the pole. Names must be unique, or left blank so the system can automatically assign a name;
• Latitude/longitude: mandatory. Coordinates of the element's position;
• Type: optional. Specifies the type of pole. If left blank, they will be imported as "common";
• Tags: optional. Here you can insert any tag registered in your system;
• Address: optional. Allows assigning an address to the pole. It does not replace the need to fill in the coordinates.
• Licensing status: optional. Determines the licensing status of the pole. Can be “Licensed”, “In analysis”, or “Unknown”;
• Files: optional. Enables the creation of a post. To add images and other files, simply insert their URLs separated by commas in the correct column of the table.

During the importation process, the system will ask you at what distance poles should be considered duplicates. For example, if 1 meter is chosen, an imported pole will search for poles within a 1-meter distance. If found, it will not be imported as it will be considered a duplicate of the existing pole.

Boxes

The table for box import has the following format:

• Name: optional. Specifies the name of the box. If not provided, the system will create a name for the box (the name needs to be unique within the project);
• Latitude/longitude: mandatory. Coordinates of the element's position;
• Level: optional. Box level according to the Project Settings. If not filled, the box is imported as HUB;
• Type: optional. Choose a Box Type. If not filled, it will choose the default box type;
• Template: optional. You can choose a template for each Box Type. If not filled, it will choose an Empty Template for the default box type, which is an empty box;
• Deployment status: optional. Determines the deployment status. It can be Implanted, Not Implanted, or Implanted and certified. If not filled, the default is Not Implanted;
• Tags:  optional. Here you can insert any tag registered in your system;
• Files: optional. Enables the creation of a post. To add images and other files, simply insert their URLs separated by commas in the correct column of the table.
• Comments:  optional. You can add a column for observations that will be imported along with the boxes.

When initiating the import process, you will be prompted to specify the maximum distance (in meters) to search for a pole. If a pole is found within this distance, it will be used for box placement.

Subsequently, the system will proceed with importing the boxes. Boxes imported successfully will have their rows marked in green. Boxes with issues will have their rows highlighted in red and will not be imported. In this manner, an error message will indicate the issue in the "status" column.

Fields can be edited directly within the OZmap table.

Passage Box

The table for importation has the following format:

• Name: optional. Specifies the name of the passage box. If not provided, the system will create a name. The name needs to be unique within the project;

• Latitude/longitude: mandatory. Coordinates of the element's position;

• Type: optional. Choose a passage box type. If not filled, it will choose the default type;

• Deployment status: optional. Determines the deployment status. It can be Implanted, Not Implanted, or Implanted and certified. If not filled, the default is Not Implanted;

• Tags: optional. Here you can insert any tag registered in your system;

• Files: optional. Enables the creation of a post. To add images and other files, simply insert their URLs separated by commas in the correct column of the table.

• Comments: optional. You can add a column for observations that will be imported along with the passage boxes.

Cables

• Name: optional. Specifies the name of the passage box. If not provided, the system will create a name. The name needs to be unique within the project;
• Latitude/longitude: mandatory. Coordinates of the element's position;
• Type: optional. Choose a passage box type. If not filled, it will choose the default type;
• Deployment status: optional. Determines the deployment status. It can be Implanted, Not Implanted, or Implanted and certified. If not filled, the default is Not Implanted;
• Tags: optional. Here you can insert any tag registered in your system;
• Files: optional. Enables the creation of a post. To add images and other files, simply insert their URLs separated by commas in the correct column of the table.
• Comments: optional. You can add a column for observations that will be imported along with the passage boxes.

Ducts

• Name: optional. Specifies the name of the duct. If not provided, the system will create a unique name for the duct based on its ends. Remember, the name needs to be unique within the project;

• Type: mandatory. Choose a duct type;

• Points: obrigatório. mandatory. This field should contain the latitude and longitude of the passage boxes or points where the ducts pass through. Latitude_1; Longitude_1, Latitude_2; Longitude_2...

• First/second point: optional. You can choose a box for the system to search at the ends of the duct;

• Deployment status: optional. Determines the deployment status. It can be Implanted or Not Implanted. If not filled, the system will choose the default status as Implanted;

• Tags: optional. Here you can insert any tag registered in your system;

• Files: optional. Enables the creation of a post. To add images and other files, simply insert their URLs separated by commas in the correct column of the table.

• Comments: optional. You can add a column for observations that will be imported along with the ducts.

Upon initiating the import process, you will be asked to specify the maximum distance (in meters) to search for a passage box. If a passage box is found within this distance, it will be used for the placement of the duct.

Clients

• Code:  essential. If provided, the system uses the passed value as the code. If not, the system generates a code;
• Name: optional. If no code is provided, it's necessary to be filled in. Client's name;
• Box:  optional. If no pole or coordinates are provided, specifying the box name becomes mandatory to add the client. If the box name is not provided, the client will be created linked to a pole;
• Pole: optional. If provided, the system connects the client to this pole. If not provided, the system uses the same pole as the box;
• Latitude/Longitude: optional fields if a pole or box is added. If not specified, the client will be created at a random position around the pole or box;
• Address: if only the address is provided without latitude and longitude, the system will prompt for a Google API key. Thus, the system will search for the address on the map and place the client in the position returned by Google. To learn how to generate an API key, contact our support.

• Power read: optional. Allows adding the power read information for the client.

• Deployment status: optional. Determines the deployment status. Can be Not Implanted, Implanted, and Implanted and Certified. If not filled, the system will choose the default status as Not Implanted;

• Client comments: optional. Imports the client with the observations provided in this field;

• Client tags: optional. Here you can insert any tag registered in your system;

• Files: optional. Enables the creation of a post. To add images and other files, simply insert their URLs separated by commas in the correct column of the table.

• Property comments: optional. Imports the client and adds the property observations with the information provided in this field;

• Property tags: optional. Here you can insert any tag registered in your system;

• Connector: optional. Equipment to which the client is connected within the box;

• Port: optional. Port number on the equipment;
  

• Automatic connection: optional. If it’s not informed a specific splitter and port, it automatically connects to any available splitter/port in the box.

Prospects

• Name: optional. Name of the prospect;

• Code: optional. Insert a code to your prospect;
  

• Latitude/longitude: mandatory. Coordinates of the prospect;
  

• Address: optional. Allows assigning an address to the prospect. Does not replace the need to fill in the coordinates.
  

• Tags: optional. Here you can insert any tag registered in your system;
  

• Comments: optional. Additional observations about the prospect.

Vertical Condominiums (Buildings)

• Name: optional. If not provided, the system will create a unique name for the building. Remember, the name needs to be unique;
• Latitude/Longitude: you will need to provide the coordinates of the building if the address is not provided;
• Deployment status: optional. Determines the deployment status. Can be implanted or not implanted. If not filled, the system will choose the default status as not implanted;
• Address: optional. Allows assigning an address to the building. Does not replace the need to fill in the coordinates.
• Files: optional. Enables the creation of a post. To add images and other files, simply insert their URLs separated by commas in the correct column of the table.
• Comments: additional information about the building.

Horizontal Condominiums

• Name: optional. Specify the name of the region. This must not be repeated, and if the field is left empty, a name will be generated automatically;
• Polygon: mandatory. Defines the area of your region. As per the table above, it should have dots as delimiters and commas between latitude and longitude;
• Address:  optional. Allows assigning an address to the region. It does not replace the need to fill in the coordinates.
• Color: optional. You can import a color with your region or let it be imported with the default color;
• Comments: optional. Additional information about the region.
• Tags: optional. Here you can insert any tag registered in your system;

POP (COs)

• Name: optional. If not provided, the system will create a unique name for the POP. Remember, the name needs to be unique;

• Type: optional. If not informed, the POP will be created as the type "Common".
  

• Level:  optional. If not informed, it is created with the level "Primary".
  

• Latitude/longitude: mandatory. Coordinates of the POP.
  

• Deployment status: optional. Determines the deployment status. It can be In project, not implanted, implanted, or implanted and certified. If not provided, it will be imported as not implanted;
  

• Tags: Tags provided in the system. It's additional information;
  

• Files: optional. Enables the creation of a post. To add images and other files, simply insert their URLs separated by commas in the correct column of the table.
  

• Comments: optional. additional information about the POP.

Spare/ Technical Reserve

• Pole: mandatory. The pole to which the reservation will be added. It can be either a name or coordinates;
• Reserve: mandatory. Quantity of reserve to be imported, given in meters;
• Cable: optional. Name of the cable if there are multiple cables on the pole. If you do not provide this information, the system will choose a random cable passing through the indicated pole.

Regions

• Name: optional. Determines the name of the region. This cannot be repeated, if the field is empty, a name will be generated automatically;
  
  
• Polygon: mandatory. Defines the area of your region. As per the table above, it should have point and comma delimiters followed by a comma between latitude and longitude.
  
• Type: optional. Choose a type for your region.
• Color: optional. You can import a color with your region or let it be imported according to the color of your type.
• Comments: Optional. Additional information about the region.
• Tags: Optional. Here you can insert a tag registered in your system.

Right below, we listed some example files for the importation.