Frank, Some more issues to add to the list. There are cases where the same way exists in different data sets but with different uses. A good example is that islands in the waterbody data are often repeated in the wooded data (if the island happens to be wooded, which happens a lot). Importing one set after another leads to duplicated ways. This case is time consuming to fix because you have to reconcile two ways and a relation. This same issue arises with wetlands. Probably others too but these are the ones I've encountered most often.
It would be wonderful if this was handled automatically, but as you stated merging the different data sets for a more sophisticated analysis of the data would lead to massive files. Another issue is how the data is partitioned. It would be really helpful if they were divided by geographical area. Currently there are a number of files sparsely populated with features (040P07 has 23 files for Wooded_area). If you are working on one area you need to import all the files which defeats the purpose of splitting them in the first place. Please don't suggest importing the current files one at a time as you can't download that large an area at once from openstreetmap. One could do a mass upload of each file but I thought that was frowned upon. Additionally, it means uploading without running the validator (resulting in duplicated nodes & ways). -- James Treacy tre...@debian.org _______________________________________________ Imports mailing list Imports@openstreetmap.org http://lists.openstreetmap.org/listinfo/imports