Brett Camper

Tangram already uses js-yaml to parse the file, and reports back any errors it encounters -- are there errors that js-yaml finds that you believe aren't making it back to...

Thanks, will check it out. Likely a result of the latest changes from Mapzen -> Nextzen keys. On Thu, Mar 8, 2018 at 4:26 PM, Garret wrote: > Hi >...

Could you show what your `sources` block looks like (you can XXX out any keys)? I haven't been able to reproduce this.

Try removing the `?api_key=XXXXXXX` from your tile url, and providing your API key as: ``` mapzen: type: MVT url: ... url_params: api_key: ``` Does that work? On Mon, Mar 12,...

I wasn't able to discern difference in performance loading this version in Tangram JS (but hey, it didn't get any worse either :)

I'd like to avoid any platform-specific implementation concepts leaking into the scene file like that. On Wed, Dec 12, 2018 at 8:11 AM Hannes Janetzek wrote: > *@hjanetzek* commented on...

Yes I get it, but that seems very awkward to me. On Wed, Dec 12, 2018 at 9:40 AM Hannes Janetzek wrote: > @bcamper What I meant was that Tangram...

@hjanetzek I think I'm not following what you mean here, can you clarify with examples? > There seem to be some stringbuilder implementation for js to avoid the overhead of...

Looking at this more I discovered an issue with defaulting sprite sizes: without some additional metadata indicating the intended native resolution for a sprite-sheet, we can't keep the size consistent...

@karimnaaji in JS, we default to `linear` filtering (not `nearest` which visually is "no" filtering) if no filtering is specified. I really think `mipmap` is overkill in most of these...