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
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) -
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):
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,
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,
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
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:
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
Hi All,
I am trying to implement a warp from a latitude, longitude, altitude (LLA)
image into a custom coordinate system using the GDAL Warp API. The
transform between LLA and my coordinate requires scaling and shifting the
elevation. My coordinate system is a local tangent plane on the
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
Hi,
I would like to collect data from a bunch of GML files into one GeoPackage
but GML files may contain more than 20 layers and ogr2ogr does not want to
append data for me because the -append switch probably has an effect only to
one explicitly given layer.
ogr2ogr -f gpkg -update -append
Hi,
Did you try to add another GML file into existing GeoPackege?
First run OK:
ogr2ogr -f gpkg -update -append mtk.gpkg /vsizip/K2344R_mtk.zip
Secong run gives an error:
ogr2ogr -f gpkg -update -append mtk.gpkg /vsizip/K2433L_mtk.zip
ERROR 1: Layer Kunta already exists, and -append not
Jukka,
>
> I would like to collect data from a bunch of GML files into one GeoPackage
> but GML files may contain more than 20 layers and ogr2ogr does not want to
> append data for me because the -append switch probably has an effect only
> to one explicitly given layer.
-append is supposed to
More intormation:
Reason may be that GML files do not have same layers but the second one has one
layer more:
ogrinfo /vsizip/K2344R_mtk.zip
ERROR 1: Random access not supported for /vsizip
Had to open data source read-only.
INFO: Open of `/vsizip/K2344R_mtk.zip'
using driver `GML'
Le lundi 01 février 2016 14:53:22, Rahkonen Jukka (MML) a écrit :
> More intormation:
>
> Reason may be that GML files do not have same layers but the second one has
> one layer more:
Yes that's exactly the reason. When 'KunnanHallintoraja' was processed, it was
seen as non existing in the
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
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
Le dimanche 31 janvier 2016 09:58:31, Ari Jolma a écrit :
> This seems to be a pretty big thing to add but doable.
>
> So, one more thing to discuss before going to vote later is the target
> milestone. Maybe add it to 2.1 as "an experimental feature" and aim for
> 2.2 as a more production ready?
18 matches
Mail list logo
