Something is amiss with the Token on AppVeyor.

See new tagged release, v0.7.0
https://github.com/ODM2/ODM2PythonAPI/releases/tag/v0.7.0

TODO:

• License: ODM2/WOFpy#52;
• python-dateutil: ODM2/WOFpy#53 (see #19);
• spyne (see #19).

Hi @ocefpaf,

We need a conda package for https://github.com/ODM2/ODM2RESTfulWebServices. Thanks.

• AppVeyor (Windows 64/32)
• Travis-CI (OS X)
• CircleCI (Linux)

Now that geoalchemy-odm2 and odm2api packages have been renamed on the anaconda channel, please remove the versions with the old names: geolachemy & odm2pythonapi.

And dateutils, once we get definitive confirmation that it's not used.

Update odm2api to the new v0.5.0-alpha release

Re-encrypt and point them to the new repository.

• AppVeyor
• CircleCI
• Travis-CI

I finally pushed this release out !
https://github.com/ODM2/WOFpy/releases/tag/v2.3.0

Package away as soon as possible, please. Thanks!

cc'ing @lsetiawan so he's directly in the loop.

Ready for a 0.5.3- alpha release.

Create a new ODM2API conda release.

The builds are failing because the tag disappeared. I guess we should delete the binaries and use the new tag.

https://github.com/ODM2/ODM2PythonAPI/releases

FYI, about the ODM2PythonAPI package:

• We haven't created (pre)releases yet. We had a discussion about it on Friday, with pro and con opinions. Hopefully this coming week we'll create a first pre-release, taken from master.
• Another group in our distributed team has started exploring creating a pypi package. Currently in testing at https://testpypi.python.org/pypi/odm2api. I'm not sure yet if the conda recipe should shoot for using that vs a tagged pre-release on the github repo; I think I prefer the latter, for now.
• There's been a lot of overhauls and cleanups in the last two month and a half, currently all in branches. No timeline yet for merging into master.

Update odm2api to the new v0.5.2-alpha release

ODM2PythonAPI is the repository name and the package should be odm2api.

We should turn this into documentation later on. For now, just a collection of notes about how conda packages are updated.

Requesting an update:

Create an issue in this repo. Initially @ocefpaf will handle updates. Later on, hopefully others (myself included) will be able to do the updates, too.

What happens next?

@ocefpaf will update the recipe meta.yaml file. He'll I send a PR from a fork, wait for a "green" build and merge. The upload to the channel is automatic after the merge.

From @valentinedwv over at ODM2PythonAPI/issue 49:

For YodaTools, can you add this package to conda: valideer

Dave, is YODA-Tools in good shape for preparing a conda package? It doesn't look that way to me. Or are you just asking to have valideer, not YODA-Tools, added to the ODM2 anaconda channel, for now, b/c it would help you with YODA-Tools development? I assume it's the latter, which seems much easier.

@sreeder asked me this question after last Friday's conda discussions with @ocefpaf:

We have been discussing how we would like to package our ODM2StreamingDataLoader project, and the idea of using a conda package has come up. I was under the impression that conda packaging is used for python libraries that you would be accessing from code. I am curious if using conda packaging is a viable approach for a Desktop application with a GUI. Would there be a simple way for a nearly computer illiterate user to download, “install”, and run a project that was packaged with conda?

I thought about it a bit, but don't have an answer. I've never dealt with this situation. So I'm posting it here to see what @ocefpaf and others think.

My hunch is that conda could help with the development process. Then you could use one of the Python tools to create self-contained executables (probably OS-specific) to create easy-to-install distributions (eg, this and that?). But this is out of my depth.

https://github.com/miguelcleon/odm2djangoadmin

@miguelcleon is the developer of this terrific ODM2-based tool (a web-based UI to an ODM2 PostgreSQL database, using Django). @ocefpaf (Filipe), three of us ODM2 leads had a great conference call with Miguel earlier today, where he demo'd odm2djangoadmin. I offered for you and I (mostly you, of course) to work with him to help him package odm2djangoadmin and then create a conda package on the odm2 anaconda channel. I said we'd start connecting early next week, and made it clear that we'll be asking him to do some work in tweaking his repo to make it more readily installable. He's on board.

As additional background, a couple of weeks ago Miguel shared this (edited from an email of his):

graphs for soils data I’ve developed
http://lczodata.com/ODM2/ODM2CZOData/chartVariableAndFeature.html

We have about 2.4 million data values now in our ODM2 database and over 11,000 soil measurements.

EDIT: Here's the presentation Miguel gave us today

Can we do a proto travis scripts to pull the conda distribution so that we could use them for testing and development... aka dogfood.

We can. I can send a PR your way or point to an example.

Then maybe we can incorporate this into other travis scripts.

Which would be the first repository to use it?

@valentinedwv, can you open a separate issue for this? I'd like to keep this issue focused on just documentation on how the process works. If what you and @ocefpaf end up doing is relevant to how the conda recipes & packages are created and updated, then it'll be great to have notes from that process added here. Thanks.

All the work has pretty much already happened (thanks @ocefpaf!!); I'm just creating this issue as a reference point, and also to help track tests that confirm that everything is working fine off conda-forge.

PR's on the ODM2 end of things that addressed this transition (and are already merged):

• ODM2/ODM2PythonAPI#148
• ODM2/YODA-Tools#34
• ODM2/WOFpy#225
• ODM2/CZ-Manager#201

Plus a bunch of PR's over at conda-forge.

The ODM2 conda channel is at https://anaconda.org/odm2/

Ping @emiliom should we do that?

New release at https://github.com/ODM2/ODM2PythonAPI/releases/tag/v0.7.1

@ocefpaf, is the plan to continue to use this repo to request new conda packages, or should we create request issues somewhere on conda-forge? Say, for odm2api, is https://github.com/conda-forge/odm2api-feedstock the repo where we'd submit request issues?

Thanks!

cc @lsetiawan

@emiliom I am creating a list of the recipes here. Please edit the list and move the recipes up/down according to your priorities.

First priority (order reflects priority, top to bottom)

• ODM2PythonAPI
• geoalchemy (ODM2 fork)
• WOFpy (ODM2 fork) - ODM2 is now the official source of WOFpy
• odm2admin. Note that this repo/package is not under the ODM2 github organization.
• ODM2RESTfulWebServices

Others (to be prioritized later)

• ODM2WebSDL
• ODM2
• ODM2StreamingDataLoader
• ODMToolsPython
• ODM2ControlledVocabularies
• YODA-File
• YODA-Tools

Source: https://github.com/ODM2

See conda-tools/conda-build-all#70