Update Google Maps functions

[glenn-jocher]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Replaces a hardcoded Google API key with a safe placeholder and cleans up the MATLAB function for better security and maintainability. 🔒✨

📊 Key Changes

• 🔑 Removed exposed Google API key and replaced it with 'YOUR_API_KEY_HERE'.
• 🧹 Improved formatting and readability (spacing, comments) and added a missing end statement.
• 🔗 Updated comment link to the current Google API Console.

🎯 Purpose & Impact

• ✅ Security: Prevents credential leakage and misuse of shared keys.
• 🛠️ Maintainability: Encourages proper key management and clearer code.
• ⚠️ Breaking change: Users must now provide their own Google API key, or code using the old embedded key will fail.
• 🚀 Best practice: Promotes storing keys outside source control (e.g., environment variables).

Optional tip (safer key handling in MATLAB):

function a = GoogleAPIkey()
a = getenv('GOOGLE_API_KEY');
if isempty(a)
    error('Google API key not set. Define the GOOGLE_API_KEY environment variable.');
end
end

Set it once per session or system:

• Windows (PowerShell): $env:GOOGLE_API_KEY="your-key"
• macOS/Linux (bash): export GOOGLE_API_KEY="your-key"

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting an ultralytics/functions-matlab 🚀 PR! This is an automated response 🤖 — an Ultralytics engineer will review and assist shortly.

To ensure a seamless integration of your work, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/functions-matlab main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

Notes on this PR:

• Thanks for removing the hardcoded credential and adding the placeholder in Google/GoogleAPIkey.m — great security improvement 🔒
• Since this may be a breaking change for users who rely on the Google API, please ensure the PR description clearly flags this and that any usage instructions are included in docs or comments.
• Quick tip for users in the PR body is helpful. Keeping it in sync with the updated function signature is appreciated.

For more guidance, please refer to our Contributing Guide. Don’t hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🎉

[UltralyticsAssistant]

🎉 Merged—thank you, @glenn-jocher!

“An ounce of prevention is worth a pound of cure.” — Benjamin Franklin
Your PR exemplifies this: removing the exposed Google API key, tightening up the MATLAB function, and guiding users toward proper key management elevates both security and maintainability. Calling out the breaking change and promoting environment variables sets a clear, best-practice path for the community.

Appreciate you raising the bar and making the codebase safer and cleaner. 🚀