[OSM-dev] UTF-8 problems in informationfreeway?

[Brett Henderson]

Stefan Baebler wrote:
> On Dec 21, 2007 7:41 AM, Brett Henderson <brett at bretth.com> 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.
>   
>> Let me know if you see it occurring on any new hourly diffs.  Daily
>> diffs already had the prod encoding hack enabled so if they contain UTF8
>> issues please let me know.
>>     
> I will check my problematic nodes tonight and report if there are any problems.
>
>   
>> It is easy for me to re-generate the hourly diffs if necessary, I just
>> have to modify the timestamp file and it will go back in time and
>> re-generate up to the current time.  If anybody wishes me to do this let
>> me know.
>>     
> It is probably easier to start with importing fresh planet dump into
> informationfreeway, than it would be to import every hourly dump ever
> since they were introduced. Then daily , then continue with hourly...
> until we find some other problem and start all over :)
>   
Yep, I won't bother unless somebody really wants it.

Brett