Ok thanks.
On Wed, Feb 14, 2018 at 8:00 AM, Even Rouault
wrote:
> >
>
> > Great news. Is it possible to provide a user defined list of resolutions
>
> > for the custom scheme which are not power of two?
>
>
>
> Not implemented, but could potentially be done
>
>
>
> Even
>
>
>
> --
>
> Spatialys
>
> Great news. Is it possible to provide a user defined list of
resolutions
> for the custom scheme which are not power of two?
Not implemented, but could potentially be done
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
__
>
>
>
>
> OK, I've added a TILING_SCHEME dataset creation option to define such as
> custom tiling scheme. See
>
> https://trac.osgeo.org/gdal/changeset/41470#file1
>
> for how to use it and how it impacts metadata.json
>
>
>
> Note that this is only implement for file tilesets and not for MBTILES
> >> Hi,
> >>
> >> At the moment we create MVT tiles from PostGIS with ST_AsMVT to suit with
> >> the national gridset that is based on ETRS-TM35FIN (EPSG:3067) coordinate
> >> system. How difficult would you consider to enhance the driver to split
> >> and
> >> write vector tiles according to oth
Even Rouault wrote:
>On mardi 13 février 2018 02:06:47 CET jratike80 wrote:
>> Even Rouault-2 wrote
>>
>> > On lundi 22 janvier 2018 23:40:55 CET Even Rouault wrote:
>> >> Hi,
>> >>
>> >> > P.S. @Even: Any news on a GDAL/OGR MVT reader?
>> >>
>> >> Yes, a new OGR MVT reader has just been commit
Hi all
No there's no standard about non-Webmercator usage of vector tiles.
TileJSON spec. leaves open how CRS is handled which was a wise decision.
So it's up to us to come up with a proposal.
But what's bad is, that TileJSON is not even up-to-date to describe
vector tiles. At least MBTiles spec.
On mardi 13 février 2018 02:06:47 CET jratike80 wrote:
> Even Rouault-2 wrote
>
> > On lundi 22 janvier 2018 23:40:55 CET Even Rouault wrote:
> >> Hi,
> >>
> >> > P.S. @Even: Any news on a GDAL/OGR MVT reader?
> >>
> >> Yes, a new OGR MVT reader has just been committed in GDAL trunk:
> >> http:/
Even Rouault-2 wrote
> On lundi 22 janvier 2018 23:40:55 CET Even Rouault wrote:
>> Hi,
>>
>> > P.S. @Even: Any news on a GDAL/OGR MVT reader?
>>
>> Yes, a new OGR MVT reader has just been committed in GDAL trunk:
>> http://gdal.org/drv_mvt.html
>
> And the writer part (for MVT and MBTILES) driv
On lundi 22 janvier 2018 23:40:55 CET Even Rouault wrote:
> Hi,
>
> > P.S. @Even: Any news on a GDAL/OGR MVT reader?
>
> Yes, a new OGR MVT reader has just been committed in GDAL trunk:
> http://gdal.org/drv_mvt.html
And the writer part (for MVT and MBTILES) driver is now in trunk
http://gdal.o
2018-01-29 14:51 GMT+01:00 Even Rouault :
> Yeah, I didn't really found a specification for those. Just my experiments
> with various MBTiles / directory of tiles found in the wild, and those I
> produced with tippecanoe.
OGR has quite some impact and the announced availability of an MVT
reader a
On lundi 29 janvier 2018 10:21:04 CET Stefan Keller wrote:
> Hi Even
>
> Great news about this MVT reader!
>
> The docs [1] says:
> > The MVT driver only uses the "json" key to retrieve the layer names, their
> > fields and the geometry type, and the "bounds" key for the layer extent.
> I just wa
Hi Even
Great news about this MVT reader!
The docs [1] says:
> The MVT driver only uses the "json" key to retrieve the layer names, their
> fields and the geometry type, and the "bounds" key for the layer extent.
I just wanted to point you to the spec. discussion of MBTiles and
TileJSON metadat
On mardi 23 janvier 2018 13:10:30 CET Jaak Laineste wrote:
> Hey,
>
> I read the drv doc, it was not completely clear how OGR handles exactly
> multi-resolution specifics; as OGR data model does not really “support”
> multi-resolution vector in data model level AFAIK.
Indeed, there's no particula
Hi,
> P.S. @Even: Any news on a GDAL/OGR MVT reader?
Yes, a new OGR MVT reader has just been committed in GDAL trunk:
http://gdal.org/drv_mvt.html
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev mailing list
--- Forwarded message --
From: Even Rouault
Date: 2017-04-17 11:44 GMT+02:00
Subject: Re: [gdal-dev] Vector Tiles in OGR
To: Stefan Keller
Cc: Gdal-Dev , Flippmoke
, Even Rouault ,
petr.pri...@klokantech.com
Hi Stefan,
> P.S. @Even: Any news on a GDAL/OGR MVT reader?
No activity on this f
Hi Stefan,
> P.S. @Even: Any news on a GDAL/OGR MVT reader?
No activity on this front as far as I know. There was a possible funding
opportunity recently
for a project that would have involved integating such a driver with QGIS, but
the odds for it
to come true seems to be very low according
Hi,
@All FYI: We just released an experimental MVT reader for QGIS:
http://plugins.qgis.org/plugins/Vector-Tiles-Reader-QGIS-Plugin/
Pls. test :-)
@Blake:
1. Because QGIS needs to know the CRS we have a problem, since the
TileJSON spec. leaves this open. There are already non-Mercator MVT
product
://github.com/kartotherian/kartotherian-overzoom/blob/master/lib/overzoomer.js
Ben
Von: Stefan Keller
Gesendet: Mittwoch, 3. Februar 2016 18:52:37
An: Blake Thompson
Cc: Stadin, Benjamin; Gdal-Dev; Even Rouault
Betreff: Re: [gdal-dev] Vector Tiles in OGR
Blake,
Sorry for iterating: I checked the spec. and analyzed a sample of
Mapbox vector tiles:
The spec. does not mention null tiles but there are tiles generated by
Mapbox which are empty/null (to save space).
I seems to me that Mapbox GL JS then backs up and takes the data from
a tile at a predef
ilto:sfkel...@gmail.com>>
Cc: Benjamin Stadin
mailto:benjamin.sta...@heidelberg-mobil.com>>,
Gdal-Dev mailto:gdal-dev@lists.osgeo.org>>, Even
Rouault mailto:even.roua...@mines-paris.org>>
Betreff: Re: [gdal-dev] Vector Tiles in OGR
Benjamin Stadin,
As an author of the specificati
Blake,
Thanks for the comments.
Regarding leaving out data at intermediate zoom levels I also meant
omitting (setting to null) the entire tile.
In fact I just realize that the spec. even does not mention how a
reader knows at which level it should expect data if a tile is
null/empty.
:Stefan
20
Blake,
Now the vector tiles spec. and the Mapbox approach became clearer to me.
I'm still pondering about realizing a vector tiles reader (especially
for QGIS) and for vector tiles uses cases like 1. base maps and 2.
spatial analysis:
Regarding clipped linestrings and polygons arriving at reader
Benjamin Stadin,
As an author of the specification, I have to disagree with you on the
support for other projections. There is no limitation on vector tiles being
required to being in mercator. The specification in fact mentions that
other projections may be used:
https://github.com/mapbox/vector
Hi Stefan,
"If there would be OGR driver for vector tiles it would make a similar
resource extremely useful also for other purposes in GIS tools - not only
for tileservers and direct visualisation.“
I was thinking you want to do more than just rendering. Then at least, as
Blake also mentioned, th
Hi Ben
Thanks for explaining - Petr and I are the maintainers of OSM2Vectortiles.
I like projections (and also GeoPackage :-) ).
But reprojection is solved here, since OGR/QGIS can transform on the fly.
This thread is about Petr's question about a reader "for mapbox-like
vector tiles stored in MBT
Hi Stefan,
A vector tile may contain data for several zoom levels. But what data is
shown at which zoom level is defined by the styling, not by the data
itself. It is handled on client side, by the web (or native) tile
renderer.
The path is the same as with mercator tiles (zoomLevel/x/y):
https:
All,
I¹d like to share a few thoughts about the current state of vector tiles.
I believe that, with vector data, there is a chance to get rid of some of
the problems that current mapping tools face in practice, especially in
regards to projections. And this chance should be used in my opinion,
ins
Hi Blake,
There is TileMaker [1]. It implements a MVT writer for v1 only as it
seems, but looks lightweight enough as a good base for a portable library.
Ben
[1]
https://github.com/systemed/tilemaker/blob/master/src/write_geometry.cpp
Am 01.02.16, 18:27 schrieb "gdal-dev on behalf of Flippmok
That's good news!
We'll be happy to add Python bindings to such a generic C++ library
for Mapbox vector tiles.
We have still some time (say few weeks?) left here to decide to
contribute either to these bindings or to Mapzen's pure Python lib.
One reason why I'm insisting on Python (bindings) - bes
Stefan,
I am not aware of any libraries besides mapnik vector tile that have been
attempting to implement v2 specification. I think mapzen's implementation might
be best? We have been wanting to add vector tiles to the python mapnik bindings
for quite some time but we don't have the time to do
Hi Blake
It's clear to me that a good generic c++ library for encoding and
decoding vector tiles is needed.
On the other hand, I'd like to experiment with vector tiles and
related QGIS parallel loading issues for which Python is more
convenient.
It seems that Mapzen's [1] Python implementation is
All,
The first thing that is going to be required likely is a good generic c++
library for encoding and decoding vector tiles IMO.
I have spent a lot of time working on developing the mapnik vector tile library
to be a solid implementation, especially around all the work done for 2.0 of
Mapbo
Hi Petr, Blake, Even and everybody
I'm (besides Petr) the other maintainer of OSM2VectorTiles.
I'd already asked Even a similar question.
I'm advising now an intern to implement such a MVT Vector Tiles reader
client in Python if possible as part of a QGIS plugin.
And I'm interested not to do redun
Hi everybody,
thanks for the comments. Regarding the technical details:
Each Tile is its own discrete dataset therefore the hardest part would be
> merging of features into the original features across tiles. You could use
> some complicated merging technique, but that could be very expensive.
>
Le mardi 05 janvier 2016 21:06:55, Blake Thompson a écrit :
> Petr,
>
> No one that I know of is currently working on such a tool. It could be a
> little difficult to write as well.
>
> Each Tile is its own discrete dataset therefore the hardest part would be
> merging of features into the origin
> I was involved in discussions a few months ago where Mapbox Vector Tiles
> read/write support would have been part of a larger project, but I'm not
> sure if/when this will come true.
Update: just learned that this project has been won by another bidding group,
so I'm not sure if the winner ha
sts.osgeo.org>"
mailto:gdal-dev@lists.osgeo.org>>
Betreff: Re: [gdal-dev] Vector Tiles in OGR
Even,
He is correct that MBTiles can store vector tiles. I know this is done in
https://github.com/mapbox/tippecanoe . I believe there is talk about updating
the MBTiles Spec as well.
Even,
He is correct that MBTiles can store vector tiles. I know this is done in
https://github.com/mapbox/tippecanoe . I believe there is talk about
updating the MBTiles Spec as well.
Thanks,
Blake Thompson
On Tue, Jan 5, 2016 at 2:21 PM, Even Rouault
wrote:
> Le mardi 05 janvier 2016 19:33:3
Le mardi 05 janvier 2016 19:33:32, Petr Pridal a écrit :
> Hi,
>
> Is anybody working on an OGR driver for mapbox-like vector tiles (PBF
> blobs) stored in MBTiles or downloaded from a url via curl?
Hi Petr,
I was involved in discussions a few months ago where Mapbox Vector Tiles
read/write sup
Petr,
No one that I know of is currently working on such a tool. It could be a
little difficult to write as well.
Each Tile is its own discrete dataset therefore the hardest part would be
merging of features into the original features across tiles. You could use
some complicated merging technique
40 matches
Mail list logo