Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chart: Map not visible #1583

Open
benjamincharity opened this issue Jun 26, 2019 · 3 comments
Open

Chart: Map not visible #1583

benjamincharity opened this issue Jun 26, 2019 · 3 comments
Assignees
Labels
Focus: component Issues concerning a specific component Needs: exploration Issues that need more information before being worked on P3: Important Status: BLOCKED Items that cannot be started until something else is accomplished Status: on hold Issues we will not address in the immediate future Type: bug An implemented item with undesired effects

Comments

@benjamincharity
Copy link
Contributor

benjamincharity commented Jun 26, 2019

1. What is the expected behavior?

The map should be visible

2. What is the current behavior?

The map is not visible, but the locations seem to be placed correctly.

chart map not working.png

No console errors.

3. What are the steps to reproduce?

Providing a reproduction is the best way to share your issue.

a) Go to the live demos
b) Navigate to the Chart demo
c) Change the selected chart to the 'map' type.
d) Notice no map is visible

NOTE: This is only reproducible when visiting a built application. This does not happen when serving (even with the aot flag).

Note: This happens even if the map is the chart that is initially loaded

Replication here: http://lab.benjamincharity.com/terminus/demo

4. Which versions of this library, Angular, TypeScript, & browsers are affected?

  • UI Library: latest
@benjamincharity benjamincharity self-assigned this Jun 26, 2019
@benjamincharity benjamincharity added Focus: component Issues concerning a specific component Needs: exploration Issues that need more information before being worked on Type: bug An implemented item with undesired effects labels Jun 26, 2019
@benjamincharity benjamincharity removed their assignment Jul 1, 2019
@benjamincharity
Copy link
Contributor Author

benjamincharity commented Jul 17, 2019

Others have reported this and a collaborator has replicated the issue. We'll wait a bit to see if more information arises.

amcharts/amcharts4#1424

Another issue specifically around this:

amcharts/amcharts4#1146

The current resolution is to disable the build optimizer. But I do not seeing us turning that off for all of our production applications.

Replication showing that disabling the build optimizer does solve the issue: http://lab.benjamincharity.com/terminus/demo2

@benjamincharity benjamincharity self-assigned this Jul 17, 2019
@benjamincharity benjamincharity added the Status: on hold Issues we will not address in the immediate future label Jul 17, 2019
@benjamincharity
Copy link
Contributor Author

Possible fix?

It isn't actually an issue with Angular, you just need to add these lines of code and it will work:

let polygonSeries = map.series.push(new am4maps.MapPolygonSeries());
polygonSeries.useGeodata = true;

@benjamincharity
Copy link
Contributor Author

The above is not a fix. Our code already had these lines directly from the original example.

@benjamincharity benjamincharity added the Status: BLOCKED Items that cannot be started until something else is accomplished label Jul 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus: component Issues concerning a specific component Needs: exploration Issues that need more information before being worked on P3: Important Status: BLOCKED Items that cannot be started until something else is accomplished Status: on hold Issues we will not address in the immediate future Type: bug An implemented item with undesired effects
Projects
None yet
Development

No branches or pull requests

1 participant