Re: [mapguide-users] XYZ-Tiles of different size

[Gunter Becker]

Hi Hans,

Not exactly, since this bug, I think, refers to an external WMS service your
FeatureSource is pointing to. In this case I think the MapGuide Server
should have already requested the external WMS with a higher dpi value, as
you mentioned, to get the result you have seen from the other server! 

But you are pointing in the right direction. XYZ-Tiles with a doubled size
of 512 x 512 pixel should not only be resized twice. They should also have
the correct label or symbol size and therefore must also be resized in
relation to dpi. That's like the behaviour you have mentioned for WMS
services. And I geuss that's also the reason why the GETMAPIMAGE
WebApi-Methodes has a dpi value. At least I have used it with higher dpi
(150) in the past for printing high quality maps.

Gunter





--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] Future plans/roadmap for MapGuide Open Source

[Jackie Ng]

Now that both MapGuide and FDO have CMake build systems for building on
Linux, we can offload most of the thirdparty libs to what is provided by the
system. And in this respect, Ubuntu provides the most compatible set of
thirdparty libs we need to build MapGuide and FDO.

As of right now, we can actually build FDO trunk via CMake on Ubuntu 14.04
LTS with 100% system-provided thirdparty libs.

MapGuide via CMake is not fully there. We still need to internally build
dbxml, apache and PHP through existing build scripts and
AGG/DWFToolkit/CS-Map through hand-made CMakeLists.txt integration. But for
everything else, Ubuntu 14.04 LTS provides the right range of compatible
libraries.

I intend to use CMake over autotools as the defacto Linux build system for
MapGuide/FDO in the 3.3 release.

Once the 64-bit Linux blockers (which I've said I'll be detailing in another
post, and I still intend to) are cleared, it would also solve the problem of
what distros to support. We can simply standardize on Ubuntu and for
everything else, just run it inside a docker container based on an Ubuntu
docker image.

- Jackie



--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] XYZ-Tiles of different size

[Hans Milling]

Could it be this bug:
http://osgeo-org.1560.x6.nabble.com/MapGuide-WMS-images-scaled-blurry-td5083082.html
I think it has something to do with the DPI you set on your map. if you want
higher resolution you need to increase the DPI from the standard 72 or 96 to
150 or 300.



--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] Future plans/roadmap for MapGuide Open Source

[Gabriele Monfardini]

Hi,

we're using Centos 6 MapGuide 32 and 64bit.
But I agree it's better to focus in a well supported linux build (and
remove 64bit blockers), no problems on which modern distribution is used.

Building from source was historically a cumbersome and very slow task,
since source is very big due to the huge amount of third party libs/apps
and hard coded values in makefiles, that prevent the process to be
streamlined.
I don't know if something has changed recently in this regard.

A dream as a Linux user would be to swap out third party components and
user system defaults, shipping only configuration details (f.i. Apache,
PHP).
This would make also compiling from source much easier and quicker.

Best regards,

Gabriele Monfardini
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users

Re: [mapguide-users] XYZ-Tiles of different size

[Jackie Ng]

Sorry, not at the moment. XYZ tiles are currently always fixed at 256x256
pixels.

If "retina" tiles is just the same bounding box rendered out to a 512x512
tile instead of 256x256, it would not be difficult to implement support for
retina tiles (We can enable retina tiles via a new parameter in the XYZ
TileSetDefinition).

I just need confirmation around the definition of what a "retina" tile
actually is. Is it just the size of the tile? Or are there other factors
that make a tile "retina"?

- Jackie



--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users

[mapguide-users] XYZ-Tiles of different size

[Gunter Becker]

Hi,

is it possible to generate xyz-tiles of a different size than 256 x 256
pixels? 

We are using OpenLayers as our viewer and print our maps with  MapFish Print
  . The problem is that when
trying to print layers of type "xyz" the print output is extreamly pixelated
while layers from a tiled wms source looks nice. OL and MapFish Print seem
to support different sizes than 256 x 256. Especially for "retina/hidpi
devices" there are properties to set the tile size: OL ( ol.source.XYZ -
tileSize,tilePixelRatio
  ), MapFish
Print ( OSM Layer - tileSize, dpi
  ).

Maybe there is any undocumented request parameter for the
GETTILEIMAGE-Request of the WebApi? Or maybe it is configurable in the
serverconfig.ini?

Gunter



--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users