#DicasOZmap | Google API

Google APIs are sets of programming interfaces designed to provide integration with services and extend the functionality of third-party systems. How about getting to know her better and learning how she can help in your daily life?

It is important to say that each API has a functionality, here at OZmap we use the following Google APIs in our requests:

  • Maps JavaScript API – provides site maps with images and local data.
  • Geocoding API – converts addresses to geographic coordinates (geocoding) and geographic coordinates to addresses (reverse geocoding).
  • Places API – provides data from over 100 million points of interest.
  • Elevation API – provides query of all locations on the earth's surface allowing calculation of elevation change along the route.

Each one of them must be selected when you generate your key and to learn how to do this just click here.

But then, what do we use all this for?

The Google API can be used in different ways within OZmap, the main ones are:

OTDR CALCULATION

You have probably already seen the “Consider relief” option when doing the OTDR calculation, it is just below the field to enter the distance and raises a lot of doubts. Basically, this functionality uses the Google API to make a more accurate calculation of the distance, based on information about the relief of the region to pinpoint the location with precision.

In addition, this calculation will also return a graph of elevation of the result obtained, showing how much was the elevation at each of the points covered.

To learn more about the OTDR feature, click here.

CABLE LENGTH

Similar to the relief-based measurement feature of the OTDR, it is also possible to calculate the cable length using the relief of the region it is passing through. To do this, just access the properties of your cable and go to the button “Assign distance with relief”, similar to the image below.

By clicking on it, the button will be replaced by the actual cable length calculation, calculated based on the relief of the region and will assign this value to the “3D Length” field.

In this case there is little difference because it is a flatter area, however it is very practical to obtain real data in locations with large differences in elevation.

IMPORT CUSTOMERS WITH ADDRESS

You might be surprised at how easy it is to import customers with just the address in your CSV file. In this case, it will be mandatory to have only two columns, the “code”/”name” and “address”, as shown in the following image:

As soon as the command to import is given, with the document inserted in the data import area, a window like the one in the image below will open, asking for the API key, if you don't already have it saved in your settings. If the key has already been registered, the import will proceed normally, using the address to position the customers.

For more information on how to import data into your OZmap, click here.

REALLOCATING CUSTOMERS IN BATCH

This functionality exists so that you can confirm that customers are in the correct location according to the registered address, the system uses Google Maps data to locate the property's address and relocates it in the corresponding coordinates to that point.

To relocate customers in batches, simply generate an area (if you don't know how to do this, click here), go to the "customers" tab, select "tools" and then "allocate by address".

A small window will open with the allocation options where it is necessary to inform the maximum distance of the allocation, which is very important, because if the address entered is incorrect, the client may be moved to a location very far away or outside its project area. . If the distance exceeds the past value the property will not be relocated, so pay close attention!

There is also the option to assign to the nearest pole after allocation, if this option is checked, the system will search for poles according to the maximum distance to search and connect the customer, updating the drop path automatically.

It is important to note that the API key is only requested when the allocation of clients is done in batch, if it is done only in one property, no key will be requested, check out more details about this in our article: Customers.

ASSIGN ADDRESS TO POSTS

If poles are very active elements in your network, you'll be glad to hear that. In OZmap there is a small button, which through the coordinates of the pole, is able to find the address and fill it for you!

If you want to assign the address of the poles in batch it is also possible through the area report:

And now that you know which functions we were able to enable with the Google API key, how about generating yours?

If you want to know more about OZMap, check out the tutorials on our channel!