You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2019. It is now read-only.
This could even provide a link to a page that describes allowed uses for that zone if their business type is not allowed in that zone. (I believe those uses are delineated here: http://sccoplanning.com/PlanningHome/ZoningDevelopment/UseCharts.aspx ) though this may deserve a separate ticket.
The text was updated successfully, but these errors were encountered:
this is a great idea. we'll see if we can get that kind of return from the
GIS. We have actually written out practical language for each zoning
district
This could even provide a link to a page that describes allowed uses for
that zone if their business type is not allowed in that zone. (I believe
those uses are delineated here: http://sccoplanning.com/PlanningHome/ZoningDevelopment/UseCharts.aspx )
though this may deserve a separate ticket.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8.
-p
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For users that aren't familiar with zone codes, it would be very useful to translate zone codes into something human readable.
e.g. if you're using /location/check to check your business's zoning, you might enter "809 Center St" which renders
This could instead say something like
It looks like the latest translation document is http://www.sccoplanning.com/LinkClick.aspx?fileticket=J2OTGOkwoJY%3d&tabid=1427
This could even provide a link to a page that describes allowed uses for that zone if their business type is not allowed in that zone. (I believe those uses are delineated here: http://sccoplanning.com/PlanningHome/ZoningDevelopment/UseCharts.aspx ) though this may deserve a separate ticket.
The text was updated successfully, but these errors were encountered: