The title may be a little confusing as not only Manifold powers up this example http://hgis.cartoninjas.net/?lng=en , but it does indeed some heavy lifting behind. Geoserver data and some other external sources are consumed by our app as well.
We used Manifold as a tile renderer for our historical topo layers. WMS is of course rendered in the real time but also are the pre-rendered layers... well initially as they are cached while being accessed ;-) The next time a tile is pulled it comes from cache.
The historical topo raster layers behind are fairly big - 100k and 25k maps are around 50gb each and manifold is really fast when reading and serving data from such data sources. We worked on a project where we had to serve orto imagery for Holland - we had 5 or 6 layers each well over 100gb in size and manifold didn't even choke! We find it a real 'monster' when it comes to working with ecws.
As for the app itself - it is rather demanding so the best browsing experience is when using Chrome or Firefox, then Opera or Safari (no GE plugin though) and then IE 9+ (yeah, 9+ ;-)
Manifold as a data server for a web app
No replies to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users