On 9/16/07, Frederik Ramm <frederik at remote.org> wrote:
>> Hi,
>> > In latest planet (planet-070912.osm), I get a bunch of ways with
> segments
> > that do not exist. For example, segments with ids 44408190 or
> 44408195 are
> > in ways 6064842 and 6064843, but the segments do not exist in the
> planet.
> > If I make the API calls to get the segments, they both exist.
> >
> > So, is this a planet.osm artifact? Is it a race condition while
> generating
> > the planet?
>> Yes, exactly. Since the script dumps nodes, then segments, then ways,
> any nodes segments created while segments are being dumped will be
> missing, as will all segments created while ways are being dumped.
There would be greater referential integrity if the ways were dumped first,
then segments and then nodes.
Since some consumers of planet.osm might expect nodes, then segments then
ways, the dump could easily create three separate files which are then
stitched together in the expected order.
This is esepcially ugly if you don't think about it, import the planet
> into your own MySQL database, and start creating new nodes... they
> will be assigned IDs that look fresh to your MySQL but there will
> actually be segments referring to these IDs already, creating a nice
> mess.
>> Bye
> Frederik
>> --
> Frederik Ramm ## eMail frederik at remote.org ## N49°00.09' E008°23.33'
>>> _______________________________________________
> dev mailing list
>dev at openstreetmap.org>http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20070916/3c51a000/attachment.html>