Tool: TomTom

[nchan0154]

This issue is for discussion of the reference tool "TomTom Maps SDK for Web".

---

TomTom has reached out to us, explaining that they offer 2500 free credits daily with no credit card.

Does this align closer to with @NickFitz is doing with the API services?

Links:

• Documentation for their Map API product (e.g., HTTP formats for raster & vector tile servers)
• Documentation for the TomTom Maps SDK for Web (the JS library)
• Tutorial for displaying basic map

[AmeliaBR]

Thanks for finding the docs & starting the issue, Nic. I added a link to the JS SDK docs.

The basic map example & other tutorials on that page are a good start for describing default widget capabilities. Like many of our reference JS frameworks, the line between default widget and dynamic API is blurry, because you're building the map with JS calls either way. My rough rule is that "widgets" covers features that could be mapped to a declarative API, although they might be specified in the framework as JS config objects. But yeah, it's a blurry line.

If either of you want to grab your own API key for experimenting, go ahead. But we'll need to figure out a way to set up the keys that are officially associated with the CG & the maps4html.github.io domain. (we can discuss that in #24)

[prushforth]

I also own the domain maps4html.org if that helps.

[AmeliaBR]

Minor annoyance. Their docs are clearly aimed at mobile app developers, not web developers. Download our entire SDK! Install it as an NPM app, but it isn't hosted on NPM. Self-host the library! Anyway, I was able to find the copy of the library code they use for the live examples & that seems to work fine.

The map viewer is built on Leaflet, though, so I'm not sure how much extra functionality it will have as far as the basic widget capabilities. Since our other Leaflet examples use OpenStreetMap raster tiles, I'm going to use the TomTom vector tiles for the examples, so there is at least some distinction.

[AmeliaBR]

Another annoyance (for our use case, which is unusual, I admit):
The TomTom CSS file includes copies of the mapbox and leaflet CSS. Or parts of it. Or modified versions thereof. I haven't compared rule-by-rule. At the very least, it's duplication. But if any of their code is modified compared to the originals, the selectors will override the styles of the other maps since we're just dumping all the code and all the CSS on to the same page.

(Can I have scoped CSS already? Like already?)

[AmeliaBR]

OK, @nchan0154: I've added the basic intro and the first two examples. Feel free to start adding more examples & adding summaries of capabilities. Don't go into detail in cases where the capability is just the same as Leaflet, but pay attention to unique features especially re the vector tiles. (Which they are converting client-side to images that then get used by Leaflet.)

[nchan0154]

Interesting! The vector tiles seem a lot faster when looking at the side by side examples, I'm excited to dig in more. Thank you for setting it up.

(Also, pouring one out for the 'scoped' attribute, you are missed.)