> I completely missed the significance of this aspect of your question! :) Now
> I'm really curious.
;) You may wish to check out this blog post from Kartena, they cover
TileStache too:
http://blog.kartena.se/using-tilemill-without-spherical-mercator/
> We've scaled horizontally. We serve 3
On Tue, Mar 22, 2016 at 7:45 AM, Peter Devoy wrote:
>
> Thanks for the suggestion Brian. I did look into it but understood it
> using non
> Spherical Mercator projections couldn't be done without hacking/extension?
>
That's probably fair. I can't say I know much about tiling
> TileStache is very simple and lightweight and needs very little in the way
> of infrastructure outside of Python, a few package requirements, and a
> WSGI-compatible Web server.
Thanks for the suggestion Brian. I did look into it but understood it using non
Spherical Mercator projections
I use TileStache for my tile layers (http://tilestache.org/doc/), all data
stored in PostGIS. While my tiles are raster images rendered with Mapnik,
TileStache also now has Vector support, which might meet your needs: (
http://tilestache.org/doc/TileStache.Vector.html).
TileStache is very simple
Thanks Paul & Peter for the stimulating topics and resources!
-Original Message-
From: postgis-users [mailto:postgis-users-boun...@lists.osgeo.org] On Behalf Of
Peter Devoy
Sent: Monday, March 21, 2016 1:34 PM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] Postgres as cache
>Drupal
HI Robert, thanks for the suggestion but unfortunately I am not
using Drupal in any projects. Best of luck with your modules
though, Mapzen's SQL functions may be of interest to you:
https://github.com/mapzen/vector-datasource/tree/master/data
> I think a generic HTTP cache in front of
ISTM that map-specific tile caching solutions are mostly there to
provide things that generic HTTP caching systems don't do, like
metatiling, or guttering the map requests. If you don't need those
features, I think a generic HTTP cache in front of your web service
would be the most architecturally
Hey Peter - no dumb endeavors only dumb implementations :)? Don't know if
my implementation is dumb or not but I am currently using Drupal to
generate GeoJSON vectors. Since Drupal has caching in it's core I am
relying on it to provide this which it seems to do OK (up to about 500
points it
Hi all,
Has anyone here tried using Postgres as the caching layer in a vector tile
server?
I need to set up a tile server and what I am thinking is have PostGIS cut up
geometries into GeoJSON vector tiles as requests come in and cache the JSON for
said requests in some other Postgres table(s)