-
Notifications
You must be signed in to change notification settings - Fork 30
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 interval_type to isochrone objects #72
Conversation
@@ -429,7 +429,7 @@ def isochrones( | |||
intervals, | |||
type="json", | |||
buckets=1, | |||
interval_type=None, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we'll default explicitly to time
for all providers now, otherwise it could be None
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small typo, the rest looks good!
routingpy/expansion.py
Outdated
@property | ||
def interval_type(self): | ||
""" | ||
Was is based on 'distance' or 'time'? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was is based on 'distance' or 'time'? | |
Was it based on 'distance' or 'time'? |
for the network analyst it's easier if we store the
interval_type
/metric
in theIsochrone
andExpansions
objects so we don't have to pass that stuff around needlessly.PR is based on #71
also did a round of dependency updates.