Maperitive

Maperitive should provide a way to label heights on relief contours, like they are labeled on topo maps.

Maperitive should be able to repeat the street label if the street is very long. The repeat settings should be configurable as rendering properties, like minimum distance between repeated labels.

Users should be able to run scripts without the need for the graphical user interface (GUI) to be open. A console version is needed that would make Maperitive truly an automated solution that could be run on servers.

Maperitive should support digital elevation model (DEM) data in the GeoTIFF format, not just SRTM HGT.

Maperitive should be able to load the OSM data for rendering from a database, not just from a file.

Add support for WMS server in order to make overlays comfortably with existing orthophoto or other maps. See http://groups.google.com/group/maperitive/browse_thread/thread/0374912ae1b31998/e6172552c3c95971#e6172552c3c95971

The current command line completion is kinda freaky, so it would be good if there is a way to turn it off.

The current rendering rules system has a poor support for OSM relations. What's needed is access to relation's member roles, its tags and tags of its members. This will probably be implemented as part of the Python scripting functionality.

If the multipolygon in an OSM file does not have all of its members, Maperitive doesn't treat it as a closed polygon and the multipolygon does not get color-filled. Maperitive needs a solution similar to coastline rendering: the multipolygon...

Users should be able to rotate the map so that it doesn't always point "north up". Text labels should not be rotated.

Maperitive should be able to render maps using different map projections, not just Mercator projection used in Web maps.

It seems that Maperitive doesn't support multiple outer ways forming a ring in multipolygons. As wiki says: "This is useful for multipolygons encompassing very large areas, where it would be impractical to have one way run around the whole of...

The super-uber-cool command X can't be used if there is no info about it. I understand that every update introduces new commands and features and it is hard for a man to keep track of all the changes, but there are automated tools that create...

Maperitive currently only supports regular expressions on tag names when matching OSM objects (http://maperitive.net/docs/manual/Querying_Data.html#@isMatch%20Function). Matching tag values would be useful, too.

Maperitive is able to save the tiles using the classical //.png format .... it would be interesting to make Maperitive able to display these tiles, typically changing the "add-web-map" command to use the tiles folder ....

There seems to be a number of sources of .OSM format files, OSM CC-by SA, CANVEC Canadian Government, CommonMap and I understand OSM will become CC-by-odbl etc. Could the OSM CC-by-SA line at the bottom be replaced by a parameter of some sort...

For example when rendering text for power line you should use voltage=*. The value is something like 100000 which should be rendered as 100 kV. So this can be defined as "replace the end three zeros with space and 'kV' string".

Maperitive has a nice UTM overlay grid. It would be nice to be able to choose a different projection, such as MGRS, OSGB, Irish NG, CH-1903, for the overlay.

When map rotation is implemented, there should be a compass rose with a few placement options like top,top-left, bottom-right etc...

Curves are currently rendered for using a limited GDI+ curving function and are not supported in SVG. A proper solution, probably using Bezier curves, is needed.

Wouldnt it be cool, you could just zoom and pan in your favourite mapping application without interruptions? I am curious if it's a lot of work to implement Direct2D [1] into Maperitive. [1]...

Ability to export to a gis format would be an unbelievably cool option allowing further processing and analysis on osm data. maybe a quantumgis project file with different .shp layers and a style files to match.

Please add a page in the documentation, reporting all the default values used for ruleset. (I spent a lot of time trying to disable the bold effect on text and finally I understand that was about text-halo-width and not font-weight :P)

It would be fine to have some asymmetrical lines in order to paint cliffs or some roads with cycleways on one side. For cliff rendering in Mapnik see http://www.openstreetmap.org/?lat=-22.135435&lon=166.522308&zoom=18&layers=M

Imagine you want to put a shield on all tourist attractions (on points, lines, and areas). Then you can do something like this: features labeled : tourism=attraction rules target : labeled define ... draw : shield...

There should be a function (similar to line-offset property) for buffering (offsetting) polygons.

Not sure if this is the right place to put this but I recently struck a problem with this combination and Maperative. When looking at the exported bitmaps using the OziExplorer .map files, Land drew the maps upside down and inverted. I checked...

... and borders using (predefined) pattern.

Via map properties, one can define the ocean color. For http://wiki.openstreetmap.org/wiki/User:Head/HaptoRender I need another property to define an ocean texture.

Maperitive needs a map-sea-color-opacity property to be able to set the opacity of the sea.

Can you implement "live" crosshair displaying coordinates on mouse position? I believe, that this wouldn't be such a big problem. It helps to identificate problems with placing elements. It can show alternatively on alt key press&hold ...

With latest maperitive (1228) under linux, there's a minor problem regarding the icon paths in the default rendering ruleset (Default.mrules). The directory is named "Icons" (with capital "I"), while the icon paths have "icons/..." (with lowercase...

Like these: http://media.tumblr.com/tumblr_lkxo9vJwJO1qghjht.png More on this issue in my blog post: http://braincrunch.tumblr.com/post/5335286217/line-rendering-artifacts

In default map style, when exporting to SVG, steps are very narrow, and they are not centered on the way.

Currently behavior of arcs in custom symbols is somewhat erratic, and there is problem with ambiguity of input. Maperitive now accepts horizontal and vertical radius and endpoint. But in some instances this is not enough - there are two possible...

I added a text-func to generate the text for a node. I think that this function is called about five to seven times for the same node. As it always returns the same string, this is just a waste of time.

When rendering shapes or text on a line, the line-offset setting should be taken into account so that the line is offset.

For orientation purpose it would be great to have a grid with a predefined scale. This makes navigating and calculating distances in the field easier. (if the map is printed off course) It shouldn't be to hard to implement a way to specify your...

As a new user I've recently used Maperitive to generate some city centre maps each highlighting different sets of features/amenities (shopping, entertainment, etc.). This seems to require producing multiple .mrules files each with small...