Skip to content

Code sprint

Jump to bottom
rweait edited this page May 23, 2012 · 20 revisions

Mapnik Code Sprint 02 - Washington, DC, USA. 15-17 June 2012

The Mapnik community is gathering for another code sprint to improve Mapnik, set the path for the future and to enjoy the company of other Mapnik developers.

You are invited. Be part of it.

When

Friday through Sunday, 15 - 17 June 2012.

Preliminary schedule

  • Friday evening: Meet and greet. Pub discussion. Show and share.
  • Saturday: Plans and teams. Lots of coding.
  • Sunday: Lots of coding.

Where

Development Seed
1714 14th Street NW
_Rear Entrance_
Washington, DC 20009

(map coming soon)

Why?

Coding, documentation and fun. The previous Mapnik code sprint in September 2010 was both great fun and a great success. Bugs were squashed, capabilities were added, performance was improved and new friends and colleagues were discovered. Proof

This time, we'll tackle some more bugs, some of the lingering Top ten Cartography Wishes from last time, and perhaps knock out some awesome new Mapnik documentation for the ever-increasing user community.

Top Ten Tasks

Last time, the Top Ten* Advanced Cartography Wishes looked a bit like this. Those that have been completed in the interim are struck-through.

http://www.slideshare.net/steve8/what-id-like-to-do-with-mapnik-4756837

  1. icon rotation: could also be used for amenity=viewpoint when tagged with viewing angles

  2. SVG icons: allow replacing colors (e.g. color a black icon in blue); have an alpha parameter (done)

  3. move icon a bit if it would collide with others

  4. replace an already placed icon with a collection icon when there is another one to be shown right there

  5. push lines apart so that there is a minimum distance between them (nearly done)

  6. be able to construct file names from tag values in XML (e.g. "symbol_file=parking.svg" should be mapped to e.g. ~/mapnik/parking.svg or http://example.com/parking.svg). Right now, people resort to generating XML styles by a script. (done, see "PathExpressions")

  7. when there is a very curvy road, place the name along a smoothed line (when the text is not centered to the line but with a dy) (nearly done)

  8. multi-line text constructed from several tags, e.g. for peak name and height (can be done when you accept the same styling for these text fragments)

  9. stronger coupling between icon and text (maybe similar to the ShieldSymbolizer?) so that manual text dy tweaking is not required anymore (want to be able to say: "place this icon in size 20x20 and put the text in size 12pt five pixels below it")

  10. collapsing of little small areas with the same tags into a single big one (for e.g. a big forest), so that e.g. the name is drawn only once

  11. be able to suppress automatic text rotation (per style or layer) - contour lines should always be displayed so that the base line of the text points to the lower ground

  12. underlined text (for e.g. capitals)

  13. sometimes, peak names drawn in a half circle, would be

Attending

  • Artem Pavlenko (UK), Mapnik Founder and Lead Developer
  • Dane Springmeyer (Oregon), Mapnik Lead Developer
  • Richard Weait (Ontario)
  • add your name (and origin) here
  • ...

More tasks and interests

Add your personal tasks and interests here.

  • Awesomeness (Artem)
  • Amazingness (Dane)
  • Mapnik documentation and tutorials (Richard)
  • add your tasks and goals
  • ...

* FSVO "ten"

Clone this wiki locally