collapse

M4OPS

For our prototype mapping system try the Demo at mapping4ops.org/M4OPS.

You can also view a demo and discussion about M4OPS on YouTube.

* Forum Staff

PeterC admin PeterC
Administrator
admin webmasterOPS
Administrator

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.


Topics - PeterC

Pages: [1] 2 3 ... 30
1
An example of one of Peter Watson's Valuation transcripts for Herne Bay in Word document format is attached to this post.  It comprises separate tables, one for each property in the 1910 Valuation, interspersed by some images to help remind about the property. For convenience each document contains a limited number of properties (eg 100), and this example shows just a few.

Each table has the following data for each property:
  • ValuationID
  • Situation
  • Description
  • Gross Value (£ and optionally shillings and pence)
  • Occupier
  • Owner
  • Former Sale - the date the property was last sold, and hopefully the amount of sale, + additional cost (eg if it was bought as land, then a house built in it)
  • Particulars

Broadly speaking the stages of the process are:
  • Manipulate the Word Documents to prepare a single table of data
  • Convert this table into a list of features for M4OPS
  • Add the All Features layer
  • Upload and compile
  • Georeference the Features

Manipulate the Word Documents to prepare a single table of data:
  • In Word, create a new landscape document
  • For each transcript document: Select all, copy and paste onto the end of this landscape document (selecting the default - destination theme)
  • To remove header lines: Select all of style Title and delete
  • Use Replace All various times:
    • Images: ^g to null
    • Manual line breaks: ^l to space
    • Tabs: ^t to space
    • Semicolons: ; to #semicolon#
    • [(unnecessary?)Extra paras: ^p^p to ^p – repeat until 0 (any left delete manually)]
    • Single paras: ^p to null
  • Select all, cut and paste as text only
  • Select all and insert table (Convert: paragraphs, 5 columns, Autofit contents)
  • Check for changes in pattern, and for each: Undo, adjust redo
    • [eg in the attached document there is an issue after id 63]
  • Delete the blank column
  • Convert to text (separate text with tabs)
  • Select all and insert table (Convert: tabs, 8 columns, Autofit contents) – if not 8 then undo, resolve issue, and redo
  • Save the document

Convert this table into a list of features for M4OPS:
  • Convert to text (separate text with semicolons)
  • Select all, copy and paste into a blank Features.csv text file
  • Replace ;space by ;
  • Copy the following string and paste it at the beginning of this file
    • ID;Situation;Description;GrossValue;Occupier;Owner;FormerSale;Particulars
  • Save the file as Features.csv

Other notes to be considered
Use ID rather than ValuationID
Each one preceded by V
remove blank lines
Comment Date
Needs to be shorttext and featureid?
Need Lon(X);Lat(Y);GeomType;GeomCoords


See Compiling Features for the next stage.

2
M4OPS - for those responsible for an OPS / Compiling Features
« on: 12 April 2018, 12:37:27 »
Once a list of un-georeferenced features has been prepared in a Features.csv file (eg from The Journal or transcripts), then the next stages of the process are:
  • Add the All Features layer
  • Upload and compile
  • Georeference the Features
(If not already done) Add the All Features layer to the LayerDefs_Feature.csv file:
  • Whereas other processes may be done more than once, this one is done just once
  • Where the fieldnames are
    layertype;category;title;csvname;candownload;url;attribution;mapkey;minx;miny;maxx;maxy;shorttext;description;fl_Ncols;flhead_col1;layerdescription
  • the All Features layer entry is
    Vector;Local;All Features;AllFeatures;TRUE;AllFeatures.geojson;#PDC#;;;;;;;;1;;These are all the features as we have recorded them.
Upload and compile:
  • In M4OPS for your OPS (first Dev then, when tested, Production):
  • Click on the Upload Tab
  • Click on Choose Files, Browse to the folder where your csv files are located
  • If you have updated the LayerDefs_Feature.csv file:
    • Select the LayerDefs_Feature.csv file and click on Open
    • Click on Upload, and (if necessary) provide the password
    • When the Uploaded OK message appears click on OK
  • As you have updated the Features.csv file:
    • Select the Features.csv file and click on Open
    • Click on Upload, and (if necessary) provide the password
    • When the Uploaded OK message appears click on OK
  • Click on Compile
  • When the (detailed) compilation results message appears click on OK or Cancel
  • (As after every Compile) Clear your browser cache, and reload M4OPS

See Georeferencing Features for the next stage.

3
To process a new version of the SOPS' Studies spreadsheet:
  • Go to https://drive.google.com/drive/shared-with-me and right-click/download the latest StudiesYYYYMMDD.xlsx file to the Mapping\Software\M4OPS folder
  • Open the downloaded file in Excel, and enable editing
  • File/Save As Text (Tab delimited) (*.txt) for the Active Sheet only
  • Exit Excel
  • Rename the file as StudiesYYYYMMDD.xlsx - Active.tsv (tsv is our name for Tab Separated Values)
  • Open this file in an editor and
    • delete all the empty rows at the end of the file
    • check there are no semi-colons in the file (and if there are change them)
    • change all tabs to semi-colons
    • delete all the excess semi-colons at the end of lines
    • Encoding - click on Convert to UTF-8, save and reload to check it is still encoded as UTF-8 (as json needs this)
  • FTP the .tsv to /ShowMapsDev/
  • On /ShowMapsDev/ rename the old Studies.csv as StudiesOLD.csv (having deleted any previous OLD versions)
  • On /ShowMapsDev/ rename the .tsv file to Studies.csv
  • Open mapping4ops.org/ShowMapsDev/CompileStudies.php?BRs&Test to precompile the Studies.json file
  • Make sure that the only OPS listed as "Location not set from Studies.csv" are those we know of (eg BAL, BRI, POR, USG, EDI, LGIWG), or for which we have not yet compiled the OPS.json file
  • (If there are problems later you may want to check the resulting Studies.json file)
  • On our local M4OPS rename the old Studies.json as StudiesOLD.json (having deleted any previous OLD versions)
  • FTP Studies.json from /ShowMapsDev/ to our local M4OPS
  • Test M4OPS, and when happy all is OK, FTP Studies.json from our local M4OPS to /ShowMaps/ (ie the production M4OPS system)
  • (Note that there is no need to repeat the precompile process on the production system, as all that M4OPS needs is the Studies.json file)
  • Test the production M4OPS

4
Feature Layer Technicalities / What is AllFeatures?
« on: 5 March 2018, 07:34:40 »
This is a technical note about the use of AllFeatures.geojson and Features.csv within M4OPS.

The Features.csv file contains detail of Features, each of which has a featureid. These can be referenced just by their featureid within other feature csv files (eg Pubs.csv).

If there is an AllFeatures.geojson line within the LayerDefs_Feature.csv file that specifies AllFeatures as the csvname, then FLG.php will compile all the features it can find (that are georeferenced and have a featureid) into an AllFeatures.geojson file. If no such features are found then one point at the centre of the box defined in the OPS, with featureid=F_OPS, is generated - and this should be deleted when there are other points.

To compile AllFeatures.geojson FLG.php will look in Features.csv as well as all the other feature csv files it is told about. Any features in Features.csv that have no geometries are called 'Features still to be Georeferenced'.

AllFeatures.geojson can be opened within M4OPS either as:
  • a Feature Layer - where it cannot be changed
  • a Modifiable Feature Layer - where it can be changed
As an MFL AllFeatures.geojson can be altered in the usual ways using Alter/Move, but it can also be added to by georeferencing 'Features still to be Georeferenced'.  Note that AllFeatures.geojson is stored in the main OPS folder, not in SavedFiles where the normal MFL geojsons are stored.

When the MFL AllFeatures is saved then besides being saved as AllFeatures.geojson a new version of Features.csv is saved - comprising both georeferenced and non-georeferenced features. This can be downloaded onto the user's computer if wanted.

5
The LIDAR layers from the EA are already defined in DefinedLayerDefs_Other.csv, so for a particular OPS all that is necessary is to add pointers to the required defined layers into the LayerDefs_Other.csv file. The process is:
  • Go to the Government's list of DTM LIDAR feeds
  • For 'LIDAR Composite DTM - 2m' click (on the right) Preview on Map
  • Repeat this for:
    • 'LIDAR Composite DTM - 1m'
    • 'LIDAR Composite DTM - 50cm'
    • 'LIDAR Composite DTM - 25cm'
  • Now you have 4 maps in the Preview List on the left, click on Preview Maps
  • In the map, zoom in and find your OPS
  • Find the best (smallest) resolution available for your OPS, by:
    • On the left, turn on the 25cm layer (click to put tick into little box), and wait
    • If no LIDAR map appears, turn on the 50cm layer and again wait
    • Again if no LIDAR map appears, repeat the process for the 1m and, possibly, 2m
  • In your LayerDefs_Other.csv enter a row like (if 1m was the best resolution):
    • Defined;Lidar;EA 1m DTM LIDAR;Terrain (DTM)
  • Repeat the whole process for DSM instead of DTM
  • Then (as usual) upload, recompile, clear cache and refresh M4OPS

6
CMS are about managing archives etc, and the following are some web pages I found from a cursory scan of possibly useful software systems (that I did for a colleague in early 2018). I had not realised how huge an area this is (and bear in mind I know very little about this area).

Possibly useful advice
http://www.nationalarchives.gov.uk/archives-sector/advice-and-guidance/managing-your-collection/documenting-collections/cataloguing-and-archives-networks/
http://collectionstrust.org.uk/what-we-do/
http://carlibrary.org/CMS.htm

Free systems
http://www.collectiveaccess.org/
http://www.adlibsoft.com/products/adlib-museum-lite
http://www.collectionspace.org/
http://www.musarch.com/
http://oedb.org/ilibrarian/5-free-and-open-source-tools-for-creating-digital-exhibitions/
https://www.gallerysystems.com/resources/free-resources/
https://sumac.com/collection-management-software/ (free upto a limit)

Commercial systems that might have reasonable offers for a small museum
http://alm.axiell.com/ incl CALM http://alm.axiell.com/collections-management-solutions/technology/calm-archive/
https://www.townswebarchiving.com/archive-management-software/pastview/
https://lucidea.com/ils-solutions/genieplus-ils/
https://archive-it.org/
https://www.soutron.com/products/digital-media-archive/
https://www.communitysites.co.uk/ - used by eg http://www.ccan.co.uk/
http://www.modes.org.uk/ - but no web aspect

Reviews
https://www.capterra.com/museum-software/
https://granitehorizon.com/blog/a-side-by-side-comparison-of-museum-collection-management-platforms-collectionspace-vs-pastperfect/

7
M4OPS - for those responsible for an OPS / Colouring Feature Layers
« on: 10 February 2018, 12:46:45 »
If a feature layer has a property that varies that you want to use to colour/color features differently, here is how to create a block of conditions to specify that colour scheme:
  • In the Colours.csv file enter a block of lines that have the following fields:
    • csid: the id of the colour scheme (must be identical for all rows in this block)
    • title: the name of the colour scheme to appear in the dropdown (identical for all rows in this block, except that only the first is used)
    • keytitle: title to appear in the key (identical for all rows in this block, except that only the first is used)
    • fproperty: the feature property to be evaluated
    • comparetype: the comparison operator (<, >, =, <=, or >=)
    • comparevalue: the value to be compared with
    • keyphrase: the phrase to be used in the key before the comparevalue
      • (If the keyphrase starts with * then the comparevalue is not appended to it in the key)
    • colour: the specification of the colour as either:
    • comment: can be used for any comment, eg what the colour is
  • Make sure all the lines (conditions) for the same csid are kept together, and that they are in the right order (because the first that evaluaates to true will be used)
  • It is useful to end each block with a condition with ;;;Unknown for fproperty;comparetype;comparevalue;keyphrase so there is a Catch-all value
  • Otherwise, if no condition is met, the default colour is used
More than one colour scheme can be in the file, each represented by a block of conditions. The possible colour schemes for feature layers appear in a drop down beside the "Feature Layers" title. When one is chosen the features are coloured according to it, and a key appears.

Useful colours are:
Colour    rgb
To do    ???

Useful help on colours can be found in:

8
To create a layer of features for an OPS extracted from OSM do the following:
  • Open Overpass Turbo
  • Navigate to the OPS study area
  • Click on the 3rd icon down in the group on the left (manually select bbox)
  • Move the boundaries of the bbox to the best fit for the OPS
  • Open the Wizard
  • Enter the following into the Wizard building or ~"addr"~"\\w" - ie every feature that has either:
    • the building tag set (to any value), or
    • any tag containing addr set (to any value)
  • Click on Build Query
  • Click on Run
  • Click on Export
  • Click on download as GeoJSON
  • Saving the file in the appropriate place on your computer, and named OSMyyyymmdd.geojson (eg OSM20180209.geojson)
  • You can now close Overpass Turbo
  • Upload the OSMyyyymmdd.geojson file into M4OPS
  • Edit the LayerDefs_Feature.csv, and set special fields to:
    • mapkey to #OSMData#
    • shorttext to name?addr:housename?addr:housenumber
      • (this defines the equivalency of the shorttext field, so that if the field does not itself have a value then it is set to the value of the equivalency)
      • (the ?s indicate that if the first field in the list does not have a value then the next is evaluated etc)
    • description to shop?amenity?addr:street
    • fl_Ncols to 2
    • flhead_col1 to Building
    • flhead_col2 to Street
    • fl_col2 to addr:street?addr:postcode
    • textforsort to fl_col2&#ZZZ&fl_col1
    • layerdescription to #Overpass#
  • Upload the LayerDefs_Feature.csv file into M4OPS, and Compile
  • Clear the cache and refresh M4OPS

For more information see:

9
M4OPS - for those responsible for an OPS / Georeferencing Features
« on: 24 January 2018, 10:28:15 »
If you have a list of features (eg from The Journal or transcripts) within M4OPS that are not georeferenced, and have compiled them, then the next stage of the process is to georeference them. Essentially what you are doing is associating a geometry (a point, line or polygon) with each feature. M4OPS makes this easy for you.

Within your OPS in M4OPS:
  • For the Base layer select as large a scale map as possible (of around the best date), so your georeferencing can be as accurate as possible
    • You may also wish to select an overlay layer - and slide between the Base and Overlay - or remove the Overlay altogether (use the little 'x')
  • Move and zoom the map so you can see the places for the features you want to georeference
  • Under Advanced Options, click on the MFL tab
  • In the drop-down for Modifiable Feature Layers choose the All Features layer, and what should appear are
    • the points and polygons of the georeferenced features so far
      • [Note that if no features have so far been georeferenced, there will be one point showing named 'OPS - Centre', which is the centre of the OPS] - this point is there to show the layer exists, and can be deleted once you have started georeferencing]
    • a list of features still to be georeferenced
    • running totals of (georeferenced) features in the layer and features still to be georeferenced
    • [Note that the Base, Overlay and Feature sections disappear to allow more room for this process.]
  • Select the appropriate set of Fields from the drop-down (these are the predefined properties or values stored for each feature, including any optional ones) - NOT All Properties
  • Now to georeference each feature:
    • In the drop-down, select the feature still to be georeferenced
    • (If not already done so) select the Point, Line or Polygon button
    • Create the geometry, ie:
      • for a point, click once on the map
      • for a line, click at least once on the map and then double-click for the last point
      • for a polygon, click at least twice on the map and then double-click for the last point
    • When a popup appears
      • in the drop-down confirm (or change) the feature you want to georeference
      • click on Save
      • click on Close
    • [You will then notice that the feature appears on the map, and disappears from the list of features still to be georeferenced - the totals also change]
    • [If you click on Close without Saving the whole operation is cancelled]
  • At any time you can hover over georeferenced features to see their details
  • At any time you can move the positions of any of the points, or the vertices of polygons
    • Click on the Move button, and then drag the points to exactly where you want them
  • At any time you can change the properties of any feature, delete it, or change its type of geometry (point, line, polygon)
    • click on the Alter button
    • click on the feature you want to change
    • if you want to delete the feature, click on the Delete button
    • otherwise, fill in the form - remembering to Save the form before you Close it
  • Periodically, and when you have finished, click on the (MFL) Save button on the left to save All Features in M4OPS (you can do this as many times as you want)
  • When finished click on the Close button, and the MFL will disappear
  • You can restart the process from the saved position at any time (but you may need to clear your browser's cache and reload M4OPS first for it to recognise your latest alterations)
Once the features are georeferenced please talk to Peter about downloading the Features files and recompiling your OPS within M4OPS.

10
M4OPS - Technicalities / The input CSV files-2
« on: 21 January 2018, 15:21:05 »
Note that this is mostly for technical information.
It is the second part of the document about the input csv files.


For each OPS in M4OPS

Input files
All files are in csv format using semi-colon ";", rather than comma, as the separator. No fields can have semi-colons within them, but they can have commas. (On Peter's PC all csv files are within eg \OPS\HcN Holywell-cum-Needingworth\FLG\.)

Every file has field names in its first row, and these field names must be as specified (in the correct case). No quotes are needed for field names or values. Any null or blank values should be left null, ie represented as ;;.

Any blank lines, any starting with the word “Comment”, and any starting with the first field name (thereby allowing a repeat of the first row of field names), are ignored. If you use Excel for accuracy then ensure that the delimiter is set to ";".

These csv files are used to generate geojson and json files, which are what M4OPS to use directly as its input.

Further optional files are:
  • Features.csv - a list of all the features known to the OPS (which can then be referred to by Feature Layers)
    • It must have the following fields
      • featureid - string value by which this feature is referred
      • shorttext - name of the feature, displays on the map when resolution is OK, and in the display panel
    • It must also have one of the following geometries
      • a pair of coordinates corresponding to a point
        • Lat(Y) - numeric (eg 52.32)
        • Lon(X) - numeric (eg -0.03)
      • a geometry specification, comprising:
        • GeomType - Point, LineString, or Polygon
        • GeomCoords - a CoordinateString, eg:
          • for a Point: [-0.03, 52.32]
          • for a LineString: [[30, 10], [10, 30], [40, 40]]
          • for a Polygon: [[30, 10], [10, 30], [40, 40], [30, 10]]
        • always Lon/Lat in decimal degrees - known as EPSG:4326
        • see https://en.wikipedia.org/wiki/GeoJSON for other examples
      • Note that the following are the same point:
        • Lat(Y)=3 and Lon(X)=5
        • GeomType=Point and GeomCoords=[5,3]
      • Note also that we use the field name Lat(Y) for latitude to remind ourselves that in mathematics this is the Y-axis, and similarly Lon(X) as longitude is the X-axis
    • It can have any of the following fields (these correspond to those listed under the PROPERTIES for the GeoJSON file, and become the defaults for all Feature Layers)
      • description - html that displays in the display panel, (default is shorttext)
      • datestart - date from which this feature is to be shown in ISO Format - YYYY-MM-DD, eg 1888-03-25, or 1910 (default 0000-01-01)
      • dateend - date after which this feature is not to be shown (ditto) (default 9999-12-31)
      • internalnote - for internal use eg as a reminder – not displayed anywhere
      • fl_col1 - used as the value in the first column in the feature list, if undefined shorttext is used
      • fl_col2 - used as the value in the second column in the feature list
      • fl_col3 - used as the value in the third column in the feature list
      • textforsort - used for sorting the feature list, if undefined then the value of fl_col1 is used
      • image - the relative filename of an image associated with the Feature (in the Images subfolder)
      • html - the relative filename of a web page associated with the Feature (in the HTML subfolder)
      • pin - pin number - see the available pin styles
      • symbol - name of the icon to use - see the available A-M and N-Z icons
      • color - colour of the circle - see the full range of colours available (default is red)
      • radius - size in pixels of the (filled) circle (default is 5)
  • People.csv - a list of all the people known to the OPS (which can then be referred to by Feature Layers)
    • It must have the following fields
      • personid - string value by which this person is referred (becomes xrefid in the JSON file)
      • shorttext - name of the person (becomes xl_col1 in the JSON file)
    • It can have any of the following fields
      • textforsort - if undefined xl_col1 (shorttext ) is used
      • xlhint -  the hint on hover over the person in the list (eg Birth)
      • datestart - date (eg Birth) from which this person is to be shown in ISO Format - YYYY-MM-DD, eg 1888-03-25, or 1910 (default 0000-01-01)
      • dateend - date (eg Death) after which this person is not to be shown (ditto) (default 9999-12-31)
      • image - the relative filename of an image associated with the Person (in the Images subfolder)
  • Abbreviations.csv - a list of all the abbreviations specific to this OPS
    • It must have the following fields
      • abbcode - the text to be replaced (by convention usually starts and ends with '#')
      • abbhtml - the text by which it is to be replaced
  • Exclusions.csv - a list of all the layers from the Area of the OPS that should be excluded
    • It must have the following fields
      • category - of the layer to be excluded
      • title - name of the layer to be excluded
For more input csv files see The input CSV files and The input CSV files-3

11
M4OPS - Technicalities / The input CSV files-3
« on: 21 January 2018, 15:17:20 »
Note that this is mostly for technical information.
It is the third part of the document about the input csv files.


For each (optional) Feature Layer in each OPS in M4OPS
All files are in csv format using semi-colon ";", rather than comma, as the separator. No fields can have semi-colons within them, but they can have commas. (On Peter's PC all csv files are within eg \OPS\HcN Holywell-cum-Needingworth\FLG\.)

Every file has field names in its first row, and these field names must be as specified (in the correct case). No quotes are needed for field names or values. Any null or blank values should be left null, ie represented as ;;.

Any blank lines, any starting with the word “Comment”, and any starting with the first field name (thereby allowing a repeat of the first row of field names), are ignored. If you use Excel for accuracy then ensure that the delimiter is set to ";".

These csv files are used to generate geojson and json files, which are what M4OPS to use directly as its input.

The required files  (using the example of a Feature Layer called “Censuses”) are:
  • Censuses.csv - a list of all the features known to the OPS used in this Feature Layer
    • It must have either:
      • featureid - Required, string, corresponds to the featureid in Features.csv, or
      • one of the geometries listed above under Features.csv
    • It can have any of the other fields listed above in Features.csv (except the geometry - see above), and, if present, these values then override the values in Features.csv
    • Note that if no featureid is given then it must have a shorttext
    • Note that if a featureid and an override shorttext is given then you may also need to give an override fl_col1
The optional files are:
  • Censuses_Events.csv - a list of all the events listed for all the features used in this Feature Layer
    • It must be sorted by featureid, and then in the order you wish them to appear (eg by evdateend)
    • It must have the following fields
      • featureid - Required, string, corresponds to the featureid in Features.csv
      • evshorttext - the short summary heading for the event
      • evdatestart - date from which this event is to be shown in ISO Format - YYYY-MM-DD, eg 1888-03-25, or 1910 (default 0000-01-01)
      • evdateend - date after which this event is not to be shown (ditto) (default 9999-12-31)
      • evdescription - a full html description of the event
    • Note that this requires a featureid and must therefore be in Features.csv
  • Censuses_People_Events.csv - a list of all the events listed for all the people and features used in this Feature Layer
    • It must be sorted by personid, and then in the order you wish them to appear (eg by evdateend)
    • It must have the following fields
      • personid - Required, string, corresponds to the personid in People.csv
      • featureid - Required, string, corresponds to the featureid in Features.csv
      • evshorttext - the short summary heading for the event
      • evdatestart - date from which this event is to be shown in ISO Format - YYYY-MM-DD, eg 1888-03-25, or 1910 (default 0000-01-01)
      • evdateend - date after which this event is not to be shown (ditto) (default 9999-12-31)
      • evdescription - a full html description of the event
  • Censuses_People_Specs.csv - contains the fields specifying the person and results lists
    • It can have the following fields
      • XRefName - (default People)
      • fnresultsHead - the html heading text for each Person (where the text "xrefid" is replaced by the personid)
      • fnresultsBody - the html body of text for each Person (ditto)
      • fnresultsevHead - the html heading text for each event (ditto)
      • fnresultsevBody - the html body of text for each event (ditto)
      • xl_Ncols - the number of columns to be shown in the People list (default 1)
      • xlhead_col1 - the heading for the first column of the People list (default is blank)
      • xlhead_col2 - ditto column 2
      • xlhead_col3 - ditto column 3
   
For more input csv files see The input CSV files and The input CSV files-2

12
The Journal by DavidRM (TJ) is a fairly free format journalling system. Entries can either be linked to dates, or loose-leaf.

The following assumes that you have created a loose-leaf category (eg Directory) in The Journal (TJ) v7, with entries that are Roads, under which are subentries that are dwellings along that road. Each entry and subentry must be given a name and a reference (which should be a unique set of alphanumerics). The fact it is a reference (or id) is indicated by it either being enclosed in parentheses, or being preceded by #.

For example you could have (although consistent referencing would be better):
  • Albany Road #R1
    • 1 (24)
    • Owl House (21)
  • Beach Road #R3
    • 24a (SE2)
    • 24b (SE3)

Within M4OPS the dwellings will be called Entry (ref) - subentry (ref), or subentry, entry. The reason for the reference is just to make (sub)entries unique and clearly identified. Thus eg Owl House will be called "Albany Road #R1 - Owl House (21)", or "Owl House, Albany Road".

Within The Journal (TJ) each entry has a page where you can enter text, tables, images etc. The purpose of the process below is to make these pages available to M4OPS so you can see them when you hover over, or click on, a feature in M4OPS. It is best if you do not format your TJ pages too much as at the moment this can confuse M4OPS.

[Note that when we talk about HTML files below we include their associated image (jpeg) files.]

Broadly speaking the stages of the process are:
  • Create HTML files from The Journal (TJ)
  • Upload the HTML files to M4OPS
  • Create the list of features for M4OPS
  • Add the All Features layer
  • Upload and compile
  • Georeference the Features

Create HTML files from The Journal (TJ):
  • Create a folder for the HTML export to go into
  • Open The Journal (TJ)
  • File/Export/Export Entries to Document
  • Either:
    • Select the relevant category (eg Directory), and deselect the entries not wanted (eg templates), or
    • Select just the entries wanted from within the relevant category (eg Directory)
    • [Note that, if partially selected, to deselect the whole category you need to fully select it first]
  • Under Export Type
    • Select HTML
    • Make sure that "Export as a Web page with category & entry index" is not selected
    • Make sure that "Save CSS information in .html file" is not selected
    • [Note that these options, and those following, should carry over from the previous export]
  • Under Export Options
    • Select Create a File for each exported Entry
    • Make sure that "Include Category Name Header in export" is selected
    • Make sure that "Include Entry Date/Name Header in export" is selected
  • Under File Names
    • Enter the Category File Name as %c (eg “Directory”)
    • Enter the Entry File Name as %e (eg “Albany Road (R1)”)
    • Make sure that Include "Full Path" in Loose-Leaf Entry Names is selected (eg Albany Road (R1) - Owl House (21)
    • Enter the Export Path separator as  &#8209;  (ie blank, hyphen, blank)
  • Click on Export
  • When asked, browse to open the folder in which to put all the files (html and related images)
  • Click on Save
  • When it says Entries Exported, click on OK
  • You can now close The Journal (TJ)
[Note that at this point you can check individual exported HTML files by just opening them, but if their reference includes an # their associated image (jpeg) files will not appear. This is solved online by the processes below.]

Upload the HTML files to M4OPS
  • Use an FTP program (eg FileZilla)
  • On the server open the relevant OPS/HTML folder, and delete any files no longer needed
  • On your PC select all the files in the folder to which you exported from The Journal (TJ)
  • Upload all these (HTML and jpeg) files to the relevant OPS/HTML folder
  • [You can check individual uploaded HTML files within a browser, but again if their reference includes an # their associated image (jpeg) files will not appear.]

Create the list of features for M4OPS:
  • Open Karen’s Directory printer (can be downloaded free from here), and list files:
    • Select the Save to Disk tab
    • Select the folder specified above
    • Save Options: File info only
    • Ensure all other options (Search Sub-Folders etc) are not ticked
    • File info: ensure just File Name is ticked
    • File Filter: select Common HTML/Web files
    • Ensure the two Formatting options are ticked (Omit COMMENT lines, Omit FILE FOLDER and TOTAL Line ids)
    • Click on Save to Disk
    • When asked, browse to choose the folder in which to put the Directory Print (DirPrnInfo.txt)
    • You can now close Karen’s Directory printer
  • Open https://regexr.com/ - an online tool to learn, build, & test Regular Expressions
    • Copy the contents of DirPrnInfo.txt, and paste them into the Text area
    • Copy the following string and paste into the Expression area
      • (.+) - {0,}(.+)( [\(\#])(\w+)(\)*)(?:\.html)
      • [making sure the (default) /g flag is set]
      • [The groups are thus 1)Road 2)Dwelling 3)Prefix 4)Ref 5)Postfix]
    • In the Tools area, click on List
    • Copy the following string and paste into the List expression area
      • $4;$2, $1$3$4$5;;;;$&;$1 - $2;$2, $1;;;;\n
    • Copy the resulting list and paste it into a blank Features.csv text file
    • Insert at the top of this file:
      • featureid;shorttext;datestart;dateend;image;html;textforsort;fl_col1;Lon(X);Lat(Y);GeomType;GeomCoords (with a new line)
    • Open DirPrnInfo.txt in Notepad++ and replace the following:
      • (.+) - {0,}(.+)( [\(\#])(\w+)(\)*)(?:\.html)\r\n
      • by null
      • [making sure the Search Mode is set to Regular Expression]
      • [This removes all the lines we have just processed and leaves others]
    • The lines that remain are either Roads with valid references, or entries with invalid references
    • Copy any lines in DirPrnInfo.txt that are Roads with valid references into the RegExr Text area
    • Copy the following string and paste into the Expression area
      • (.+)( [\(\#])(\w+)(\)*)(?:\.html)
      • [again making sure the (default) /g flag is set]
      • [The groups are thus 1)Road 2)Prefix 3)Ref 4)Postfix]
    • In the Tools area, click on List
    • Copy the following string and paste into the List expression area
      • $3;$1$2$3$4;;;;$&;$1;$1;;;;\n
    • Copy the resulting list and paste append it to the Features.csv text file
    • Save Features.csv

See Compiling Features for the next stage.

13
Sources of Maps and Geographic Datasets / AWS public datasets
« on: 4 December 2017, 10:27:32 »
AWS (Amazon Web Services ) hosts a variety of public datasets that anyone can access for free, called AWS public datasets. Several of these datasets are Geospatial, including OSM for which details are given here.

14
The Genealogist announced in 2017 that they will be publishing the 1910 Valuation of England (or "Lloyd George Domesday Survey") which reveals who was living where and who the owner of the property.

In his introductory article, Nick Thorne explores the unique online collection of Land Tax records and maps revealing Edwardian occupiers and owners of property - as well as some long lost streets!


15
In the article We mapped it so you don’t have to the University of Georgia (UGA) Libraries’ Willson Center Digital Humanities Lab compare several mapping systems that students and faculty might consider using:
  • Google Fusion Tables
  • Carto
  • ArcGIS
  • Neatline (and Omeka)
None seem very relevant to One-Place Studies.

Pages: [1] 2 3 ... 30
mapping4ops.org is a Society for One-Place Studies project supported by Grassroots Giving from Skipton Building Society
Glossary | BBCodes | Feedback