On sole duty keeping the office open.
December 22, 2014
I have a working embedded map, with a reduced feature set, which shows up on both the category pages and the location pages. It seems to be working perfectly, although I'm still only half-way through figuring out how the labels should work (they should not display initially, but should display when you click on a location, in lieu of the usual popup box). I have them successfully hidden, but can't figure out how to show them on click; the feature overlay has a style which is not calculated based on the feature, so you can't retrieve the appropriate text. At least, I can't yet do that.
Wrote some XSLT to generate lists of owners who are candidates for deletion because they're a) old (predating the summer data work) and b) not linked to any title as owner or seller. Sent the list to SF; on confirmation, I'll run the SQL which is also generated by the XSLT to delete those owners.
Added new fields for generation tracking:
ALTER TABLE `titles` ADD COLUMN `ttl_gen_cust` int(11) default 0 AFTER `ttl_transferdate`; ALTER TABLE `titles` ADD COLUMN `ttl_gen_noncust` int(11) default 0 AFTER `ttl_gen_cust`;
Updated local_classes.php accordingly. Tested in dev, implemented in live.
December 20, 2014
Today I fixed another wrinkle in the XML-to-OpenLayers/JSON mapping, whereby a single line-string (a straight line for a short road) was recorded as a zone/@points with only two points, but this is invalid. I've been forced to use @ulx and friends for this, as I have for the single point locations, and I've tweaked the XSLT and the map drawing code accordingly.
I also added the ability to select an existing feature and edit it, so that you can correct an error in an existing complex shape without having to redraw it completely. That seems to be working well.
Next I really want to move the LocList code out of the main module, and comment it more thoroughly.
December 19, 2014
An annoyingly long process figuring out how to encode the nested arrays to create the ol.geom.Geometry objects, but it's all now working, and the drawing interface is now generating TEI surface elements for pasting directly into XML files. There's one remaining hiccup: single-line streets generate two points, which is not enough for the TEI @points attribute, so I need to convert those (like the single-point ones) to using the four coordinate attributes instead.
Tried to wget a webpage and hand it off to grep to get a string, but had trouble doing it because the file was produced by MS Office and was a UTF-16 file (Little-endian, windows line-endings, etc.) Not sure which part of all of that was the culprit, but a utility (looks like part of a stock Ubuntu install) called iconv will take care of this.
Running this: iconv -f utf-16 -t utf-8 fixed.html |grep 'Symbola' worked a treat.
December 18, 2014
Bug in live website found right at the end of the day.
Added an explicit rotation control to the bottom of the map; tweaked label display and font sizing; made some other minor cosmetic changes. The next stage is rewriting the JSON to use our OL coords instead of SVG.
Met with SF and JS-R to discuss three main issues: the generation variables (there will be two, one for cust and one for non-cust); removal of obsolete owners, and deduping of remaining owners; and ethnicity values and assignment. Details are in my notes...
Also tested FineReader running against one of our photo-image PDFs. Took 1.5 hours, but produced a really quite impressive result from shabby typescript.