Embed an interactive map as html

[macrigiuseppe]

Is your feature request related to a problem? Please describe.
Currently there is now way to export an existing map as an html file

Describe the solution you'd like
As user I should be able to export the map from the export bar

Potential designs:

• Independent options

• or we can combine "Export map url" and "Export map" into a single element.

And in the export modal dialog we provide the following options:

• Export map to an html file
• Export to Cloud and generate permalink

Existing issues affected:
#301
#223 possible reference

Possible implementation

• Convert the entire page into a string and save it as html file using html-screen-capture-js. Maybe using webworkers to speed up the process.
• Static template:
  • Publish a build of kepler.gl to cdn
  • Generate a static html file we are going to use as the template, it should be automatically generated during deploy
  • Once users export a map, we can simply hydrate the template with data/configuration map

Considerations

• Should we link js and css externally or keep them in line?
• What happens if data is too big? Can we combine everything in one file or should we use an external file?

[roqueleal]

We hope soon you can develop the embeded module soon! Greetings excellent contributions

[macrigiuseppe]

reference: #331

[macrigiuseppe]

This is blocked by #332

[schnerd]

One consideration that I don't see listed in the issue: Versioning of builds published to the CDN.

If the static HTML people are using makes any assumptions about the kepler JS API (or CSS for that matter), then the builds published to the CDN should probably be versioned. Otherwise publishing a new Kepler build with backwards incompatible changes could break all these old static pages. If you make the bundled code a part of the published npm package, you could probably use unpkg as a free CDN for this.

[macrigiuseppe]

One consideration that I don't see listed in the issue: Versioning of builds published to the CDN.

If the static HTML people are using makes any assumptions about the kepler JS API (or CSS for that matter), then the builds published to the CDN should probably be versioned. Otherwise publishing a new Kepler build with backwards incompatible changes could break all these old static pages. If you make the bundled code a part of the published npm package, you could probably use unpkg as a free CDN for this.

@schnerd unpkg is exactly the strategy we have decided to pursuit .

[briantcl]

as discussed in the sprint meeting, we will also test it out by introducing this new feature in a medium ariticle as well. thanks!

[Jesterary]

How soon will this feature be available? It will be very helpful!

[macrigiuseppe]

How soon will this feature be available? It will be very helpful!

@Jesterary the necessary work for the functionality is tracked in here: #366

[vulkenree]

can I easily embed kepler.gl to a dash app?