Status Update
Comments
ca...@google.com <ca...@google.com>
ca...@google.com <ca...@google.com> #2
i am using these dependencies for the map
// Maps SDK for Android KTX Library implementation 'com.google.maps.android:maps-ktx:3.0.0'
// Maps SDK for Android Utility Library KTX Library
implementation 'com.google.maps.android:maps-utils-ktx:3.0.0'
implementation 'com.google.android.gms:play-services-base:18.5.0' implementation 'com.google.android.gms:play-services-basement:18.5.0' implementation 'com.google.android.gms:play-services-maps:19.0.0'
and also getting some map sdk error as well dab File created: google_maps_sdk_crash dab File created: _google_maps_sdk_crash_count_1 dab Couldn't create marker: google_maps_sdk_crash dab File created: _google_maps_sdk_crash_count_2 dab Marker deleted: _google_maps_sdk_crash_count_1
ca...@google.com <ca...@google.com> #3
Thank you for posting.
We are currently looking into this and will get back to you as soon as we have an update.
jd...@gmail.com <jd...@gmail.com> #4
Thank you for waiting.
We'll need some more details to troubleshoot this issue - please provide the following, in particular steps to reproduce the issue:
-
Put together a simplified reproduction case (
http://sscce.org/ ) and add it to a git hosting provider (e.g. github, bitbucket, etc)? The easiest way to do this might be to fork the Google Maps Android API Samples Repository and modify one of the existing demo activities:https://github.com/googlemaps/android-samples -
List steps to reproduce the problem
- Maps SDK client library version (used to build your app):
- Maps renderer (Latest or Legacy):
- Devices you have verified this issue on:
- Google Play Services version on the device:
- Android version:
- Manufacturer and model:
- Was this working correctly on a previous version of Google Play Services? (If yes, which client library and SDK version?)
-
Attach the following:
- screenshots
- sample code
- an APK if possible.
-
Complete stacktrace when the issue occurs
ca...@google.com <ca...@google.com> #5
Thank you for waiting.
As per our engineering team, please advise on what you intend to use for this data so we can learn more about the use cases and specific data points you are looking for.
jd...@gmail.com <jd...@gmail.com> #6
It would be ideal to have certain metadata including sqft of array, approximate number of panels, age of system, geocode/address etc. Thanks
Jeff Cantin
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Wednesday, March 13, 2024 12:31:34 AM
To: b-system+-2031919821@google.com <b-system+-2031919821@google.com>
Cc: jdcsolalt@gmail.com <jdcsolalt@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
ca...@google.com added
Thank you for waiting.
As per our engineering team, please advise on what you intend to use for this data so we can learn more about the use cases and specific data points you are looking for.
_______________________________
Reference Info: 318248461 Photovoltaic identification feature request
component: Public Trackers > Google Maps Platform<
status: Assigned
reporter: jdcsolalt@gmail.com
assignee: gm...@google.com
cc: ca...@google.com, jdcsolalt@gmail.com
type: Feature Request
access level: Default access
priority: P4
severity: S4
blocked by: 318323170<
retention: Component default
Generated by Google IssueTracker notification system.
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
jd...@gmail.com <jd...@gmail.com> #7
in whether it's possible to recognize solar modules on rooftops
On Wed, Mar 13, 2024 at 12:57 AM Jeffrey Cantin <jdcsolalt@gmail.com> wrote:
Description
========================================================================
#REMINDER: Please do not disclose any PII. Some examples of PII are email address, IP, contact number, any part of name, project numbers and billing accounts. Comments or attachments that include PII will be removed and restricted from public viewing as it may violate our security and privacy policies.
Please refrain from emailing a reply to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
========================================================================
What would you like to see us add to this API?