Posts Tagged ‘opengeodata’

Introducing a new OSM editor… Potlatch 2 (Open Geo Data)

Monday, December 14th, 2009

[Editor's note: This tool from the OpenStreetMaps.org cohort is open source and written in ActionScript 3.0. It displays OSM information in vector format for editing and tagging. Use it in concert with the MapZen iPhone app for capturing points of interest (POI) in the field.]

Republished from OpenGeoData. Nov. 30, 2009.

OpenStreetMap users will know all about Potlatch, the online editor that appears when you click the ‘Edit’ tab on the site. Well, there’s a whole new version coming soon!

Potlatch 2 is a complete rewrite still with the same principle in mind: an editor which hits the right balance between speed, ease-of-use, and flexibility. It’s under very active development at the moment and I’ll include a link at the end of this post where you can have a look.

But there are four big new features – and one behind-the-scenes change – to tell you about first.

New feature – friendly tagging system

Potlatch 2 has a friendly, intuitive tagging system. The mapper can use graphical menus, dedicated fields, and icons to get the tagging just right – without the need to remember tag names and values.

For example, you can choose highway types from a set of icons, then add a speed limit by selecting the appropriate restriction sign.

Potlatch 2 tag editor

All this is fully customisable using a straightforward presets file. Using this, you can create your own favourite tag combinations.

New feature – WYSIWYG rendering

Potlatch 2 has an all-new rendering engine far in advance of the current one.

With road names, patterned fills, rotated icons, and much more, the editing experience can be like working live on the familiar Mapnik rendering, the cyclemap, Osmarender, or anything you like -making it much more approachable for the beginner.

The Halcyon renderer used in Potlatch 2

Just like the tagging, the rendering is easy to customise. It uses a special form of CSS, called MapCSS, which lets you create wonderful-looking maps with just a few lines of text. The tagging and rendering together make Potlatch 2 ideal for ‘vertical’ mapping applications, such as a cycle-specific editor or a building/addressing editor. Stylesheets aren’t just about making the map look pretty: you can create stylesheets to help your mapping, such as one that highlights roads without names.

The rendering engine (Halcyon) is available as a compact (<100k) standalone component which you can embed in webpages, so your custom maps can be used outside Potlatch 2.

Continue reading at OpenGeoData . . .

Copyright Easter Eggs (OpenGeoData)

Friday, October 24th, 2008

[Editor's note: Amusing April 1st post from the folks that bring us OpenStreetMap.org. Republished from there. I think meant both as fun and somewhat seriously. I remember making my first trap street on the Humboldt Bay Bay Area Bike Map in 1997 :)]

Commercial map providers have for years used ‘easter eggs’ or as cartographers know them ‘trap streets’. These are fake streets, churches and sometimes villages in maps that are put in on purpose. If you copy the map then the map owner knows it was you because you couldn’t possibly have mapped these fake features.

OSM has a large wiki page on the subject including this picture of an A-Z map:

Notice ‘Lye Close’ ? This pun has been put there as a trap street, there is no actual street there.

In the license process, the OpenStreetMap Foundation has recognised the need for a license not just based in copyright law. Like large commercial map suppliers we are moving toward a license based upon copyright, database and contract law. These ‘three pillars’ are the same foundations upon which many data sets are sold.

Similarly and in order to professionalise OpenStreetMap due to the increasing completeness and therefore value of the OpenStreetMap data we need to protect copyright. The OpenStreetMap Foundation has decided to begin a process of entering trap streets in to our data. These will be in out of the way places so that they are not noticed, but if that data turns up in a TomTom or similar device then we will be able to prosecute for infringing our data.

This process was decided on secretly at the first OSMF board meeting over a year ago and many hundreds of trap streets are now present. The OSMF has decided to go public now because we have completed an entire ‘fake village’ and placed it in southern Germany. These trap streets and the trap village are un-deletable in the API due to special code to protect copyright.

The OpenStreetMap Foundation Board feel this is a good compromise between on the one hand having only real streets and no copyright protection and on the other enforcing all downloads of data with DRM mechanisms which were found impractical. The community impact is now to be measured, now that these methods and tools are public.

The Board would like to invite discussion on this exciting new method of protection, and will follow comments to this post closely.

The OpenStreetMap Foundation Board.