-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add parsing of version and user data #7
base: master
Are you sure you want to change the base?
Conversation
Thanks for providing a patch for #6. |
To use a namedtuple looks much better than a normal tuple. Thanks for your suggestion. |
The parser could also convert the timestamp to a datetime object. I would say there is no performance issue:
|
"only" 23.8usec, but for each node, way and relation. For Germany alone just parsing the datetime would take ~30min. |
Okay, additional 30min for a datetime object is a little bit to high. |
Any news on this patch? This would be very helpful to me. For the record- I agree with not turning the timestamp metadata into a datetime object, since this can easily be done by the programmer (perhaps include an example to illustrate how). The data I need is the version of the object, and the changeset. |
It would be nice that the with_metadata kwarg would be also supported by the pdb parser. In my eyes the implementation for the osm file is complete and works well. |
I'll take a look and see what I can do. My git-foo is not so strong as to easily know how to grab this request and merge it into my branch before working on it |
Was this part released? |
No it wasn't released yet. The main point was that the pdb parser doesn't support the extraction of meta data which provide this patch for osm files.
|
This pull request implements parsing of version and user data from XML source.