On Dec 21, 2007 3:09 PM, Brett Henderson <[EMAIL PROTECTED]> wrote: > Stefan Baebler wrote: > > On Dec 21, 2007 7:41 AM, Brett Henderson <[EMAIL PROTECTED]> wrote: > > > >> I'm a dufus, I may have found the problem. I didn't have the production > >> encoding hack enabled on the hourly diffs, I've enabled it now. > >> Presumably this means that most non ascii characters were being mangled. > >> > > s*it happens :) > > > > Perhaps writing some of the commandline parameters (all sans > > passwords) into the header of xml might be a good idea to know how > > data was obtained. Of course this would only reveal last osmosis > > operation on the given dataset, but better this than no info at all. > > When opening such file as input stream with osmosis this info could be > > shown (either by default or in verbose mode). > > > Perhaps, but it's not very simple. I'm not sure how you'd pick the > relevant options to include without just dumping the entire command line > into the file. That leads to problems figuring out which parts of the > command line should be masked out and getting access to the orginal > command line in the first place. It could be messy. > > However my main issue is that I'm very hesitant to add kludges to > support features of limited value. Given the generic nature of osmosis > it is hard to add metadata that is useful. A similar one is that > osmosis isn't currently supporting the bounds xml element because it is > difficult to do so in a meaningful way.
Brett, as an aside, I have a good chunk of the Bounds support mostly written, but then I looked at the xml again and saw the "origin" attribute (data source URI). I have no idea why that's stuck in the bound element, but there it is, and I'll figure out how to deal with it. So, soon Osmosis can support this metadata of limited usefulness... Karl _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
