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
User can click on, search for, route to Commercial Overlays. Details link to handbook info. #309
Comments
Use the tooltip for the summary text. Unblocking… |
@allthesignals I think we should close this as wontfix. You can already get to Commercial Overlay details from the lot view. We need to establish rule for why something is routable. I don't think "so you can link externally" is a good reason for something to be routable. Special Purpose districts are routable because you can search for them, which is a good reason. Objections to closing this? |
It’s weird to me that people would be able to search for nearly every zoning district except for C1 and c2 overlays which are some of the most important in the ZR. Why this one as opposed to any of the others?
…Sent from my iPhone
On Oct 20, 2017, at 10:02 AM, Andy Cochran <notifications@github.com<mailto:notifications@github.com>> wrote:
@allthesignals<https://github.com/allthesignals> I think we should close this as wontfix. You can already get to Commercial Overlay details from the lot view. We need to establish rule for why something is routable. I don't think "so you can link externally" is a good reason for something to be routable. Special Purpose districts are routable because you can search for them, which is a good reason. Objections to closing this?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub<#309 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AelYL3doeiR6GoIEJSqHfmr7ZKiIewPtks5suNIdgaJpZM4P2CeA>.
|
Thanks, @fruchala. That's a good reason for making COs routable AND searchable. |
How should routing working for this? Is it feature-level or...? |
Addresses #309 by making it routable.
Need to get some summary text so we can display it on the route.
The text was updated successfully, but these errors were encountered: