mapnik 0.5.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News mapnik 0.5.0 (Default branch)
# 1  
Old 02-08-2008
mapnik 0.5.0 (Default branch)

ImageMapnik is a toolkit for developing GISapplications. At the core is a C++ shared libraryproviding algorithms/patterns for spatial dataaccess and visualization. Essentially a collectionof geographic objects (map, layer, datasource,feature, and geometry), the library doesn't relyon "windowing systems" and can be deployed in anyserver environment. It is intended to play fair ina multi-threaded environment and is aimedprimarily, but not exclusively, at Web-baseddevelopment. High-level Python bindings(boost.python) facilitate rapid applicationdevelopment, targeting zope3, django, etc.License: GNU Lesser General Public License (LGPL)Changes:
Support was added for native builds on Mac OS X, single/multi-threading variants, gdal rastering, and character encoding. The text label placement functionality was made more comprehensive. A Qt4 based viewer application was added. The internal geometry representation was changed to explicitly support multi-geometries. An optional libxml2 based map loader was added. Image quantization was added. Image "views" are supported. The "memory file" based I/O in the shape input plug-in was improved.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
core_addshmem_read(5)						File Formats Manual					     core_addshmem_read(5)

NAME
core_addshmem_read - determines the inclusion of readable shared memory in a process core dump VALUES
Failsafe Default Allowed values or DESCRIPTION
The tunable was added in response to a problem where a customer was limited in debugging a user-level process crash because shared memory segments were not written as part of the core file. Upon core dump, the sections of user memory labeled as shared read-only are written (along with the normal data sections) if this tunable is set to and left out if it is set to Who is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Value of This Tunable Be Raised? When you wish to include read-only shared memory segments in user core files due to debugging needs by developers or maintainers on the system. What Are the Side Effects of Raising the Value? User process core files would increase in most cases (most applications use at least some shared memory). This could be a problem on sys- tems where disk space is at a premium. When Should the Value of This Tunable Be Lowered? When there is no need for debugging core files where shared memory corruption or data values are in question. What Are the Side Effects of Lowering the Value? Core files will tend to be smaller. What Other Tunable Values Should Be Changed at the Same Time? Certainly think about which does the same thing for read/write shared memory segments. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. Tunable Kernel Parameters core_addshmem_read(5)