Prerequisites for using Maps
- Print
- PDF
Prerequisites for using Maps
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Available in Classic and VPC
Check the service support environment and usage fees for best use of Maps.
Cloud environment specifications
The following details are the cloud environment specifications supported by Maps.
| Item | Specifications |
|---|---|
| Region (zone) | Korea, U.S., Singapore, Hong Kong, Japan, and Germany |
| Platform | VPC, Classic |
| Languages | Korean, English, and Japanese |
Note
For more information on the VPC environment, see Service introduction in NAVER Cloud Platform portal. If you want to know whether the VPC environment is supported for each service, see Ncloud user environmental guide.
Service specifications
Maps API is provided in various forms of resources to support various service environments. The specifications of each resource are as follows.
Web Dynamic Map supported web browsers
Web Dynamic Map provides codes optimized for desktop and mobile environments and fully supports the major web browsers. The supported web browsers are as follows.
| Item | PC web browser compatibility | Mobile web browser compatibility |
|---|---|---|
| Core APIs |
|
|
| Submodule (Visualization) APIs |
|
|
Note
Web Dynamic Map operates without any issues even when used with any framework or library.
Mobile Dynamic Map Android SDK specifications
This section describes the specifications of the Mobile Dynamic Map Android SDK.
Operating systems and libraries
The OS version and library version supported by the Mobile Dynamic Map Android SDK are as follows.
| SDK version | Operating system version | Dependency library | Development language |
|---|---|---|---|
| Mobile Dynamic Map Android 3.x | Android 5.0 (API level 21) and above | Android Jetpack | Java, Kotlin |
SDK deployment
Mobile Dynamic Map Android SDK version 3.x is deployed from the https://repository.map.naver.com/archive/maven Maven repository. This adds a repository setting to the root project's build.gradle and declares the SDK dependency in the app module's build.gradle.
The Mobile Dynamic Map Android SDK version 3.x demo project can be downloaded from the github repository.
Changes after SDK upgrade
The following features are not available when the Mobile Dynamic Map Android SDK is upgraded from version 2.x to 3.x.
| Features | SDK 2.x | SDK 3.x |
|---|---|---|
| Reverse Geocoding | Use the coordinate-address conversion feature by calling NMapActivity.findPlacemarkAtLocation() | Reverse Geocoding not supported -> Use Reverse Geocoding REST API |
| Run NAVER Maps app button | Enable the NAVER Maps app by calling NMapView.setBuiltInAppControls() | NAVER Maps app calling not supported -> Use URL Scheme for NAVER Maps app integration |
| Marker drag | Use the marker drag feature by calling NMapPOIitem.setFloatingMode() | Marker drag is not supported -> It is recommended to fix a view that plays the role of a marker in the center of the page and move the map to specify the location. For more details, see CameraEventActivity demo |
Note
For more information on SDK upgrade, see 2.x → 3.x migration guide.
Mobile Dynamic Map iOS SDK specifications
This section describes the specifications of the Mobile Dynamic Map iOS SDK.
Operating system
The OS version supported by the Mobile Dynamic Map iOS SDK is as follows.
| SDK version | OS version | Development language |
|---|---|---|
| Mobile Dynamic Map iOS 3.x | iOS version 9 and above | Swift, Objective-C |
SDK deployment
Mobile Dynamic Map iOS SDK version 3.x is deployed from cocoapods. After installing CocoaPods, install git-lfs additionally to receive large libraries. After installing git-lfs, initialization must be performed. After completing initialization, you must update the SDK to the latest version.
Mobile Dynamic Map iOS SDK version 3.x demo project can be downloaded from the github repository.
Changes after SDK upgrade
The following features are not available when the Mobile Dynamic Map iOS SDK is upgraded from version 2.x to 3.x.
| Deprecated feature | SDK 2.x | SDK 3.x |
|---|---|---|
| Reverse Geocoding | Use coordinate-address conversion feature by calling NMapReverseGeocoder.findPlacemarkAtLocation: | Reverse Geocoding not supported -> Use Reverse Geocoding REST API |
| Run NAVER Maps app button | Enable NAVER Maps app by calling NMapView.setBuiltInAppControl: | NAVER Maps app calling not supported -> Use URL Scheme for NAVER Maps app integration |
| Marker drag | Use marker dragging feature by calling NMapPOIitem.setPOIflagMode: | Marker drag is not supported -> It is recommended to fix a view that plays the role of a marker in the center of the page and move the map to specify the location. For more details, see CameraEventActivity demo |
Note
For more information on SDK upgrade, see 2.x → 3.x migration guide.
NAVER Maps app integrating URL Scheme specifications
This section describes the specifications for using the NAVER Maps app integrating URL Scheme.
NAVER Maps app version
The NAVER Maps app integrating URL Scheme feature has been applied from the NAVER Maps app version 5. It is recommended to download the latest version from the Play Store or App Store and use it. The minimum specifications are as follows.
| Operating system | NAVER Maps app version |
|---|---|
| Android | 5 and above |
| iOS | 5 and above |
Precautions for using API
When implementing a service using the Maps API, the following precautions should be noted.
- Be careful not to arbitrarily change the names of the features and services provided by Maps. It is necessary to indicate exactly 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." - Calling the API without going through the official call path is considered as abuse, and the use of the service may be restricted.
Usage fee
Maps is providing service in a usage-based pricing plan (section pricing plan). For more details about the pricing standard for Maps, see the following page.
Was this article helpful?