Skip to main content

Maps

Introduction​

Map based solutions are a popular option to help customers understand where they can get products and services from.

Essity usage is mainly around the "Dealer Locator" use case, where a map is embedded in a webpage, offering the user the functionality to find the physical locations of Essity partners, retailers etc.

Introduction to Maps

Users are, today, very familiar with mapping techonology in multiple settings.

For Essity, the most common use case is a "Dealer Locator" map embedded in a webpage. Essity's preferred solution is to use Google Maps (https://developers.google.com/maps) APIs, which in general features:

Google Maps APIs are a set of tools and services provided by Google that allow developers to access and integrate Google Maps data into their web and mobile applications. These APIs enable the creation of interactive maps, geolocation services, and geographic data visualizations, making them essential for businesses and developers seeking to enhance user experiences with location-based information.

Key Features of Google Maps APIs​

  • Maps JavaScript API: Allows web developers to embed interactive Google Maps into web pages, offering features like custom map styling, markers, and Street View panoramas[3][4].
  • Places API: Provides detailed information about millions of places worldwide, including names, addresses, and user ratings[6][8].
  • Directions API: Calculates directions and optimizes routes for various modes of transportation, including real-time traffic data[6][9].

Use Cases on Websites​

  1. Interactive Maps Embedding: Embedding interactive maps into websites and mobile apps to provide location-based information, such as store locators or travel itineraries[2][3].

  2. Geocoding and Address Validation: Converting addresses into geographic coordinates for location-based searches or validating addresses for delivery services[6].

  3. Route Optimization: Using the Directions API to optimize routes for logistics companies, enhancing delivery efficiency and reducing costs[5][6].

  4. Location-Based Content: Displaying location-specific content, such as weather updates or local news, by accessing a user's location[2].

  5. Real Estate and Tourism: Utilizing Street View imagery to offer immersive experiences for real estate listings or tourism websites[2][5].

  6. Data Visualization: Overlaying custom data on maps to visualize geographic information like sales territories or population density[2].

These use cases demonstrate how Google Maps APIs can enhance user engagement and provide valuable insights for businesses across various industries.

Citations: [1] https://blog.hubspot.com/website/google-maps-api [2] https://promevo.com/blog/google-maps-api [3] https://devhunt.org/blog/google-map-api-for-developers-integration-basics [4] https://www.youtube.com/watch?v=kA679ERgBV4 [5] https://ubilabs.com/en/google-maps/integration-for-companies [6] https://sada.com/topics/google-maps-platform/ [7] https://ubilabs.com/en/google-maps/api-sdk [8] https://developers.google.com/maps/documentation/places/web-service/overview [9] https://developers.google.com/maps/documentation

Engagement​

Reach out to the Digtial Marketing Platform Team

Review and Approval​

With the help of the Digital Marketing Platform Team:

  • Firstly, check if the map requirement has not already been met to some extent. It is already common functionality, so an existing solution is likely to be resuable.
  • Secondly, have some understanding what kind of consumption is expected, with two areas of consideration
    • the expected volume of users of the solution
    • the expected API usage based on the functionality involved

These then form the basic inputs for review and approval, which should be considered in two stages

  • First, reach out and have the early discussion to help define the best solution
  • Second, with a defined solution (business usage, expected user experience, anticpated API consumption, architecture outline etc.), agreement should be reached to use the APIs and then keys are provisioned.
warning

Poor implementations can rapidly consume expensive APIs, leading to price spikes. These are easily avoidable, and that is what the review is aiming to achieve more than anything else.

Standards and Conventions​

Google Maps (https://developers.google.com/maps) comes with a portfolio of mapping solutions covering a wide range of use cases.

The use cases are split into four categories; maps, routes, places and environment as per the documentation (https://developers.google.com/maps/documentation).

The dealer locator scenario mainly requires only the Maps APIs & SDKs for viewing, plus minor use of the Places APIs & SDKs to geolocating dealer addresses.

(At the time of writing) any other usage would be considered non-standard, and require dicussion/exception to continue.

Architecture and Design​

REFERENCE DESIGN REQUIRED

Implementation​

Pre-requisites​

  • Defined solution (from eariler phases)
  • (rate restricted/quota'ed) non-production APIs keys
    • HTTP Referer (client)
    • IP Whitelist (server)
info

Non-production API keys come with quotas, designed to catch any implementation errors which would otherwise lead to excessive usage.

Development​

Testing​

Deployment​

Operations and Support​