[OSM-dev] XAPI and using a home server
grahamjones139 at gmail.com
Sun Mar 6 16:32:35 GMT 2011
That seems to have fixed it. I will add this workaround to the instructions
on the Wiki.
I'd better try using it for something now!
On 6 March 2011 15:25, Roland Olbricht <roland.olbricht at gmx.de> wrote:
> > The only thing is that it ends with:
> > "runtime error: open64: 2 ./db/area_tags_local.bin File_Blocks:1"
> > and does not provide the closing </osm-derived> tag.
> > Do you have any suggestions on what might cause that?
> Yes, it's a bug in the software. Thank you for reporting it. First, for a
> feasible workaround please place empty files with names
> in the database directory. The probably fastest way is
> pushd YOUR_DATABASE_DIR
> touch area_tags_local.bin
> touch area_tags_local.idx
> The cause is a little bit intricate. OSM3S should allow for the usage of
> derived data structures, and as a showcase the handling of areas is
> This feature is not mature enough to offer it as part of the regular
> interface, but areas if present, can be printed with the print statement.
> Unfortunately, the print statement throws an error if a corresponding file
> the database doesn't exist. While useful in general to find errors, its
> unhelpful for this optional data structure, which may be absent for good
> However, the workaround above should do it for the moment. I'll fix the
> behaviour, by making areas truly optional also in the print statement, with
> the next bugfix version.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dev