Le mie letture per TANTO

 

Un nuovo editor online per OpenStreetMap

via Planet Geospatial by Richard Fairhurst on 11/30/09

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.

New feature – Beginners’ Guide

You couldn’t write instructions for Potlatch without writing instructions for OSM. The new Potlatch user needs to know about tagging, surveying, and copyright – but they’re certainly not Potlatch-specific.

So Potlatch 2 will have an accompanying ‘OSM Guide’, explaining the basics with friendly, illustrated text. It will be concise, focused and clear.

New feature – vector background layer

Mappers are working more and more with imports. But the approach until now has been to import data directly into the map – and many people have pointed out the problems this can lead to.

Potlatch 2 will support vector background layers. You can load OSM-formatted data from servers or files, and work on bringing it into the map the way you want, at your own pace.

Because this integrates fully with MapCSS stylesheets, you can choose to temporarily hide background data, or show (say) only footpaths… whatever you like.

Fully rewritten in ActionScript 3

Potlatch 2 is written in ActionScript 3, a Java-like language with an open source compiler� and full docs available online. The Potlatch 2 source comes with instructions on getting started and is, of course, permissively licensed under the WTFPL.

Potlatch 2 thus far has been written by Dave Stubbs and Richard Fairhurst (me). But we would love to see more people hacking on the source. There’s a potlatch-dev mailing list especially for this.

Playing with Potlatch

So where are we up to right now, and how long do you have to wait?

The tagging system, rendering engine, geometry editing, and server communication are all up and running – the core of the editor, and the real hard work.

Some other features, like Yahoo and tiled backgrounds, are finished but not currently exposed through the editor: they’ll be along shortly. Others, such as GPS track support, the Beginners’ Guide and the vector background layer are not coded yet but are intended for the initial release.

Potlatch 1 has some three years of development behind it, of course, and much of this feature set has not yet been ported to Potlatch 2. There’ll be countless little UI tweaks (no keyboard shortcuts yet, for example!); and as you’d expect for an in-development version, performance can sometimes be sluggish and there’s a lot of optimisations we’d like to do.

But with work progressing so fast, this seemed a great time to talk about it. Both the tagging system and the renderer are enormously flexible and we’d like to see people hacking on them as soon as possible.

So how about some links? You can find a read-only running version at:
http://www.geowiki.com/potlatch2/

or play with the renderer alone at:
http://www.geowiki.com/halcyon/

Should you want to try a particular area, just put the lat and lon in the URL like this:
http://www.geowiki.com/potlatch2/?lat=52.2&lon=0.1
http://www.geowiki.com/halcyon/?lat=52.2&lon=0.1

and the source is at:
http://trac.openstreetmap.org/browser/applications/editors/potlatch2

and you can read MapCSS documentation at:
http://wiki.openstreetmap.org/wiki/MapCSS

Have a play, let us know what you think, and grab the source!

Spain Cadastre WMS in Spherical Mercator

via Planet OSGeo by gvsigmobileonopenmoko on 11/28/09


As far as I know, the Spanish Cadastre WMS server (run by the Ministry of Economy of Spain) is one of the first to provide its data in the Spherical Mercator projection EPSG:3857 (aka EPSG:3785 and EPSG:900913), so now we can switch between the great cadastre layer and the OSM layers for example. This is the Montjuic Palace in Barcelona:

As we know, the Spherical Mercator projection is conformal (keeps angles and shapes locally) and all parallels have the same length E:

R = 6378137 m
E = 2 * pi * R = 40075016.686 m

But we know that the true length of each parallel is approximately P = E * cos(lat), so if one wishes to measure distances, perimeters or paths directly on a map in EPSG:3857, it’s necessary to multiply the result by a factor f = cos(lat). For areas, f = [cos(lat)]^2. For Barcelona, for example, we have:

lat = 41.402634
f = 0.75008067 (distance)
f = 0.56262101 (area)

According to these results obtained with gvSIG, the perimeter p and area a of that block of buildings should be:

p = 0.75008067 * 571.444 = 428.6 m
a = 0.56262101 * 22935.684 = 12904.1 sq m

The expected values (from the official size of the block shown here) are:

p = 418 m
a = 12387 sq m

Oops, I think I didn’t choose a very standard block.

Curso de gvSIG Online (via feedly)

Curso de gvSIG Online

gvsig_logo

Esta dica vem do blog do Edmar Moretti, que é o curso online de gvSig que foi montado pelos alunos do CEFET de Goiás, sob orientação do Prof. Nilson Ferreira.

O gvSig pra quem não conhece é um software para Sistemas de Informações Geográficas que dispõe de funções para aquisição, armazenamento, gerenciamento, manipulação, processamento, exibição e publicação de dados e informações geográficas.

Quem estiver interesse no curso sobre o gvSig, segue o link: http://www.lapig.iesa.ufg.br/lapig/cursos_online/gvsig/index.html

Fonte: Blog do Edmar Moretti

Posts Relacionados


[link to original | source: Planet OSGeo | published: 5 hours ago | shared via feedly]

OpenStreetMap Formula 1 Circuits (via feedly)

OpenStreetMap Formula 1 Circuits
OpenStreetMap Formula 1 Circuits

F1 OpenStreetMap Circuits
OpenStreetMap Formula 1 Circuit - Circuit de Monaco (Monaco)

OpenStreetMapper 'kevjs1982' has been busy mapping Formula 1 circuits across the world using OpenStreetMap.

"I have been putting a page together showing all the Formula 1 grand prix circuits on OSM and this has shown how random motor racing circuits have been tagged in the past

Highway=road, Highway=motorway, Highway=track, Highway=service, Highway=unclassified, and leisure=sport have all be used.

Relations for the Grand Prix circuit have been created and where the circuit is a dedicated one the highway has been changed to raceway.

Annoying now I've been through the lot it seams that the highway=raceway tag has been abandoned (I could have sworn it wasn't last week) although Mapnik renders it (see Donington Park, Silverstone, Hockenheimring, and Nürburgring for some old highway=raceways) - typical!

If you are in Montreal or Valencia and looking for something to map you could do worse than double checking the grand prix circuits out - looks like both are generally part of the local cycle networks and some areas are probably better tagged as something other than Raceway (current) or Track (previous) - in particular Valencia looks to have been redeveloped a lot since the aerial photography was taken and was originally laid down as a highway=track on top of open ground and other roads.

If you want to see how much stuff can be tagged round a Grand Prix circuit while bringing Potlatch to it's knees than the two German tracks are good places to check out!

Alas, not all tracks are in Open Street Map at present - 上海国际赛车场 (China), İstanbul Park (Turkey), Marina Bay (Singapore), 鈴鹿サーキット (Japan), Yas Marina (Abu Dhabi), and Korean International Circuit (Korea) are missing, and Wikipedia doesn't even know where the Indian track is (unsurprisingly all the new ones outside aerial mapping coverage).

mapperz correction
http://en.wikipedia.org/wiki/Jaypee_Group_Circuit
http://en.wikipedia.org/wiki/Indian_Grand_Prix

Diary entry centred on the Nürburgring Nordschleife - where else could you do so really?

Formula 1 OpenStreetMap can be found at:
http://kjs.me.uk/osm/f1.php - shows all the tracks on this years and next years calendar (aside from India).

So if your interested and have some knowledge either in formula 1 or helping openstreetmap fill the gaps then you can help.
Starting point is http://wiki.openstreetmap.org/wiki/Main_Page
The OpenStreetMap - http://www.openstreetmap.org/index.html

Source:
http://www.openstreetmap.org/user/kevjs1982/diary/8217

Mapperz News Blog

[link to original | source: Planet Geospatial | published: 7 hours ago | shared via feedly]

Apple Has a New Geo Team (via feedly)

Apple Has a New Geo Team
An article on a ComputerWorld blog announces that Apple quietly bought PlaceBase, and that the founder of that company, Jaron Waldman, is now part of the “Geo Team” at the company. Read more related Spatial Sustain posts:China Bans Map TradingMapSherpa Launch Forges Whole New Geo Business PlanOrtelius Aims to Unleash Both the Art and Science of [...]

[link to original | source: Planet Geospatial | published: 3 days ago | shared via feedly]

Master IED in Comunicazione Ambientale

via envi.info by redazione on 9/21/09

di Eleonora Anello

Giunto ormai alla 6° edizione il Master in Comunicazione Ambientale dello IED (Istituto Europeo di Design) si conferma come realtà formativa consolidata.

Il Master, in collaborazione con AICA (Associazione Internazionale per la Comunicazione Ambientale), nasce dalla consapevolezza che sempre di più le aziende, gli Enti Pubblici e gli enti senza fine di lucro devono affrontare i problemi e le opportunità che l’ambiente nel suo complesso offre. Il comunicatore ambientale risponde alle esigenze delle aziende per quanto riguarda gli aspetti del “marketing verde” e del rapporto dell’azienda nei confronti del territorio, oppure, nel caso di aziende che producono servizi per l’ambiente, si occupa della comunicazione rivolta al cittadino-utente.

La durata del corso è di 200 ore, suddivise in moduli di tre giorni nell’arco di 6 mesi, formula che permette anche a chi già lavora nell’ambito e desidera implementare la proprio formazione, di frequentare i corsi. La sede delle lezioni è Torino presso lo IED. La chiusura delle iscrizioni e la possibilità di accedere alle tre borse di studio a copertura parziale è fissata al 2 ottobre.

Questo il link per consultare il programma dettagliato e avere ulteriori informazioni.

QGIS 1.3 ‘Mimas’ is here

via Planet Geospatial by admin on 9/20/09

We just released QGIS 1.3 ‘Mimas’. Download your copy http://qgis.org/en/download/current-software.html and read the official announcement over on the QGIS blog here

I did some revisions to the Windows all in one installer for this release and was able to shrink it down in size quite a bit – always good news for those of us living in hte ‘internet badlands’.

The vector editing features in QGIS are now becoming a serious contender with commercial applications in my opinion, the new goodies in QGIS 1.3 just go even further to qualify that statement.

Hope you all enjoy using the work of a very dedicated QGIS developer team (these guys always blow my mind with their work!).

I will probably plan the next release for after the QGIS Hackfest in Vienna in November. Really looking forward to that!

GeoCouch: New release (0.10.0)

via Planet OSGeo by Volker Mische on 9/19/09

It has been way to long since the initial release, but it’s finally there: a new release of GeoCouch. For all first time visitors, GeoCouch is an extension for CouchDB to support geo-spatial queries like bounding box or polygon searches.

I keep this blog entry relatively short and only outline the highlights and requirements for the new release as GeoCouch finally has a real home at http://gitorious.org/geocouch/. Feel free to contribute to the wiki or fork the source.

Highlights

  • Many geometries are supported: points, lines, polygons (using Shapely).
  • Queries are largely along the lines of the OpenSearch-Geo extension draft. Currently supported are bounding box and polygon searches.
  • Adding new backends (in addition to SpatiaLite) is easily possible.

Requirements

Other versions might work.

Download

If you don’t like Git, you can download GeoCouch 0.10.0 here.

ALL 1,841,177 UK POSTCODES FREE'D?

via Planet Geospatial by Mapperz on 9/16/09

ALL 1,841,177 UK POSTCODES FREE'D?


Example of UK Individual Postcodes

Example of UK Individual Postcodes (density)
image source:

http://da.vidnicholson.com/2006/12/uk-postcode-coverage-map.html

According to the Guardian:

"Wikileaks is hosting what it says is a copy of the entire UK postcode list, last updated on July 8 2009, that contains "all 1,841,177 UK post codes together with lattitude [sic] and longitude, grid references, county, district, ward, NHS codes and regions, Ordnance Survey reference, and date of introduction. The database ... is over 100,000 pages in size."

The 230MB file, zipped to 20MB, does indeed contain a huge slew of postcodes in comma-separated form, with those details as headers for each column.

Oh my. We have no idea who has leaked this, but it is the gateway to some valuable information: Royal Mail, as we ascertained previously in the Free Our Data campaign, sells the Postcode Address File (aka PAF) for a considerable sum, and makes a good profit on it: in August 2007 the postal regulator Postcomm revealed that PAF operations made a profit of £1.58m on revenues of £18.36m, all but £4m from resellers."

Data seems to be

Postzon™

"links Postcodes and addresses to geographical data"

http://www.royalmail.com/portal/rm/jump2?mediaId=400088&catId=400084

so there is a licence cost:

System licence £1,000
Multi-system licence £3,000
Corporate licence £25,000

Full story:

http://www.guardian.co.uk/technology/blog/2009/sep/16/wikileaks-postcode-file-free-data

More information on UK Postcodes

http://en.wikipedia.org/wiki/Postcodes_in_the_United_Kingdom

If you want a non-derived Royal Mail/Ordnance Survey and Free Postcodes without an annual licence.

http://www.freethepostcode.org/currentlist


Mapperz News Blog

Huffman’s Three Principles for Data Sharing

via Planet Geospatial by Sean Gorman on 9/16/09

Todd came into town for the Gov2.0 Summit last week, and in additional to dropping off a terabyte worth of data from Afghanistan, he talked a bit about what has made the “beer for data” program work at the Taj. Outside the universal thirst for beer data sharing success boiled down to three basic principles:

1) Create immediate value for anyone contributing data: when users contribute data they should get an immediate return on that investment. In the case of the Afghan pilot that meant getting to see your contributed data on a map of high resolution satellite imagery as soon as you uploaded it. The imagery for Afghanistan was made available by NGA, then tiled and served up by a Fusion Server, graciously donated by Google.

2) Make contributor’s data available back to them with improvements: any data that goes in should be available to download back out again. Further, the data should come back better than when it went in. In the Afghan pilot this meant if you shared data in a spreadsheet format into the platform you could get it back out as KML, shapefile, Atom, JSON, spatialite etc. (Addendum to principle 2 - PDF’s are evil, and make parsing and extracting data into a sharable format complete misery.)

3) Share derivative works back with the data sharing community: urge users who create derivative works, with shared data, to contribute their data products back to the group. In the case of the Afghan pilot researchers were taking the detailed data from the field and feeding it into their sophisticated models and simulations. Researchers would then upload the results into GeoIQ to share the derivative works back with the data sharing community. This meant that agencies and individuals that shared data again got a better product back by contributing. The researchers get better data to feed their models, and a self perpetuating feedback loop is created that sustains increasing data sharing.

While these sound like simple principles, it is amazing how often they are not followed and effective data sharing is blunted. Too often data sharing - especially with government and corporations - is a black hole. Data goes in but never comes back out. Also it is rare to see the positive feedback loops of researchers sharing their work products back with the data sharing community. Too often researchers get wrapped around the axle on their products being proprietary or sensitive. While this can be the case their is huge benefit in feeding results back to gauge their veracity and accuracy. I’ve definitely seen way too many models that look great in the lab and completely fall apart in reality because researchers would not feed results back to the field for verification and error bounding. I’m hoping we’ll have more opportunities to implement these principles in future projects and we can see the success of Todd’s work in Jalalabad duplicated hundreds of times over.