[OSM-dev] Osmosis enableDateParsing

[Karl Newman]

On Wed, Jan 7, 2009 at 4:25 PM, Frederik Ramm <frederik at remote.org> wrote:

> Hi,
>
>    I played around with the enableDateParsing option and found:
>
> $ time osmosis --rx testfile.osm enableDateParsing=yes --wx out.osm
> Jan 8, 2009 1:12:50 AM com.bretth.osmosis.core.Osmosis main
> INFO: Osmosis Version 0.29
> [...]
> Jan 8, 2009 1:13:10 AM com.bretth.osmosis.core.Osmosis main
> INFO: Pipeline complete.
>
> real    0m20.456s
> user    0m19.420s
> sys     0m1.290s
> $
>
> $ time osmosis --rx testfile.osm enableDateParsing=no --wx out.osm
> Jan 8, 2009 1:16:55 AM com.bretth.osmosis.core.Osmosis main
> INFO: Osmosis Version 0.29
> [...]
> Jan 8, 2009 1:17:15 AM com.bretth.osmosis.core.Osmosis main
> INFO: Pipeline complete.
>
> real    0m20.061s
> user    0m20.460s
> sys     0m0.930s
> $
>
> How can this be explained? I would have expected a significant, or at
> least noticeable, difference between running with and without date
> parsing! (I tried "enableDateParsing=foobar" just to make sure Osmosis
> recognizes the option, and it does complain that foobar is not a yes/no
> value...)
>
> Bye
> Frederik
>

Brett changed it a while ago where the timestamps are preserved as strings
instead of parsed into Date objects. So now, I think enableDateParsing=no
will put in dummy timestamps. If you leave date parsing enabled (it is by
default) and your original timestamps are in "standard" (ISO) format, then
it will just pass the strings through unmodified.

Karl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20090107/8d4159f1/attachment.html>