Skip to content
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.

Sign up for GitHub

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

Jump to bottom

costdistance Python API should accept a vector mapop for points #348

Open
djohnson729 opened this issue Jul 1, 2016 · 1 comment
Open

costdistance Python API should accept a vector mapop for points #348

djohnson729 opened this issue Jul 1, 2016 · 1 comment

Comments

@djohnson729
Copy link
Contributor

Currently, the Python API for costdistance only accepts a series of long/lat point pairs as input for source points. It should also accept a vector MapOp.
@ericwood73
Copy link
Contributor

I'll take this one

ericwood73 added a commit to ericwood73/mrgeo that referenced this issue Sep 16, 2016
@ericwood73
Added signature to CostDistanceMapOp that takes a vector of source po…
0a45545 
…ints (Issue ngageoint#348)

Added unit test for CostDistanceMapOp and modified some of the supporting test classes to support this test.  Also added a python unit test for costDistance.  This test is incomplete because of an issue running python tests right now that the test runner is called unitest.main with an unrecognized verbosity argument.  May be an environment issue.

Signed-off-by: ericwood73 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ericwood73 @djohnson729