Changeset IDs and versions as Long?

2016-07-25 Thread Toby Murray
I'm at the SOTM-US hack day. Someone heard I've tinkered with JOSM and asked some questions. They are trying to work on making an OSM API but with peer-to-peer functionality instead of only talking to a single API endpoint. Their plan is to use changeset IDs and object version numbers as kind of

Re: [OSM-dev] OSM-Carto style, ported to vector tiles!

2016-07-25 Thread Daniel Koć
W dniu 25.07.2016 16:50, Daniel Koć napisał(a): So, I don't understand npm issues, but can work around them, but still there are some other problems, including fonts issues, which I don't understand. Maybe it has something to do with Ubuntu version (mine is 16.04 64-bit)? Report after some

Re: [OSM-dev] OSM-Carto style, ported to vector tiles!

2016-07-25 Thread Daniel Koć
W dniu 25.07.2016 11:24, Rory McCann napisał(a): I presume that is the "maxzoom is deprecated" messages? You can ignore them. Or is it something else? Nope, only minzoom/maxzoom warnings. What happens if you go to http://localhost:8080/tiles/index.json what is the value of the "tiles" in

Re: [OSM-dev] OSM-Carto style, ported to vector tiles!

2016-07-25 Thread Christoph Hormann
On Monday 25 July 2016, Rory McCann wrote: > > > That however would also mean you would need to remove all the > > > > way_area > 0.01*!pixel_width!::real*!pixel_height!::real > > > > filters from SQL for z14 - otherwise you get missing geometries at > > the higher zooms (not a real lot - that

Re: [OSM-dev] OSM-Carto style, ported to vector tiles!

2016-07-25 Thread Rory McCann
On 24/07/16 18:26, Christoph Hormann wrote: > Ok - so you essentially say that use of !pixel_width! and !pixel_height! > is - in the vector tiles system used - limited to the lower zoom > levels. Yes, you can't use *pixel* for z15+. You can hack around it, like I do[1], with "zoom dependent