Skip to content

[google_maps_flutter] Add support for heatmap layer  #33586

Closed
flutter/packages
#3257

Description

@Rob-Biemans

Add heatmap layer api support as in the Google Maps Javascript API, which can be found here; https://developers.google.com/maps/documentation/javascript/heatmaplayer

Activity

  1. XinyueZ commented on Jun 13, 2019

    @XinyueZ
  2. Rob-Biemans commented on Jun 16, 2019

    @Rob-Biemans
    Author
  3. urmilshroff commented on Aug 16, 2019

    @urmilshroff
  4. jerfeson commented on Aug 29, 2019

    @jerfeson
  5. DCubix commented on Oct 14, 2019

    @DCubix
  6. clemclx commented on Oct 24, 2019

    @clemclx
  7. fvisticot commented on Nov 13, 2019

    @fvisticot
  8. MpEliaz commented on Dec 27, 2019

    @MpEliaz
  9. SvenSlijkoord commented on Jan 11, 2020

    @SvenSlijkoord

    Heatmap support is implemented for both Android & iOS in PR flutter-team-archive/plugins#2454 but I am having trouble getting the podspec file to build because Google-Maps-iOS-Utils is a static framework dependency.

    The build_all_plugins_ipa task gives the following error:

    [!] The 'Pods-Runner' target has transitive dependencies that include statically linked binaries
    

    Does anyone know how to include the Google-Maps-iOS-Utils dependency without breaking the build?

  10. cyanglaz commented on Jan 27, 2020

    @cyanglaz

    After looking into the google-maps-utils repo, I want to experiment to have a separate flutter plugin to handle all the features in the google-maps-utils. I will set up the new plugin and add some minimum code. After that, we can work together to add these new features. Including heat-map mentioned in this issue.

  11. lbk9 commented on Jan 30, 2020

    @lbk9
  12. 46 remaining items

  13. flutter-triage-bot commented on Nov 29, 2023

    @flutter-triage-bot

    This issue is marked P1 but has had no recent status updates.

    The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

    Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

  14. stuartmorgan-g commented on Dec 5, 2023

    @stuartmorgan-g
    Contributor

    This is in progress; keeping P1.

  15. flutter-triage-bot commented on Apr 9, 2024

    @flutter-triage-bot

    This issue is marked P1 but has had no recent status updates.

    The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

    Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

  16. ZhuBoao commented on Apr 11, 2024

    @ZhuBoao
  17. stuartmorgan-g commented on Apr 23, 2024

    @stuartmorgan-g
    Contributor

    The PR had been blocked on a significant API wrapping issue, but that has been resolved an the PR is once again making good progress.

  18. trevor-nomadik commented on May 8, 2024

    @trevor-nomadik

    The PR had been blocked on a significant API wrapping issue, but that has been resolved an the PR is once again making good progress.

    Anyway I can help? Would definitely solve one of my current problems.

  19. stuartmorgan-g commented on May 8, 2024

    @stuartmorgan-g
    Contributor

    Anyway I can help?

    Anyone is welcome to add comments to flutter/packages#3257 if they have feedback that they would help advance the PR.

    (Since this issue has attracted a lot of "me too"-type comments, I want to clarify that comments on the PR need to focused on constructive feedback; "+1" or "me too" will only slow progress by wasting the time of the people working on the PR.)

  20. wangela commented on Aug 13, 2024

    @wangela

    Heatmap layer support has been released for apps targeting Android, iOS, and web in google_maps_flutter v2.8.0 🚀

  21. github-actions commented on Aug 27, 2024

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  22. locked as resolved and limited conversation to collaborators on Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority issues at the top of the work listc: new featureNothing broken; request for a new capabilityc: proposalA detailed proposal for a change to Fluttercustomer: crowdAffects or could affect many people, though not necessarily a specific customer.p: mapsGoogle Maps pluginpackageflutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions