can't have a MultiProvider with mvt tiles about tilestache HOT 10 OPEN

@migurski Thanks in advance. I totally see why you'd use their code as a reference, not just merge it in. I look forward to hearing more later in the week.

FWIW, I am the one that opened the issue. I just accidentally did so on our generic company account instead of my own and don't see how to swap it over.

from tilestache.

Thanks for reporting this. Would you be able to provide a pointer to the branch code that you're running? I’m curious about ignore_cached_sublayers but not sure where that’s coming from.

from tilestache.

The lines from my requirements.txt file are:

-e git://github.com/mapzen/TileStache.git@9f867b7d6c8cec3c8e5aa3571e65bfea22cf019f#egg=TileStache-integration-1
-e git+https://github.com/mapzen/tilestache-providers.git@b1b76c71f498bfb56be50633e316eae56089ffc4#egg=tilestache_providers-master

TileStache-integration-1 was a branch that Mapzen assured me a few years back that they kept up to date. Obviously they went out of business a year ago, so it's even more important to get back on the standard system.

from tilestache.

@migurski Is this something that's likely to be fixed soon? Or is there anything you need beyond the lines from my requirements code?

The ignore_cached_sublayers error is what I saw when I tried to use the master branch instead of the Mapzen branch.

I need both points and shapes in my tiles, so I make two tiles and glue them together using the MultiProvider. But that doesn't work for MVT tiles in the master branch. If there's a different way to glue them together, I'm happy to change to that.

Thanks!

from tilestache.

@JulieGoldberg thanks for providing that additional detail! I will try to give this a deeper look during the week. I am unlikely to attempt to merge the Mapzen changes back to TileStache because so many of them are specific to Mapzen’s internal needs. I need to determine where ignore_cached_sublayers is being used and what it’s for to give you a better answer, but I do agree that supporting vector tiles is valuable.

from tilestache.

@migurski Did you have a chance to look at this last week? If so, any update on the timeframe for a fix?

from tilestache.

Hi Julie, not yet!

from tilestache.

It does seem like the changes in question are just in the TileStache.Goodies.VecTiles package. TileStache has a well-defined way of pulling in external packages, so one approach you might take would be to isolate the VecTiles portion of the Mapzen fork and import it as a 3rd-party provider using the Module:Class syntax described in the docs.

from tilestache.

That did actually work. I had to copy in some of their code, adjust paths, etc, but that was it. I'll email you the pieces of their Goodies:VecTiles that I needed to pull out in the hopes that you can integrate it into the main Tilestache down the road. But in the mean time, I can use this workaround. Thanks

from tilestache.

I’m happy that worked, Julie! I see your email, thank you for sending it. I will attempt to integrate your changes.

from tilestache.