- Print
- PDF
Maps scenarios
- Print
- PDF
Available in Classic and VPC
You can easily implement NAVER Maps using the Maps API provided by the NAVER Cloud Platform. You can view the detailed usage methods in Getting started with Maps and Using Maps, but we recommend taking a look at the overall usage scenario of Maps first. Reading the guide after learning the usage scenario will allow you to use Maps more smoothly. The overall sequence of using Maps and description of each sequence are as follows:
1. Setting user permissions
2. Issuing authentication key
3. Setting project
4. Applying authentication key
5. Using API
6. Viewing usage
1. Setting user permissions
If several users need to manage and share Maps, you can operate it by setting permissions for each user. User-specific permissions can be composed of administrator and user permissions through the Sub Account of the NAVER Cloud Platform, and roles can be defined for each permission.
Since setting permissions is not mandatory, you can set or unset it at any time when you need permissions while using Maps.
Sub Account is a service provided free of charge upon subscription request. For an introduction on Sub Account and details about its pricing plans, refer to the Services > Management & Governance > Sub Account menu in the NAVER Cloud Platform portal.
You can refer to the following guide:
2. Issuing authentication key
To use Maps, you must first register an application on the NAVER Cloud Platform console and get an authentication key. Maps belong to the AI·NAVER API > Application Service. The Maps APIs that can be registered include Web Dynamic Map, Mobile Dynamic Map, Static Map, Directions 5, Directions 15, Geocoding, Reverse Geocoding. All APIs can be registered in 1 application, or each API can be registered as an individual application. Guides that can be referred to in relation to application registration are as follows:
3. Setting project
To use the Maps API, you must load the Maps API resources provided by the NAVER Cloud Platform into your development project file, or add dependencies to the resources and libraries. As the way to set up a project differs for each development resource, see the start guide for each resource. Maps REST API can be used without separate settings. Guides that can be referred to in relation to project settings are as follows:
- Getting started with Web Dynamic Map
- Getting started with Mobile Dynamic Map Android
- Getting started with Mobile Dynamic Map iOS
Since the submodules of the Web Dynamic Map are separate libraries from the Web Dynamic Map core API, you must load the submodules using submodules
URL parameters to use them. To load a submodule, the Web Dynamic Map API must be loaded first. The following explains the submodules provided by the Web Dynamic Map:
- panorama: provides street view/aerial view.
- geocoder: provides transformation methods between coordinate systems and extended projection objects that support specific coordinate systems.
- drawing: provides drawing tools that can draw polygons, rectangles, polylines, circles, and markers on the map.
- visualization: provides heat maps and dot maps to easily understand data with geographical information.
4. Applying authentication key
You must apply the authentication key (Client ID, Client Secret), issued through the application registration according to the 2. Subscribe to Maps procedure, to your development project. That is, you can use the Maps API by applying the issued authentication key to the settings file of your development project. For Maps REST API, enter the authentication key in the header. As the way to apply the authentication key varies for each development resource, see the start guide for each resource. You can refer to the following guides:
- Getting started with Web Dynamic Map API
- Getting started with Mobile Dynamic Map Android
- Getting started with Mobile Dynamic Map iOS
- Static Map overview
- Directions 5 overview
- Directions 15 overview
- Geocoding overview
- Reverse Geocoding overview
Make sure the client ID and client secret are kept confidential. If security is a concern, reissue a new value. Check the procedure for reissuing the authentication key in Viewing application information.
5. Using API
You can implement the NAVER Maps service using the classes and libraries provided by the NAVER Cloud Platform Maps API. You start by creating a map object and reserving a place to display the map. For the detailed implementation method, you should refer to the development guide for each development resource. You can refer to the following development guides:
- Developing Web Dynamic Map
- Developing Mobile Dynamic Map Android
- Developing Mobile Dynamic Map iOS
- Static Map API specifications
- Directions 5 API specifications
- Directions 15 API specifications
- Geocoding API specifications
- Reverse Geocoding API specifications
When implementing a service using the Maps API, you cannot arbitrarily change the features and service names provided by NAVER Maps, and you must indicate the same as the names guided in this guide (street view, directions, navigation, satellite map, cadastral map, map search, public transportation, real-time traffic, and so on).
<example> If a customer uses the Web Dynamic Map to show "street view," it cannot be changed and indicated as "entrance view" or "road view".
6. Viewing usage
View the usage of the Maps API on the NAVER Cloud Platform console. Since you are charged when exceeding a certain usage amount, you should manage the usage of Maps by setting a usage limit or by notifying when exceeding the limit. You can refer to the following guide: