Hi Jon,
I just tried your patch but now I always get the following error when doing
an import:
node_changed_mark failed: ERROR: prepared statement "node_changed_mark"
does not exist
Any ideas?
Thanks,
Jason
On Fri, Jan 22, 2010 at 8:48 PM, Jason Beverage wrote:
> Hi John,
>
> Thanks for the
Hi John,
Thanks for the patch, I will give it a test this weekend! I think it would
be a decent option on the command line if it works out well.
Jason
On Fri, Jan 22, 2010 at 6:38 PM, Jon Burgess wrote:
> > > I'm working with osm2pgsql (latest trunk version) to import OSM into
> > a
> > > Post
> > I'm working with osm2pgsql (latest trunk version) to import OSM into
> a
> > PostgreSQL/PostGIS database. The issue I'm having is that if I use
> > the --slim option I'll occasionally get an error similar to:
> >
> > Going over pending relations
> > COPY_END for COPY osm_rels FROM STDIN;
> >
On Jan 21, 2010, at 1:19 PM, Frederik Ramm wrote:
> It is fixed now.
>
> Bye
> Frederik
Thanks Frederik!
Dane
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
Hi,
Brett Henderson wrote:
> I was wondering how you fixed it. That's neat. Do you need the
> --sort-change-0.6? You probably do, but I don't know what order you end
> up with using --apply-change with full history diffs.
I tried it without, and it complained - for some reason the newer
ver
On Fri, Jan 22, 2010 at 8:54 AM, Frederik Ramm wrote:
> Hi,
>
>
> Brett Henderson wrote:
>
>> If you use the latest SVN version it will detect if multiple versions of
>> an entity exist and throw an error in the --apply-change task. I'll try to
>> do another official release of Osmosis over the
Hi,
Brett Henderson wrote:
> If you use the latest SVN version it will detect if multiple versions of
> an entity exist and throw an error in the --apply-change task. I'll try
> to do another official release of Osmosis over the next day or two with
> this change included.
Just for laughs - a
On Fri, Jan 22, 2010 at 8:19 AM, Frederik Ramm wrote:
> Hi,
>
> Jon Burgess wrote:
> > It seems there are two versions of a way in the haiti data:
>
> My bad. I forgot a --simc switch when I moved from Haiti only to
> Haiti+DomRep this afternoon and this broke things.
>
> It is fixed now.
>
If y
Hi,
Jon Burgess wrote:
> It seems there are two versions of a way in the haiti data:
My bad. I forgot a --simc switch when I moved from Haiti only to
Haiti+DomRep this afternoon and this broke things.
It is fixed now.
Bye
Frederik
--
Frederik Ramm ## eMail frede...@remote.org ## N49°00'0
On Thu, 2010-01-21 at 11:29 -0800, Dane Springmeyer wrote:
> On Jan 21, 2010, at 5:51 AM, Mike Warren wrote:
>
> > Jon Burgess writes:
> >
> >> If I remember correctly this error occurs when you try to import two
> >> data sets which contain some overlapping data. In your case it
> >> appears
>
2010/1/21 Jon Burgess :
> On Thu, 2010-01-21 at 11:13 -0500, Jason Beverage wrote:
>> I'm working with osm2pgsql (latest trunk version) to import OSM into a
>> PostgreSQL/PostGIS database. The issue I'm having is that if I use
>> the --slim option I'll occasionally get an error similar to:
>>
>> G
On Jan 21, 2010, at 5:51 AM, Mike Warren wrote:
> Jon Burgess writes:
>
>> If I remember correctly this error occurs when you try to import two
>> data sets which contain some overlapping data. In your case it
>> appears
>> that relation ID 284132 appears in both the data extracts. Only the
Jon Burgess writes:
> If I remember correctly this error occurs when you try to import two
> data sets which contain some overlapping data. In your case it appears
> that relation ID 284132 appears in both the data extracts. Only the slim
> mode keeps a copy of this node/way/relation data and tri
On Thu, 2010-01-21 at 11:13 -0500, Jason Beverage wrote:
> Hi all,
>
> I'm working with osm2pgsql (latest trunk version) to import OSM into a
> PostgreSQL/PostGIS database. The issue I'm having is that if I use
> the --slim option I'll occasionally get an error similar to:
>
> Going over pending
14 matches
Mail list logo
