[mapserver-dev] Vector Tile Production...

[Lime, Steve D (MNIT)]

I believe you can already do map.scaledenom=10000 or map.scale=10000 to explicitly set a scale for use with queries. Might check to see if a scale has been explicitly set and then on compute if necessary. --Steve

________________________________
From: mapserver-dev-bounces at lists.osgeo.org [mapserver-dev-bounces at lists.osgeo.org] on behalf of Rahkonen Jukka (MML) [jukka.rahkonen at maanmittauslaitos.fi]
Sent: Monday, September 14, 2015 11:14 AM
To: Even Rouault; mapserver-dev at lists.osgeo.org
Subject: Re: [mapserver-dev] Vector Tile Production...

Hi,

Call the vendor option as "scaledenom" so it would be easy to connect with the settings in the mapfile. Width+Height is not so good because vectors do not need non-rectangular pixels.

-Jukka Rahkonen-

________________________________
Lähettäjä: Even Rouault<mailto:even.rouault at spatialys.com>
Lähetetty: ‎14.‎9.‎2015 15:42
Vastaanottaja: mapserver-dev at lists.osgeo.org<mailto:mapserver-dev at lists.osgeo.org>
Aihe: Re: [mapserver-dev] Vector Tile Production...

Le lundi 14 septembre 2015 14:10:27, thomas bonfort a écrit :
> Hi all,
>
> I have  a mostly functional and fully untested (on the client side)
> branch that implements vector tile rendering for mapserver:
> https://github.com/tbonfort/mapserver/tree/vector-tiles .

Thumbs up!

> It relies on
> mapserver's WFS implementation, so we'll need to also adapt mapcache
> to handle these WFS queries in order to present  x/y/z style URLS so
> it becomes actually usable.
>
> Given that we're using WFS, we actually don't care about projections,
> you can request a vector tile for any extent/projection combo,
> although that isn't going to be supported by any client (yet?). I did
> have to fiddle around with handling scale computations as there's no
> concept of scale in traditional getfeature queries
> (<UrlBlockedError.aspx>https://github.com/tbonfort/mapserver/commit/50c3a44ddd3c182ca0e1a16a6e5a1
> c5c20675768) => Steve or Even could you have a glance?

That should be fine I think.

It raises a few interesting ideas for having a more generic scale-aware WFS
mode. Perhaps we could have vendor WFS options WIDTH and HEIGHT that, if set,
would trigger the msCalculateScale() call. So that could also potentially be
used to have scale-aware shapezip output ("give me features in this AOI
appropriate for a 1024x1024 rendering")
And the clipping to the BBOX could also potentially be a CLIPPED=YES vendor
option (but you have to do it anyway for MVT output due to the way coordinates
are encoded).

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20150915/cd500217/attachment.html>