Faster polygon rendering about mapsui

[smremde]

@pauldendulk Is it possible, for large geometry datasets, to use the GDI rendering interface and a TileLayer ?

[pauldendulk]

Yes, something like that could be possible. The Mapsui.Sample.Wpf project has a Shapefile sample that uses the RasterizingLayer. This uses the DefaultRenderer (in this case Mapsui.Rendering.Xaml) to create bitmaps from the shapefile vectors. You could create your own RasterizingTileLayer that works similarly. You could create a specific renderer instead of the default renderer.

Some notes:

• The GDI renderer is not used in any of the projects that I work on and I am not sure if it works properly atm.
• Threading might be an issue. Rendering on a background thread is often problematic. You might need to invoke it on the UI thread.
• I don't see much future for GDI. I see a trend towards more hardware accelerated rendering. For Xamarin I now focus on OpenGL (through OpenTK) for Windows I would like to use DirectX (through SharpDX).
• The current OpenGL renderer has no implementation for IRenderer.RenderToBitmapStream :(
• A RasterizingTileLayer wil need a TileSchema. This could be created on the fly. Take the map extent. Calculate the square that contains that extent. Take that as the top tile. Split is in fours going down a number of levels.

[pauldendulk]

I just committed an update to ShapeFileSample to fix the Mapsui.Samples.WinForms sample. This uses GDI rendering.

Also I did a quick test with GDI rendering in the RasterizingLayer. In Mapsui.Samples.Wpf.Window1.xaml.cs.ShapeFileClick I added this as first line:

       DefaultRendererFactory.Create = () => new Rendering.Gdi.GdiMapRenderer();

And added a reference to Mapsui.Rendering.Gdi. To my surprise this just worked :). Performance was actually not that much faster. The main benefit of your suggestion is the rasterization. Which platform you use for rasterization is less important, but it helps if it's fast.

[smremde]

A RasterizingTileLayer would only be advantageous if you can query your data spatially or cache tiles.

Which platform you use for rasterization is less important, but it helps if it's fast.

Yes, I hadn't looked closely at your library and I hadn't seen the RasterizingLayer!

Threading might be an issue. Rendering on a background thread is often problematic. You might need to invoke it on the UI thread.

GDI rendering would not have this issue.

[pauldendulk]

A RasterizingTileLayer would only be advantageous if you can query your data spatially or cache tiles.
True, but I see spatially querying data (fetching just the data you need for the tile) as a separate issue. Others report this problem here: https://mapsui.codeplex.com/discussions/554838. Basically the problem in this case is the implementation of the ShapefileProvider. The IProvider.GetFeaturesInView has a BoundingBox parameter which could be used to fetch just that box from disk or database.

[pauldendulk]

I am closing this issue. I added some more specific issues: #16, #17 and #18.

There are no plans to improve the performance of the WPF polygon rendering itself. If needed the RasterizingLayer can be used.