21
M4OPS - for those responsible for an OPS / Compiling Features
« Last Post by PeterC 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:
See Georeferencing Features for the next stage.
- Ensure the Features.csv file is in UTF8 format with no BOM
- for Notepad++ use the menu Encoding - click on Convert to UTF-8 (without BOM), save and reload to check it is still encoded as UTF-8
- Add the All Features layer
- Upload and compile
- Georeference the Features
- 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.
- 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.