Closed thomas-maschler closed 9 years ago
Hey, I was working on a similar projected and only noticed later, that there was already something out there. I worked on some of your TODOs and fixed some bugs.
There are several other things I want to work on, including adding additional metadata items and a Metadata Reader.
Do you still actively maintain this module and accept more pull requests?
Under which license do you want to publish it. We normally use the MIT license for our code. Would you be fine with that?
Hey Thomas,
Definitely still interested in the project - active maintenance is another issue. We built arcpy-metadata principally for a project we're now done with, but I think it has applicability to our other work, so I can see circling back to it at some point. So, it's not abandoned, but I haven't been adding to it in 2015.
I'm personally fine with the MIT license for the code, but let me confirm that I'm allowed to license the code that way before I say for sure. The University gets a little finicky sometimes, but we've used other open source licenses in the past without a problem.
Thanks for the additions - this is all great stuff!
Great,
Currently adding some of the more tricky metadata items (nested multi items with special attributes). Hope to get this done by the end of the week.
PS: don't worry about the MIT license. If there is another license you would prefer, just let me know.
Using the ArcGIS XML metadata allows to edit metadata for shapefiles and other datasets in the file system directly without exporting them first. For datasets in GDB copy metadata to temp file instead of exporting them (currently only works for 32bit python, crashed for 64bit python, must be a bug in arcpy). BUG fixes: If metadata element doesn't exist create it first before updating it. Add additional unittests to test other data formats