collapse

Welcome!



Welcome to Robot Rebels, an online robot maker community.

Register today to post your projects, ask questions, share knowledge and meet like-minded people from around the world.


The RobotRebel.org Community

Author Topic: Google Vision API using Raspberry Pi and Node  (Read 3050 times)

Ladvien

  • Alabtu-ian Refugee
  • Member
  • *
  • Posts: 57
Google Vision API using Raspberry Pi and Node
« on: April 20, 2018, 02:38:12 PM »
Google Vision API using Raspberry Pi and Node

This is a jumpstart guide to connecting a Raspberry Pi Zero W to the Google Vision API.

1. Get an Account
Sadly, Google Vision API is not a completely free service.  At the time of writing an API account provides 1000 free Google Vision API calls a month.  Then, it's a $1.00 for each 1000 calls.

I know, I know, not too bad.  But this isn't a commercial project.  I'm wanting to use it for a puttering little house bot.  If my wife gets a bill for $40 because I decided to stream images to the API, well, it'll be a dead bot. Anyway, I thought I'd still explore the service for poo-and-giggles.

To get an account visit

* Google Console

And sign-in with an existing Google account or create one.

2. Enter Billing Information
Now, here's the scary part, you've must enter your billing information before getting going.  Remember, you will be charged if you go over 1000 calls.



Again, if you exceed your 1,000 free calls you will be charged. (What? I said that already? Oh.)

2. Enable Cloud Vision API
After setting up billing information we still need to enable the Cloud Vision API.  This is a security feature, essentially, all Google APIs are disabled by default so if someone accidentally gets access they don't unleash hell everywhere.




Now search for [code single]Vision[/code] and click the button.  Here there should be a glaring [code single]Enable[/code] button.  Press it.




The last thing we need to do is get the API key.  This needs to be included in the API call headers for authentication.

Do not let anyone get your API key. And do not hardcode it in your code.  Trust me, this will bite you.  If this accidentally gets pushed onto the web, a web crawler will find it quickly and you will be paying bajillions of dollars.

Let this article scare you a bit.

* Dev Puts AWS Keys on Github

Let's go get your API Key.  Find the [code single]Credentials[/code] section



You probably wont see any credentials created, as you've probably have not created any yet.

Let's create a new API Key.


I'd name the key something meaningful and limit it to only the Google Cloud API.



Go ahead and copy your API key, as we will need it in the next step.

3. Raspberry Pi Side Setup
The articles listed at the top of this one will help you setup the Raspberry Pi for this step.  But if you are doing things different, most of this should still work for you.  However, when we get to the part of about environment variables, that'll be different for other Linux flavors.

Start by SSH'ing into your Pi.

And update all packages
Code: [Select]
sudo pacman -SyuWe're going to create an environment variable for the Google Cloud Vision API.  This is to avoid hardcoding your API key into the code further down.  _That will work_, but I highly recommend you stick with me and setup an environment variable manager to handle the API.

Switch to the root user by typing
Code: [Select]
suEnter your password.

The next thing we do is add your Google Vision API Key as an environment variable to the [code single]/etc/profile[/code] file, this should cause it to be intialized at boot.

Type, replacing [code single]YOUR_API_KEY[/code] with your actual API Key.
Code: [Select]
echo 'export GOOGLE_CLOUD_VISION_API_KEY=YOUR_API_KEY' >> /etc/profileNow reboot the Pi so that takes effect.

Code: [Select]
sudo rebootLog back in.  Let's check to make sure it's loading the API key.
Code: [Select]
echo $GOOGLE_CLOUD_VISION_API_KEYIf your API key is echoed back, you should be good to go.

4. Project Setup

Let's create a project directory.

Code: [Select]
mkdir google-vis
cd google-vis
Now let's initialize a new Node project.
Code: [Select]
npm initFeel free to customize the package details if you like.  If you're lazy like me, hit enter until you are back to the command prompt.

Let's add the needed Node libraries.  It's one.  The axios library, which enables async web requests.

Code: [Select]
npm axios
Also, let's create a resource directory and download our lovely test image.  Ah, miss Hepburn!

Make sure you are in the [code single]google-vis/resources[/code] project directory when downloading the image.
Code: [Select]
mkdir resources
cd resources
wget https://ladvien.com/images/hepburn.png

5. NodeJS Code

Create a file in the [code single]go-vis[/code] directory called [code single]app.js[/code]

Code: [Select]
nano app.jsThen paste in the code below and save the file by typing CTRL+O and exiting using CTRL+X.

Code: [Select]
// https://console.cloud.google.com/
const axios = require('axios');
const fs = require('fs');

const API_KEY = process.env.GOOGLE_CLOUD_VISION_API_KEY

if (!API_KEY) {
  console.log('No API key provided')
}

function base64_encode(file) {
    // read binary data
    var bitmap = fs.readFileSync(file);
    // convert binary data to base64 encoded string
    return new Buffer(bitmap).toString('base64');
}
var base64str = base64_encode('./resources/audrey.jpg');

const apiCall = `https://vision.googleapis.com/v1/images:annotate?key=${API_KEY}`;

const reqObj = {
    requests:[
        {
          "image":{
            "content": base64str
          },
          "features":[
                {
                    "type":"LABEL_DETECTION",
                    "maxResults":5
                },
                {
                    "type":"FACE_DETECTION",
                    "maxResults":5           
                },
                {
                    "type": "IMAGE_PROPERTIES",
                    "maxResults":5
                }
            ]
        }
      ]
}

axios.post(apiCall, reqObj).then((response) => {
    console.log(response);
    console.log(JSON.stringify(response.data.responses, undefined, 4));
}).catch((e) => {
    console.log(e.response);
});

This code grabs the API key environment variable and creates a program constant from it.

Code: [Select]
const API_KEY = process.env.GOOGLE_CLOUD_VISION_API_KEYThis is how we avoid hardcoding the API key.

6. Run
Let's run the program.

Code: [Select]
node app.jsIf all went well you should get similar output to below

Code: [Select]
data: { responses: [ [Object] ] } }
[
    {
        "labelAnnotations": [
            {
                "mid": "/m/03q69",
                "description": "hair",
                "score": 0.9775374,
                "topicality": 0.9775374
            },
            {
                "mid": "/m/027n3_",
                "description": "eyebrow",
                "score": 0.90340185,
                "topicality": 0.90340185
            },
            {
                "mid": "/m/01ntw3",
                "description": "human hair color",
                "score": 0.8986981,
                "topicality": 0.8986981
            },
            {
                "mid": "/m/0ds4x",
                "description": "hairstyle",
                "score": 0.8985265,
                "topicality": 0.8985265
            },
            {
                "mid": "/m/01f43",
                "description": "beauty",
                "score": 0.87356544,
                "topicality": 0.87356544
            }
        ],
  ....
]

7. And so much more...
This article is short--a jump start.  However, there is lots of potential here.  For example, sending your own images using the Raspberry Pi Camera

raspicam
pi-camera

Please feel free to ask any questions regarding how to use the output.

There are other feature detection requests.

Google Vision API -- Other Features

However, I'm going to end the article and move on to rolling my on vision detection systems.  As soon as I figure out stochastic gradient descent.

 

* Search


* Recent Topics

My name is Frits and I am Making a Game called TIXITAXI by Killer Angel
[July 08, 2019, 04:01:58 AM]


Pictures on the front page! by tinhead
[June 30, 2019, 02:55:35 PM]


Coding a Nano i2c Slave by AmandaG
[June 11, 2019, 02:48:03 PM]


repetierHost 2.1.6 not working? by MEgg
[June 09, 2019, 03:11:34 PM]


Servo Calibrator by Bajdi
[May 24, 2019, 04:01:10 AM]


MKS Gen L 1.0 by Bappi
[May 21, 2019, 07:22:54 PM]


ESP32 "Life is Life" 64x32 flexible P4 RGB LED by jinx
[May 18, 2019, 11:19:44 AM]


Warco HV-4" Rotary Table by jinx
[May 08, 2019, 03:12:58 PM]


Warco WM14 milling machine by jinx
[April 28, 2019, 09:41:40 AM]


MKS GEN L Servo Issue by Reywas
[April 22, 2019, 09:10:08 PM]


Meowth Abandoned by Nemesis
[April 11, 2019, 11:08:00 AM]


Bench Power: Help a rebel out by jinx
[April 03, 2019, 04:20:10 AM]


Just a short intro... by MEgg
[March 18, 2019, 05:49:28 PM]


Yes I am alive! by jinx
[March 10, 2019, 04:38:53 AM]


CZ-1 2.0: problems, calibration and printing, part2 by MEgg
[February 26, 2019, 03:35:15 PM]

* Recent Posts

Re: My name is Frits and I am Making a Game called TIXITAXI by Killer Angel
[July 08, 2019, 04:01:58 AM]


Re: My name is Frits and I am Making a Game called TIXITAXI by fritsl
[July 05, 2019, 03:51:46 AM]


Re: My name is Frits and I am Making a Game called TIXITAXI by Killer Angel
[July 05, 2019, 03:06:49 AM]


Re: My name is Frits and I am Making a Game called TIXITAXI by fritsl
[July 04, 2019, 01:57:44 PM]


Re: My name is Frits and I am Making a Game called TIXITAXI by Killer Angel
[July 04, 2019, 03:33:22 AM]


Re: Pictures on the front page! by tinhead
[June 30, 2019, 02:55:35 PM]


Re: Pictures on the front page! by Brassfly
[June 30, 2019, 01:07:32 PM]


Pictures on the front page! by fritsl
[June 30, 2019, 09:12:25 AM]


My name is Frits and I am Making a Game called TIXITAXI by fritsl
[June 28, 2019, 07:28:05 AM]


Re: Coding a Nano i2c Slave by AmandaG
[June 11, 2019, 02:48:03 PM]


repetierHost 2.1.6 not working? by MEgg
[June 09, 2019, 03:11:34 PM]


Re: Servo Calibrator by Bajdi
[May 24, 2019, 04:01:10 AM]


Re: Servo Calibrator by jinx
[May 22, 2019, 02:28:13 AM]


Re: MKS Gen L 1.0 by Bappi
[May 21, 2019, 07:22:54 PM]


Re: MKS Gen L 1.0 by jinx
[May 21, 2019, 03:27:08 PM]