On 17 Jun 2009, at 00:56, Ian Dees wrote:
On Tue, Jun 16, 2009 at 6:20 PM, Shaun McDonald sh...@shaunmcdonald.me.uk
wrote:
On 16 Jun 2009, at 14:00, Ian Dees wrote:
My Java version [1]. I haven't updated it yet because it was
working fine.
What are my options for the converter? Do I
Pushed to dev
-Original Message-
From: talk-boun...@openstreetmap.org [mailto:talk-
boun...@openstreetmap.org] On Behalf Of Joe Richards
Sent: 17 June 2009 9:13 AM
To: t...@openstreetmap.org
Subject: [OSM-talk] Land Information New Zealand (LINZ) data
importtechnical steps
I'm working
On Tue, Jun 16, 2009 at 7:10 PM, Telsnospam-ab...@bloodgate.com wrote:
Instead of getting more consistent and easy-to-interpret-and-use data, all we
get
is more and more garbage, duplicated information (attribution=blah on every
node!), badly designed data structures (multipolygons, I look at
Hi,
Sorry in advance if I'm in the wrong place (please point me to the bug
tracking system if there's one)
I might have found a bug in the current osm2pgsql code that handle boundary
relations, but I'm not smart enough to kick his ass.
Happens when :
- handling type=boundary/multipolygon
On 13 Jun 2009, at 09:04, Matt Amos wrote:
unfortunately, sometimes data finds its way into OSM which might be
copyrighted. the data working group was set up to help the community
deal with these incidents when usual methods of community arbitration
fail.
the usual course of action when
On 14 Jun 2009, at 10:49, Wolfgang Schreiter wrote:
Hi Fr
This also gets in the way of the
osm community itself. New mappers ask for guidance all the time, and
countless hours of precious mapper and developer time are wasted in
debates
on how to do this or that correctly, how to
On 12 Jun 2009, at 23:29, Stefan de Konink wrote:
Tom Hughes wrote:
Ian Dees wrote:
I'm interested in this data dump, too. What do we still need to
talk about?
The practicalities of how we (a) separate the public tracks from the
private ones (about a 75:25% split) and
I hope it is
So it looks like you grab a node and it has id n and you upload after
changing it n+1. Or something.
If the database has some id n+1 it shouts 'EPIC FAIL' and the client
says uh-oh you're out of date.
But, the client could just try uploading n+2 or n+3... n+m until it
succeeds. Is that
yeah sorry I mean version
On 17 Jun 2009, at 13:06, Iván Sánchez Ortega wrote:
El Miércoles, 17 de Junio de 2009, SteveC escribió:
So it looks like you grab a node and it has id n and you upload after
changing it n+1. Or something.
I don't understand why a client would want to change node
El Miércoles, 17 de Junio de 2009, SteveC escribió:
So it looks like you grab a node and it has id^H^Hversion n and you upload
after changing it n+1. Or something.
AFAIK, the API doesn't work like that. When uploading data, you have to
provide the version number you downloaded, *not* the
2009/6/17 Iván Sánchez Ortega i...@sanchezortega.es:
El Miércoles, 17 de Junio de 2009, SteveC escribió:
So it looks like you grab a node and it has id^H^Hversion n and you upload
after changing it n+1. Or something.
AFAIK, the API doesn't work like that. When uploading data, you have to
On 17 Jun 2009, at 00:56, Ian Dees wrote:
On Tue, Jun 16, 2009 at 6:20 PM, Shaun McDonald sh...@shaunmcdonald.me.uk
wrote:
On 16 Jun 2009, at 14:00, Ian Dees wrote:
My Java version [1]. I haven't updated it yet because it was
working fine.
What are my options for the converter? Do I
12 matches
Mail list logo
