On Jan 20, 2009 12:48am, James Ewen wrote:
On Mon, Jan 19, 2009 at 6:53 PM, Richard Degelder rtdegel...@gmail.com>
wrote:
> Is there a process to include the NID, in an
> appropriate manner, with the import data that was derived from GeoBase?
In Steve's upload, we have a UUID with each
On Jan 18, 2009 11:08pm, Steve Singer wrote:
On Sun, 18 Jan 2009, Michel Gilbert wrote:
Steve,
Good work. Your osm file looks great. I am going to use your work to
tackle
the nrn import with FME.
Sounds good.
Let me know if you want the latest versions of the geobase2osm.py scri
On Dec 29, 2008 10:41am, Jochen Topf wrote:
On Mon, Dec 29, 2008 at 03:08:36PM +, michc...@gmail.com wrote:
>> There just was a discussion on dev about a single way with 40.000
nodes.
>>
>> That is far too long to be able to handle it with current software and
>>
>> makes lots of pr
On Dec 29, 2008 3:11am, Jochen Topf wrote:
On Sun, Dec 28, 2008 at 06:48:37PM -0800, Sam Vekemans wrote:
> the canadian geopolitical boundries was just imported.
> I imagine there was a spike in the database.
>
> What exactly was the problem? And why &how would it need to be removed?
> Im s
Corey: The Kamploops example was to validate the change detection process
and import. The boundary cutting was arbitrary. I think we can import by
bounding box of 0.5 degree for example and make sure to have overlaps. That
way I would have catch the error you indicate.
Richard: The hydrogra
May be I was not clear. I agree with you, user effort is very important and
we should keep existing OSM data. However Geobase data will provide a very
very very good coverage and accuracy where no OSM data is available. The
use of Geobase data will allow the users to work locally to improve t
I think the idea is not to replace existing OSM data. Therefore the import
should be able to insert only new data. I do not think we should exclude
areas. We should detect the changes instead. Richard proposed to start
where osm data is not present. I agree with him.
Michel
On Nov 20, 2008
7 matches
Mail list logo
