Re: [OSM-dev] Creation of dataset for import
Emilie Thanks for this link. It all looks rather complicated and too much for the amount of data that I have. I was hoping for a simpler solution. Right now, it seems to me that tracing twice might be the most effective solution. 80n On Mon, Jul 19, 2010 at 5:15 PM, Emilie Laffray emilie.laff...@gmail.comwrote: On 19 July 2010 17:09, 80n 80n...@gmail.com wrote: I'm just starting a project that will create a load of data for OSM, but will be done off-line based on a static copy of planet.osm. What I want to know is how to create that data so that it is most easily imported back into the main database. It will comprise a lot of new buildings and garden fences but will also comprise plenty of other things (road re-alignments, new roads, open spaces, etc) and will be created by a team of people tracing from aerial imagery. So faced with planet.osm and surrey.osm how can they best be merged? Hello, some people have been doing some kind of merges in France. One is the BMO import which had an incremental road import. http://wiki.openstreetmap.org/wiki/BMO Also for Corine, we spent lots of time looking at overlaps and I suspect some extension of those techniques could be used. Emilie Laffray ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Creation of dataset for import
On Wed, 21 Jul 2010, 80n wrote: Right now, it seems to me that tracing twice might be the most effective solution. The simple solution obviously would generate SQL from a diff file, that can by pass the api. This could be relatively fast. Stefan ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Creation of dataset for import
On 21 July 2010 10:28, 80n 80n...@gmail.com wrote: Emilie Thanks for this link. It all looks rather complicated and too much for the amount of data that I have. I was hoping for a simpler solution. Right now, it seems to me that tracing twice might be the most effective solution. Maybe, anyway if you want to discuss something more technical I would be happy to do so. Emilie Laffray ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Creation of dataset for import
On Wed, Jul 21, 2010 at 10:37 AM, Stefan de Konink ste...@konink.de wrote: On Wed, 21 Jul 2010, 80n wrote: Right now, it seems to me that tracing twice might be the most effective solution. The simple solution obviously would generate SQL from a diff file, that can by pass the api. This could be relatively fast. High performance is not a requirement. Fidelity of merging edits that are potentially conflicting is important. There will be some divergence between the OSM dataset and the once that is being created. Stefan ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Creation of dataset for import
On Wed, 21 Jul 2010, 80n wrote: High performance is not a requirement. Fidelity of merging edits that are potentially conflicting is important. There will be some divergence between the OSM dataset and the once that is being created. Actually it is, the faster the transactions can be pushed through, the lower the chance of collissions will be. If this file takes you a week to upload by the api, the consequences are easy to see. Stefan ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Creation of dataset for import
On Wed, Jul 21, 2010 at 1:04 PM, Stefan de Konink ste...@konink.de wrote: On Wed, 21 Jul 2010, 80n wrote: High performance is not a requirement. Fidelity of merging edits that are potentially conflicting is important. There will be some divergence between the OSM dataset and the once that is being created. Actually it is, the faster the transactions can be pushed through, the lower the chance of collissions will be. If this file takes you a week to upload by the api, the consequences are easy to see. Stefan It's going to take several months to prepare *before* it even meets OSM, so speed really isn't a requirement. 80n Stefan ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Creation of dataset for import
On Wed, 21 Jul 2010, 80n wrote: It's going to take several months to prepare *before* it even meets OSM, so speed really isn't a requirement. So what you actually are looking for is a tool that can interactively fastforward changes? As you would have with a source code versioning system? Stefan ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] Creation of dataset for import
I'm just starting a project that will create a load of data for OSM, but will be done off-line based on a static copy of planet.osm. What I want to know is how to create that data so that it is most easily imported back into the main database. It will comprise a lot of new buildings and garden fences but will also comprise plenty of other things (road re-alignments, new roads, open spaces, etc) and will be created by a team of people tracing from aerial imagery. So faced with planet.osm and surrey.osm how can they best be merged? 80n ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
