Mapmyindia REST API SDK for React Native - beta

Easy To Integrate Maps & Location APIs & SDKs For Web & Mobile Applications

Powered with India's most comprehensive and robust mapping functionalities.

Now Available for Srilanka, Nepal, Bhutan and Bangladesh

1. For full documentation contact MapmyIndia here:

Email: apisupport@mapmyindia.com.

2. You can get your api key to be used in this document here: https://www.mapmyindia.com/api/signup

Mapmyindia is the location data platform for mobile and web applications. We provide building blocks to add location features like maps, search, and navigation into any experience you create. Use our simple and powerful APIs & SDKs for interactivity and control.

Not a Mapmyindia user yet? Sign up for an account here. Once you’re signed in, all you need to start building is a Mapmyindia key. Use this same short code with all of our interactive mapping libraries, JavaScript SDKs, and directly against our REST APIs. You can create and manage your access tokens on your Mapmyindia Account page.

Your MapmyIndia Maps SDK usage needs a set of license keys (get them here ) and is governed by the API terms and conditions.

As part of the terms and conditions, you cannot remove or hide the MapmyIndia logo and copyright information in your project.

Please see branding guidelines on MapmyIndia website for more details.

The allowed SDK hits are described on the plans page. Note that your usage is

shared between platforms, so the API hits you make from a web application, Android app or an iOS app all add up to your allowed daily limit.

$ npm install mapmyindia-restapi-react-native-beta --save

If you are using React-Native < 0.60.0 then you have to follow additional steps which are below

$ react-native link mapmyindia-restapi-react-native-beta

1. In XCode, in the project navigator, right click Libraries ➜ Add Files to [your project's name]

2. Go to nodemodules ➜ mapmyindia-restapi-react-native-beta and add RNRestapi.xcodeproj

3. In XCode, in the project navigator, select your project. Add libRNRestapi.a to your project's Build Phases ➜ Link Binary With Libraries

4. Run your project (Cmd+R)<

1. Open up android/app/src/main/java/[...]/MainActivity.java

• Add import com.restapi.reactnative.RNRestapiPackage; to the imports at the top of the file

• Add new RNRestapiPackage() to the list returned by the getPackages() method

2. Append the following lines to android/settings.gradle:

3. Insert the following lines inside the dependencies block in android/app/build.gradle:

• Atlas AutoSuggest

• Distance Matrix ETA

The Place detail API is to extract the details of a place with the help of its eLoc i.e. a 6 character code. Since a place may or may not have additional attributes associated with it, the response from the place details may be different for each record. However the response will be an extract from an existing set of master key-value pairs grouped as objects.

##### a. Mandatory Parameters:

1. eLoc: the id or eLoc of the place whose details are required. The 6-digit alphanumeric code for any location. (e.g. mmi000). 2. response : successcallback of api call

The API is highly configurable to configuration enables to provide the required set of attributes to the user on the basis of assigned sub templates. The default configuration with available with basic pay-as-you-go rates is that of General Details subtemplate.

The parameters are group in sub templates. Here is the list of attributes with sub template information.

1. Eloc (string) : 6 characters alphanumeric unique identifier 2. placeName (string) : Name of the place 3. address (string) : address of the place 4. type: defines the type of location matched (HOUSENUMBER, HOUSENAME, POI, STREET, SUBLOCALITY, LOCALITY, VILLAGE, DISTRICT, SUBDISTRICT, CITY, STATE, SUBSUBLOCALITY, PINCODE)

1. city (string): The name of the city in which the location exists. 2. district (string): The name of the district in which the location exists. 3. pincode (string): The pin code of the location area. 4. subDistrict (string): The name of the sub-district in which the location exists. 5. state (string): The name of the state in which the location exists.

1. houseNumber (string): The house number of the location. 2. houseName (string): The name of the location. 3. locality (string): The name of the locality where the location exists. 4. street (string): The name of the street of the location. 5. subSubLocality (string): The name of the sub-sub-locality where the location exists. 6. subLocality (string): The name of the sub-locality where the location exists. 7. village (string): The name of the village if the location exists in a village. 8. poi (string): The name of the POI if the location is a place of interest (POI).

1. Email 2. Mobile 3. Telephone 4. Website

1. latitude(double): The latitude of the location. 2. longitude(double): The longitude of the location.

1. Entrylat(double):The entry latitude of the location. 2. Entrylon(double):The entry longitude of the location.

##### a. Mandatory Parameters: 1. query (string) e.g. Shoes, Coffee, Versace, Gucci, H&M, Adidas, Starbucks, B130 {POI, House Number, keyword, tag} 2. response : successcallback of api call

##### b. Optional Parameters:

1. location {string (latitude[double],longitude[double])} e.g. location=28.454,77.435 2. zoom (double) = takes the zoom level of the current scope of the map (min: 4, max: 18). 4. tokenizeAddress (boolean) = provides the different address attributes in a structured object. 5. pod (string) = it takes in the place type code which helps in restricting the results to certain chosen type. Below mentioned are the codes for the pod - 1. SLC: Sublocality 2. LC: Locality 3. CITY: City 4. VLG: Village 5. SDIST: Subdistrict 6. DIST: District 7. STATE: State 8. SSLC: Subsublocality 6. filter = this parameter helps you restrict the result either by mentioning a bounded area or to certain eloc (6 digit code to any poi, locality, city, etc.), below mentioned are the both types - a. filter = bounds: lat1, lng1; lat2, lng2 (latitude, longitude) {e.g. filter=bounds: 28.598882, 77.212407; 28.467375, 77.353

##### a. Mandatory Parameters:

1. keywords (string) e.g. FODCOF, Shoes, Coffee, Versace, Gucci, H&M, Adidas, Starbucks, B130 {POI, House Number, keyword, tag} 2. refLocation {string (latitude[double],longitude[double])}: Provides the location around which the search will be performed. It also supports Eloc. E.g. refLocation=28.454,77.435 or refLocation="MMI000" 4. response : successcallback of api call

##### b. Optional Parameters: 1. page (integer): provides number of the page to provide results from. 2. sort (string): provides configured sorting operations for the client on cloud. Below are the available sorts: a) dist:asc & dist:desc - will sort data in order of distance from the passed location (default). b) name:asc & name:desc - will sort the data on alphabetically bases. 3. radius (integer): provides the range of distance to search over (default: 1000, min: 500, max: 10000). 4. bounds (string) : Allows the developer to send in map bounds to provide a nearby search within the bounds. {e.g. (bounds("28.56812,77.240519;28.532790,77.290854")) 5. filter (string) : This parameter helps you get a specific type of EV charging Station - filter = model:(string);brandId:(string);plugType:(string)

##### a. Mandatory Parameters: 1. lat:(double) the latitude of the location for which the address is required. 2. lng:(double) the longitude of the location for which address is required. 3. response : successcallback of api call

##### a. Mandatory Parameters:

1. address(string) address to be geocoded e.g. 237 Okhla industrial estate phase 3 new delhi, delhi 110020 2. response : successcallback of api call

##### b. Optional Parameters: 1. itemCount (integer): parameter can be set to get maximum number of result items from the API (default: 1). 2. bias (integer): This parameter can be used to set Urban or Rural bias. A positive value sets the Urban bias and a negative value sets Rural bias. Allowed values are: - 0 : Default: (No bias) - -1 : Rural - 1 : Urban 3. podFilter (string): This parameter can be used to set admin level restriction. The result will be either the given admin level or equivalent admin or higher in the hierarchy. No lower admin will be considered for geocoding. Allowed values are: - hno : house number - hna : house name - poi : point of interest - street : street - sslc : sub sub locality - village : village - slc : sub locality - sdist : sub district - loc : locality - city : city - dist : district - pincode :pincode - state : state 4. bound (string): This parameter ca

Note: Please note that podFilter & bound parameters are mutually exclusive. They cannot be used together in an API call.

##### a. Mandatory Parameters: 1. source:{string (longitude[double],latitude[double])} 2. destination: is pair of comma separated longitude & latitude value.Last coordinate will be considered as end point (mandatory) and those in between are via points (optional). Example: {longitude},{latitude};{longitude},{latitude} 3. response : successcallback of api call ##### b. Optional Parameters: 1. geometries(string): This parameter used to change the route geometry format/density (influences overview and per step). Default value is - polyline with 5 digit precision; - polyline6 for 6 digit precision; - geojson for geometries as geojson. 2. steps(boolean): Return route steps for each route leg. Possible values are true/false. By default it will be used as false. 3. exclude(string): Additive list of road classes to avoid, order does not matter. Possible values are toll, motorway & ferry. Multipl