Google Places API vs OpenLayers

Need advice about which tool to choose?Ask the StackShare community!

Google Places API

68
87
+ 1
0
OpenLayers

389
397
+ 1
50
Add tool

Google Places API vs OpenLayers: What are the differences?

Developers describe Google Places API as "Help users discover the world with rich details for points of interest". You can provide users data on location names, addresses, ratings, reviews, contact information, and atmosphere. Local guides and users submit tens of millions of updates every day, so you can count on accurate, reliable information. On the other hand, OpenLayers is detailed as "A high-performance, feature-packed library for all your mapping needs". An opensource javascript library to load, display and render maps from multiple sources on web pages.

Google Places API and OpenLayers can be primarily classified as "Mapping APIs" tools.

OpenLayers is an open source tool with 5.31K GitHub stars and 1.99K GitHub forks. Here's a link to OpenLayers's open source repository on GitHub.

According to the StackShare community, OpenLayers has a broader approval, being mentioned in 12 company stacks & 43 developers stacks; compared to Google Places API, which is listed in 12 company stacks and 5 developer stacks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Google Places API
Pros of OpenLayers
    Be the first to leave a pro
    • 13
      Flexibility
    • 10
      Maturity
    • 7
      Incredibly comprehensive, excellent support
    • 7
      Open Source
    • 4
      Choice of map providers
    • 3
      Low Level API
    • 3
      Extensible
    • 3
      Strong community

    Sign up to add or upvote prosMake informed product decisions

    What is Google Places API?

    You can provide users data on location names, addresses, ratings, reviews, contact information, and atmosphere. Local guides and users submit tens of millions of updates every day, so you can count on accurate, reliable information.

    What is OpenLayers?

    An opensource javascript library to load, display and render maps from multiple sources on web pages.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention Google Places API and OpenLayers as a desired skillset
    CBRE
    United States of America Texas Houston
    CBRE
    United States of America Texas Austin
    CBRE
    United States of America Pennsylvania Radnor
    CBRE
    United States of America Ohio Cleveland
    CBRE
    United Kingdom of Great Britain and Northern Ireland England London
    What companies use Google Places API?
    What companies use OpenLayers?
    See which teams inside your own company are using Google Places API or OpenLayers.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What are some alternatives to Google Places API and OpenLayers?
    Google Maps
    Create rich applications and stunning visualisations of your data, leveraging the comprehensiveness, accuracy, and usability of Google Maps and a modern web platform that scales as you grow.
    TomTom
    It is the leading independent location technology specialist, shaping mobility with highly accurate maps, navigation, real-time traffic info and services.
    Leaflet
    Leaflet is an open source JavaScript library for mobile-friendly interactive maps. It is developed by Vladimir Agafonkin of MapBox with a team of dedicated contributors. Weighing just about 30 KB of gzipped JS code, it has all the features most developers ever need for online maps.
    Mapbox
    We make it possible to pin travel spots on Pinterest, find restaurants on Foursquare, and visualize data on GitHub.
    OpenStreetMap
    OpenStreetMap is built by a community of mappers that contribute and maintain data about roads, trails, cafés, railway stations, and much more, all over the world.
    See all alternatives