Comments: Getting Started with the GeoFence

Pages

Looking for answers to technical questions?

We welcome your comments and suggestions below. However, if you are looking for solutions to technical questions please see our Technical Assistance page.

  • Is the GeoFence software still supported? It doesn't appear that the Google Maps API is working.

    • I found this out just a few days ago. It seems as though Nick Poole's Google Maps API key is no longer working. You can get your own free GM API key by going to the Google Cloud site. You can then edit the index.html file in the app.asar file in the Resource directory under where the executable is. app.asar file can be opened with a 7-zip plug-in. Replace Nick's API key with yours and save the file. You should be able to run the Geofence program after that. You can change the initial location text in the index.html file and the logic.js file has the initial latitude and longitude coordinates if you want to change them. I haven't gotten Node.js to run the main.js file yet even thought I have installed the Electron package. I don't know how to compile all this to the executable either, but at least the program seems to run.

      I'm still working on uploading the coordinates to the board. I haven't figured out if they are uploading correctly or not . . .

      I'd like to be able to re-compile the whole package myself, but there seems to be some missing steps. If anyone has any input it would be helpful.

    • Hi there, it sounds like you are looking for technical assistance. Please use the link in the banner above, to get started with posting a topic in our forums; it looks like someone has already posted about the issue here. Ideally, you should file an issue on the GitHub repo.

      That being said... yes, it does appear to be down. This is not surprising as Google is constantly updating their products. Unfortunately, the SparkX team is extremely busy working on the newest and greatest stuff (aka the Arduino core for the Artemis); so, it might be a while before they can look at that issue. Hopefully, someone in the community tries to pitch in on that javascript error in the meantime.


If you've found a bug or have other constructive feedback for our tutorial authors, please send us your feedback!