Reverse-engineer and document code-enforcement case API

[evankroske]

Here's the search form:

http://www3.sanjoseca.gov/codeEnforcement/cets/form_index.asp

Add the documentation to the GitHub pages site for the HackNightProjects repository, and add a link to it from index.html:

https://github.com/codeforsanjose/HackNightProjects/tree/gh-pages

[mthong]

Interesting. The City of San Jose also publishes a map of code enforcement complaints:
https://sanjosegis.cartodb.com/u/sanjoseadmin/viz/9b780252-c469-11e5-b73e-42010a14800d/embed_map

Would it negate the need to reverse engineer the API if the code enforcement dataset were posted on the data portal? (Assuming the data portal were up to the task of serving it up via API...)

[evankroske]

Even if the data were available on the open data portal via API, it's worth documenting the de-facto API of the code-enforcement case system. The case system is the system of record for this data, so if someone were building an app that needed the most up-to-date code-enforcement data, their app would have to talk to this system.