No, the problem shows up clearly enough if you compare a node in planet.osm to the corresponding node in a diff file.<br><br><div class="gmail_quote">On Dec 17, 2007 10:44 AM, J.D. Schmidt <<a href="mailto:jdsmobile@gmail.com">
jdsmobile@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Did the UTF-8 encoding problems start to show up, after OSMXAPI was
<br>moved to the HyperCube server ? AFAIU, eventhough its url is an<br><a href="http://informationfreeway.org" target="_blank">informationfreeway.org</a> address, OSMXAPI processing was moved to the<br>HyperCube server, so something might have been differently configured on
<br>an US locale installed server, versus the UK locale installed<br><a href="http://informationfreeway.org" target="_blank">informationfreeway.org</a> server.<br><br>Might be a good idea to check that first.<br><br>Dutch
<br><br>80n skrev:<br><div><div></div><div class="Wj3C7c">> Brett<br>> Yes, it's probably something like that. All I can say for sure is that the<br>> node in planet.osm looks different to the same one in an Osmosis diff file.
<br>><br>> If we could identify how it is encoded differently then maybe I could<br>> compensate for it on import into Osmxapi, but it would be better to fix the<br>> problem at source - wherever that it.<br>>
<br>> Anyway, there's no rush to deal with it at the moment.<br>> 80n<br>><br>> On Dec 17, 2007 6:05 AM, Brett Henderson <<a href="mailto:brett@bretth.com">brett@bretth.com</a>> wrote:<br>><br>>> It warms my heart to return from leave to discover new osmosis utf8
<br>>> problems, I missed those little guys ;-)<br>>><br>>> I'll check it out. Might take me a few days though because I'm a bit<br>>> overwhelmed with email and Christmas at the moment ... Strictly
<br>>> speaking I suspect this is not truly a bug but yet another artefact of<br>>> the database encoding issues, it may not be easy to nail.<br>>><br>>> Stefan Baebler wrote:<br>>>> Another artifact of similar utf problem can be seen at yesterday's
<br>>>> lowzoom(!) tile:<br>>>> <a href="http://tah.openstreetmap.org/Tiles/info.php?x=1107&y=727&z=11&layer=tile" target="_blank">http://tah.openstreetmap.org/Tiles/info.php?x=1107&y=727&z=11&layer=tile
</a><br>>>> Mengeš ("š" is ok)<br>>>> Domžale ("ž" is ok)<br>>>> Moravče ("č" turned into "Ä ")<br>>>><br>>>> On zoom 12 and higher "č" in Moravče is ok:
<br>>>><br>>> <a href="http://tah.openstreetmap.org/Tiles/info.php?x=4431&y=2909&z=13&layer=tile" target="_blank">http://tah.openstreetmap.org/Tiles/info.php?x=4431&y=2909&z=13&layer=tile
</a><br>>>> There definitely is a problem _somewhere_.<br>>>><br>>>> In today's and last week's dump node is ok (extract made with osmosis!):<br>>>> <node id="29161753" timestamp="2007-12-02T08:52:13Z"
<br>>>> lat="46.1356895" lon="14.7445634"><br>>>> <tag k="created_by" v="JOSM"/><br>>>> <tag k="name" v="Moravče"/>
<br>>>> <tag k="place" v="town"/><br>>>> </node><br>>>> (this xml snippet is an extract of a planet file, done with osmosis<br>>>> for local archive:
<a href="http://osm.baebler.net/data/" target="_blank">http://osm.baebler.net/data/</a> )<br>>>><br>>>> Osmosis seems to handle that in files(!) just fine, but osmxapi gives it<br>>> wrong:<br>>>>
<br>>> <a href="http://www.informationfreeway.org/api/0.5/node%5bplace=town%5d%5bbbox=14.5,46.1,14.8,46.2%5d" target="_blank">http://www.informationfreeway.org/api/0.5/node%5bplace=town%5d%5bbbox=14.5,46.1,14.8,46.2%5d
</a><br>>>> either there is a bug in osmxapi or during the import into its db.<br>>>><br>>>> hope it helps tracking it down.<br>>>><br>>>> greets,<br>>>> Štefan<br>>>>
<br>>>> On Dec 8, 2007 12:54 AM, Frederik Ramm <<a href="mailto:frederik@remote.org">frederik@remote.org</a>> wrote:<br>>>><br>>>>> Hi,<br>>>>><br>>>>><br>>>>>> This appears to be an osmosis problem.
<br>>>>>> A recent planet contains the following:<br>>>>>><br>>>>> [...]<br>>>>><br>>>>> I concur; the latest daily diff before the Dec06 planet file had UTF-8
<br>>>>> problems as well but the affected objects were represented ok in the<br>>>>> planet file.<br>>>>><br>>>>> Bye<br>>>>> Frederik<br>>>>><br>>>>> _______________________________________________
<br>>>>><br>>>>> dev mailing list<br>>>>> <a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br>>>>> <a href="http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev" target="_blank">
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev</a><br>>>>><br>>>>><br>>>> _______________________________________________<br>>>> dev mailing list<br>>>> <a href="mailto:dev@openstreetmap.org">
dev@openstreetmap.org</a><br>>>> <a href="http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev" target="_blank">http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev</a><br>>>><br>>><br>
>> _______________________________________________<br>>> dev mailing list<br>>> <a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br>>> <a href="http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev" target="_blank">
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev</a><br>>><br>>><br></div></div>>> ------------------------------------------------------------------------<br><div><div></div><div class="Wj3C7c">
>><br>>> _______________________________________________<br>>> dev mailing list<br>>> <a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br>>> <a href="http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev" target="_blank">
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev</a><br><br><br></div></div></blockquote></div><br>