Depts

Useful feature required by GN's project, now implemented.

Downloaded and installed homebrew.
Used brew to install ant on my Mac.
Downloaded BreezeMap from github.

in build.xml set <target name="teiToGeoJSON"><arg value="-s:${proj.dir}/xml/servitengasse.xml"/> to point to my xml file

in index.html set value for var mapCentre, and for maxZoom, numZoomLevels and zoom in view object, and for numZoomLevels and maxZoom in layerXYZ object, also tried two different tilesets in the layerXYZ object (OSM default and plain grey-scale from cartodb

to start up simple http server
cd to directory (e.g. cd /Users/sarneil/Documents/Projects/gerslav/servitengasse/BreezeMap-master)
python -m SimpleHTTPServer 8000 .

to kill server session
ctrl-c in terminal window running session

to build geojson from xml data file
cd to utilities folder in the breezemap instance for the project (e.g. cd /Users/sarneil/Documents/Projects/gerslav/servitengasse/BreezeMap-master/utilities)
ant -lib .

Set up svn repo, and introduced VB to the project; he's now working on CSS for the home page.

AM and PM came by for the latter to get the former started on the next phase of the Latin site project. Copied all the requisite files over for them, and got everything installed and running.

We have three location types, and I had only allowed for two. Created a third, which involved a little reconfiguration of the JSON.

With KB, interviewed VB for the former's workstudy position; green sheet not yet available.

Implemented distinct placemarkers for the federal and non-federal ridings in preparation for the designer's input on how they should look. One obvious problem emerged: fed and non-fed ridings with the same coordinates. I've worked around it for the moment by offsetting one slightly to the left and one slightly to the right, pending input from DH and FF.

Some of the ones done before turned out to be too low-res; new ones were uploaded and I've now OCRed them and added the results to the repo.

Results now added to the repo.

Finally got around to adding HTML validation into the build process, and of course it threw up several types of error; a couple in XSLT generation, but most in encoding, especially nesting persNames (now disallowed by Schematron), and structuring tables. The HTML validator has nice feedback on the table structure, catching cases where the cell and row counts don't make sense. Fixed a whole pile of those sorts of issues, as well as one inconsistency in the taxonomy.