[OSM-talk] Fixing VMAP0 data

[Martin Spott]

Hi Roozbeh,

"Roozbeh Pournader" wrote:
> Trying to get the earlier points of Iran into OSM, I found that the
> mapnik layer uses VMAP0 data for things such as province boundaries.
> But as it happens all around the world, boundaries change.
> 
> For example, Khorasan, which used to be the largest province of Iran,
> has been divided into four parts. First a small part (Tabas and near
> cities) went to the Yazd province, then the rest of Khorsan got divide
> into three new provinces, North Khorsan, South Khorasan, and Razavi
> Khorasan. The VMAP0 data, unfortunately, does not reflect this.

Well, there are several projects which try to adress such changes - OSM
not being the only one. VMap0 is a very special case as it contains
lots of things that should be fixed in one or the other way  ;-)

Do you have sources at hand that explain the changes that would need to
be made ? I'm maintaining a database of multiple global and local
datasets (including VMap0) and I'd be interested in getting things up
to date there as well. OSM/Mapnik certainly could profit from an
updated VMap0 dataset once the changes are made.

Cheers,
	Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------