-
Notifications
You must be signed in to change notification settings - Fork 1
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
Metanorm depends on Django #23
Comments
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
Merged
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
akorosov
added a commit
that referenced
this issue
Sep 9, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Normalizers create instance of GeosGeometry and return to Harvesting, but that creates a dependency on Django. To reduce dependecies (and make Metanorm easier integrated in other software, e.g. Nansat) GeosGeometry should be created in Harvesters and Metanorm should return only strings.
The text was updated successfully, but these errors were encountered: