Closed MrMaksimize closed 8 years ago
These appear to be fields from the Code Enforcement application.
•CaseId -- this would be the Code Enforcement Case ID number •CaseDepiction -- I'm not sure what this stands for. I'm checking with Jim Myers to see if there is a document that describes all of the field labels. •SortableStreetAddress -- it looks like this puts the Street Name first, and the street number after so that it can be sorted in a list •APN -- this is the Assessors Parcel Number •Mapreference -- I believe this is the Thomas Bros. Map Code
Here's more info on the Code Enforcement XML dataset: http://www.sandiego.gov/development-services/opendsd/codenforcement.shtml
I should probably provide a brief overview of the info in Open DSD - this is oversimplified, but may help to describe things.
There are essentially three parts of the system:
Code Enforcement is primarily complaint driven and consists of complaints, which are entered in the system as Cases and assigned a Case Number and an Investigator. The investigator takes a series of steps, such as sending out an initial notice, investigating the site/research, etc. Various timelines and reminder/follow-up dates are provided for follow-up and action toward correcting the complaint before the case is eventually closed.
Ministerial permits (Process 1) are generally construction permits which are obtained via a Staff-level/other-the-counter type decision. These can include things like building permits, right-of-way permits, etc.
Discretionary permits consist of projects where a Process 2 or higher decision is required before a construction permit/ministerial permit can be issued.
Process 1 - staff decision Process 2 - staff decision, may be appealed to Planning Commission for a final decision Process 3 - Hearing Officer hearing, may be appealed to Planning Commission Process 4 - Planning Commission decision, may be appealed to City Council Process 5 - City Council decision (receives a Planning Commission recommendation first)
I can provide more information about specific areas/questions
Would it help if we summarized everything in a single doc to help describe... like this:
OpenDSD Website Search by Data Tips
There are essentially three parts of the system:
Code Enforcement Cases map search Code Enforcement is primarily complaint driven and consists of complaints, which are entered in the system as Cases and assigned a Case Number and an Investigator. The investigator takes a series of steps, such as sending out an initial notice, investigating the site/research, etc. Various timelines and reminder/follow-up dates are provided for follow-up and action toward correcting the complaint before the case is eventually closed.
Dataset Information Dataset Legend CaseId -- this would be the Code Enforcement Case ID number CaseDepiction -- I'm not sure what this stands for. I'm checking with Jim Myers to see if there is a document that describes all of the field labels. SortableStreetAddress -- it looks like this puts the Street Name first, and the street number after so that it can be sorted in a list APN -- this is the Assessors Parcel Number Mapreference -- I believe this is the Thomas Bros. Map Code
Ministerial Permit Approvals map search Ministerial permits (Process 1) are generally construction permits which are obtained via a Staff-level/other-the-counter type decision. These can include things like building permits, right-of-way permits, etc.
Discretionary Permit Approvals map search Discretionary permits consist of projects where a Process 2 or higher decision is required before a construction permit/ministerial permit can be issued.
Development Processes Summary Process 1 - staff decision Process 2 - staff decision, may be appealed to Planning Commission for a final decision Process 3 - Hearing Officer hearing, may be appealed to Planning Commission Process 4 - Planning Commission decision, may be appealed to City Council Process 5 - City Council decision (receives a Planning Commission recommendation first)
This should be written into an MD file within the repo. @ahempton or @jerryHall is this something you'd be willing to do?
Temporarily assigning to myself, while we find someone who can push this forward.
What is an MD file? Metadata?
Markdown. Same as RST (restructured text). @jerryHall 's post above uses the necessary syntax, as does the README.md from this repo. I think @MrMaksimize has some instructions above as well.
Got it - thanks
I'm trying to get more familiar with GitHub... Trying to respond to requests of me but I feel like I might be missing some of them
On Jan 7, 2016, at 12:56 PM, Ben Cipollini notifications@github.com wrote:
Markdown. Same as RST (restructured text). @jerryHall 's post above uses the necessary syntax, as does the README.md from this repo. I think @MrMaksimize has some instructions above as well.
― Reply to this email directly or view it on GitHub.
OK, I followed @MrMaksimize 's instructions and added info this to the file: https://github.com/opensandiego/open-dsd-notifications/blob/master/dsdDescriptions.md
I also linked the file from README.md. So, we're done here :)
Please see below for some of the data coming in from the OpenDSD endpoint.
The problem is -- we don't fully understand what a lot of these things mean. Namely:
In addition, I don't fully understand what is the difference between the various code violations / approvals/ ministerials approvals and other object types on OpenDSD.
IMO this should be documented.
We need to provide a description in a file in the repo
I created a file here: dsd-description And here's how you can edit it (you have to be logged in and have access to the repo).