The CSA Propylaea Project: Guide to FileMaker Database

The FileMaker (version 9) database that has been created to record the survey data is called NWwingSRVdta and carries the extension "fp7." There are five tables: FieldNotes, EwallREVcoords, SwallREVcoords, CADnotes, and KapTables. (Each table is available as a stand-alone, tab-delimited file for those wishing to import the table into another database management system: FieldNotes.tab, EwallREVcoords.tab, SwallREVcoords.tab, CADnotes.tab, and KapTables.tab. The individual tables have been combined into a single zip file called NWwingSRVdta.zip. The individual files were all generated with the UTF-8 character set.)

The material in the database includes the original survey data (coordinates) supplied by Mr. Kapokakis; the same survey data translated into the coordinate systems for the east and south walls, as appropriate; the final coordinates to be used, after adjustment for offsets; the notes made during the survey work; references to the notebook pages used during the survey process; and notes concerning the modeling of problematic blocks.

The database was organized and created by Mr. Eiteljorg. Ms. Jones assisted in the process of data entry, sometimes reading data or assisting in reading data and sometimes checking. No other persons were involved in creating the data set.

The intention from the outset was to create single data source for the work on the NW wing wall blocks. FileMaker 6.0 was the beginning program, and the data have been migrated through the succeeding versions; thus, the files were in fp5 format originally and were migrated to the current fp7 format. The database accomplished its aims well; indeed, it has proven to be more useful than originally envisioned, providing not only automated processes for CAD data entry via export procedures but also permitting a single source to be the definitive resource for the model.

The fields and relationships are as follows:

In table FieldNotes:
- SequenceNo -- Number -- note-taking sequence number, not survey-crew number
- TotalStationNo -- Number -- survey-crew number - used as a primary key but not defined as unique as it should have been
- BlockNo -- Number -- CSA-assigned number for each block (which may be seen in the model by turning on the correct layers; see the documentation of the CAD models for more information)
- BlockPart -- Text -- text description (block itself or, e.g., "peritenia bevel top")
- Code1 -- Text -- corner designation (e.g., UR for upper right)
- Code2 -- Text -- only for actual block corners: indicator of coordinate supplied, as hwd for height, width, depth (y,x,z); w for width only, d for depth only, etc.
- Code2Rev -- Text -- as code 1, but all places marked so that, e.g., width only would be indicated as XwX
- Code3 -- Text -- as Code1 but for points that were not block corners
- Obsrv dim in mm -- Number -- the offset measured at survey time
- NotesComments -- Text -- comments in notebook
- FromTStoPTinMMx -- Number -- from notebook, offset in x axis of wall-based coordinate system, plus or minus, in mm.
- FromTStoPTinMMy -- Number -- from notebook, offset in y axis of wall-based coordinate system, plus or minus, in mm. - though included as a possibility, there was no occasion when an offset in this axis was used
- FromTStoPTinMMz -- Number -- from notebook, offset in z axis of wall-based coordinate system, plus or minus, in mm.
- MyComments -- Text -- comments made during the creation of the CAD model
- ExtKey -- Calculation (stored, = Wall&BlockNo&Code1&BlockPart) - despite the name, this was not used as a key
- Wall -- Text -- almost exclusively E or S to indicate east wall or south wall but a few points on the west and north walls were surveyed for orientation
- Any of the coordinates for a given point might be adjusted according to a measured offset taken during the survey process, as described in the document about surveying (to be found at propylaea.org/Surveymethods.html). As a result, each coordinate, after being re-configured into a coordinate based upon the user coordinate system for the appropriate wall and stored in the appropriate table (below), could be adjusted by adding or subtracting, where required, the measured offset to yield the coordinate for final use in the CAD model, as follows.
  - XadjustedFORfinalCAD -- Calculation (unstored, = If (Wall="E";EwallREVcoords::E_UCS_X_value + (FromTStoPTinMMx)/1000;(If (Wall="S";SwallREVcoords::S_UCS_X_value + (FromTStoPTinMMx)/1000;""))))
  - YadjustedFORfinalCAD -- Calculation (unstored, = If (Wall="E";EwallREVcoords::E_UCS_Y_value + (FromTStoPTinMMy)/1000;(If (Wall="S";SwallREVcoords::S_UCS_Y_value + (FromTStoPTinMMy)/1000;""))))
  - ZadjustedFORfinalCAD -- Calculation (unstored, = If (Wall="E";EwallREVcoords::E_UCS_Z_value + (FromTStoPTinMMz)/1000;(If (Wall="S";SwallREVcoords::S_UCS_Z_value + (FromTStoPTinMMz)/1000;""))))
- WallBlock -- Calculation (=Wall & Right("000" & BlockNo;3) - used as a primary key but not required to be unique, as it should have been
- Block_Corner_Part -- Calculation (= WallBlock & Code1 & BlockPart & Code2)
- S_Wall_Surface -- Number - this number is the surface (not the block) surveyed on the south wall. The south wall blocks often have multiple surfaces that comprise the blocks because of protrusions and recesses, and the drawings of the wall (used to guide the survey work) made it far more reasonable to refer to surface numbers than block numbers. A single sequence of numbers was used for the surfaces, and the number applied to a block is the lowest number applied to the surfaces that comprise the block. [Note: On the CAD model, the layer named L____SW shows the numbers of both blocks and surfaces. The block numbers are larger (.3 m, drawing scale, for the blocks and .2 m. for the surfaces). There are never more than two surfaces per block, and, in each case, the lower number is the block number. Thus, for instance, block 60 includes surface 61. Note also that there are unused numbers arising from blocks not surveyed and/or errors in the numbering process.] This problem did not occur on the east wall; block and surface numbers are the same.

In table EwallREVcoords are the coordinates of east-wall survey points, in the user coordinate system designed for the east wall. These values were exported from the model file via an AutoCAD list command after they had been entered from the original survey data and then a new user coordinate system (EWALL) enabled; the data were not entered by hand.
- E_UCS_X_value -- Number -- East wall coordinate system value for x
- E_UCS_X_value -- Number -- East wall coordinate system value for y
- E_UCS_X_value -- Number -- East wall coordinate system value for z
- TotStaNO -- Number - a foreign key here

In table SwallREVcoords are the coordinates of south-wall survey points, in the user coordinate system designed for the south wall. These values were exported from the model file via an AutoCAD list command after they had been entered from the original survey data and then a new user coordinate system (SWALL) enabled; the data were not entered by hand.
- S_UCS_X_value -- Number -- South wall coordinate system value for x
- S_UCS_X_value -- Number -- South wall coordinate system value for y
- S_UCS_X_value -- Number -- South wall coordinate system value for z
- TotStaNO -- Number - a foreign key here

In table CADnotes are notes made in the process of creating the CAD model. This table should be consulted to check for any blocks that have been problematic in any way. There are many such blocks, and this is the table where the problems - and chosen solutions - are recorded. Note that there are not such descriptions/explanations for blocks not modeled. That is, if no attempt was made to model a block, there is no information in this table to explain why. The rather slow evolution of layer names means that the layer and WallBlock fields changed as work on the model progressed.
- layer -- Text -- CAD layer name in model
- note -- Text -- comment by model-maker
- date -- Date -- date of comment or last alteration
- person -- Text - model-maker
- WallBlock -- Calculation from layer name to indicate block number and thereby supply a link to the main table ( = Middle (layer;3;1) & Right (layer;3) - a foreign key here)

In table KapTables are the original survey coordinates. These values were imported into the table from Mr. Kapokakis's supplied data file; the data were not entered by hand.
- TotalStationNumber -- Number -- survey-crew number - a foreign key here
- X -- Number -- surveyed X value
- Y -- Number -- surveyed Y value
- Z -- Number-- surveyed Z value

Table-to-table relationships:
Total station number, the number recorded by the survey crew for each set of coordinates, is the key column/field used to relate tables to one another with a single exception. The Wallblock column/field relates FieldNotes to CADnotes.

The relationships are all one-to-one relationships with this exception: More than one point on a wall might be located by the same survey point. When two blocks meet tightly, for instance, the UR corner of one may match the UL of its neighbor. Therefore, the FieldNotes table is related to all the survey-data tables in many-to-one relationships.

Please note that information in these tables is necessarily positivist. That is, there is an implicit assumption that the information is somehow demonstrably correct. The truth, alas, is usually gray, however; so users may wish to consult the notebook, photographs, or other sources to satisfy themselves that the information is correct -- or at least not clearly incorrect. (The notebook -- a PDF file of scanned pages -- will be available here soon.)

Downloading the Files

Please note that the FileMaker file has not been zipped (compressed). Some browsers are confused when they encounter uncompressed binary files like this and may simply open a file in your browser window as if it were a text file instead of downloading it. This is a known problem with Safari. If you encounter such a problem, please right-click on the file and choose the download option. If that does not solve the problem, please notify CSA.

The tab-delimited ASCII files, in a single zipped file, should present no download problems. You will, of course, need to import the files, when uncompressed into a database management system and establish the correct relationships.




	The Project: •Home Page Αρχική Σελίδα •Background & Rationale Φόντο •Project Introduction Εισαγωγή •History •Publications & Lectures •Grant Application The Building: •General Information •Photographs Φωτογραφίες Photo Database Managing photos CAD Issues & Data: •CAD discussion •Coordinates & Grids •Mechanical Drawings •CAD Models Survey Issues & data: •Survey Discussion •Survey Notebooks •Survey Database On-going investigation of Architectural planning in antiquity •Web pages: Introduction General planning Propylaea matters Discussion •Equivalent Blog Copyright Statement Older Propylon Archives About this document. Search this site.		The CSA Propylaea Project: Guide to FileMaker Database The FileMaker (version 9) database that has been created to record the survey data is called NWwingSRVdta and carries the extension "fp7." There are five tables: FieldNotes, EwallREVcoords, SwallREVcoords, CADnotes, and KapTables. (Each table is available as a stand-alone, tab-delimited file for those wishing to import the table into another database management system: FieldNotes.tab, EwallREVcoords.tab, SwallREVcoords.tab, CADnotes.tab, and KapTables.tab. The individual tables have been combined into a single zip file called NWwingSRVdta.zip. The individual files were all generated with the UTF-8 character set.) The material in the database includes the original survey data (coordinates) supplied by Mr. Kapokakis; the same survey data translated into the coordinate systems for the east and south walls, as appropriate; the final coordinates to be used, after adjustment for offsets; the notes made during the survey work; references to the notebook pages used during the survey process; and notes concerning the modeling of problematic blocks. The database was organized and created by Mr. Eiteljorg. Ms. Jones assisted in the process of data entry, sometimes reading data or assisting in reading data and sometimes checking. No other persons were involved in creating the data set. The intention from the outset was to create single data source for the work on the NW wing wall blocks. FileMaker 6.0 was the beginning program, and the data have been migrated through the succeeding versions; thus, the files were in fp5 format originally and were migrated to the current fp7 format. The database accomplished its aims well; indeed, it has proven to be more useful than originally envisioned, providing not only automated processes for CAD data entry via export procedures but also permitting a single source to be the definitive resource for the model. The fields and relationships are as follows: In table FieldNotes: SequenceNo -- Number -- note-taking sequence number, not survey-crew number TotalStationNo -- Number -- survey-crew number - used as a primary key but not defined as unique as it should have been BlockNo -- Number -- CSA-assigned number for each block (which may be seen in the model by turning on the correct layers; see the documentation of the CAD models for more information) BlockPart -- Text -- text description (block itself or, e.g., "peritenia bevel top") Code1 -- Text -- corner designation (e.g., UR for upper right) Code2 -- Text -- only for actual block corners: indicator of coordinate supplied, as hwd for height, width, depth (y,x,z); w for width only, d for depth only, etc. Code2Rev -- Text -- as code 1, but all places marked so that, e.g., width only would be indicated as XwX Code3 -- Text -- as Code1 but for points that were not block corners Obsrv dim in mm -- Number -- the offset measured at survey time NotesComments -- Text -- comments in notebook FromTStoPTinMMx -- Number -- from notebook, offset in x axis of wall-based coordinate system, plus or minus, in mm. FromTStoPTinMMy -- Number -- from notebook, offset in y axis of wall-based coordinate system, plus or minus, in mm. - though included as a possibility, there was no occasion when an offset in this axis was used FromTStoPTinMMz -- Number -- from notebook, offset in z axis of wall-based coordinate system, plus or minus, in mm. MyComments -- Text -- comments made during the creation of the CAD model ExtKey -- Calculation (stored, = Wall&BlockNo&Code1&BlockPart) - despite the name, this was not used as a key Wall -- Text -- almost exclusively E or S to indicate east wall or south wall but a few points on the west and north walls were surveyed for orientation Any of the coordinates for a given point might be adjusted according to a measured offset taken during the survey process, as described in the document about surveying (to be found at propylaea.org/Surveymethods.html). As a result, each coordinate, after being re-configured into a coordinate based upon the user coordinate system for the appropriate wall and stored in the appropriate table (below), could be adjusted by adding or subtracting, where required, the measured offset to yield the coordinate for final use in the CAD model, as follows. XadjustedFORfinalCAD -- Calculation (unstored, = If (Wall="E";EwallREVcoords::E_UCS_X_value + (FromTStoPTinMMx)/1000;(If (Wall="S";SwallREVcoords::S_UCS_X_value + (FromTStoPTinMMx)/1000;"")))) YadjustedFORfinalCAD -- Calculation (unstored, = If (Wall="E";EwallREVcoords::E_UCS_Y_value + (FromTStoPTinMMy)/1000;(If (Wall="S";SwallREVcoords::S_UCS_Y_value + (FromTStoPTinMMy)/1000;"")))) ZadjustedFORfinalCAD -- Calculation (unstored, = If (Wall="E";EwallREVcoords::E_UCS_Z_value + (FromTStoPTinMMz)/1000;(If (Wall="S";SwallREVcoords::S_UCS_Z_value + (FromTStoPTinMMz)/1000;"")))) WallBlock -- Calculation (=Wall & Right("000" & BlockNo;3) - used as a primary key but not required to be unique, as it should have been Block_Corner_Part -- Calculation (= WallBlock & Code1 & BlockPart & Code2) S_Wall_Surface -- Number - this number is the surface (not the block) surveyed on the south wall. The south wall blocks often have multiple surfaces that comprise the blocks because of protrusions and recesses, and the drawings of the wall (used to guide the survey work) made it far more reasonable to refer to surface numbers than block numbers. A single sequence of numbers was used for the surfaces, and the number applied to a block is the lowest number applied to the surfaces that comprise the block. [Note: On the CAD model, the layer named L____SW shows the numbers of both blocks and surfaces. The block numbers are larger (.3 m, drawing scale, for the blocks and .2 m. for the surfaces). There are never more than two surfaces per block, and, in each case, the lower number is the block number. Thus, for instance, block 60 includes surface 61. Note also that there are unused numbers arising from blocks not surveyed and/or errors in the numbering process.] This problem did not occur on the east wall; block and surface numbers are the same. In table EwallREVcoords are the coordinates of east-wall survey points, in the user coordinate system designed for the east wall. These values were exported from the model file via an AutoCAD list command after they had been entered from the original survey data and then a new user coordinate system (EWALL) enabled; the data were not entered by hand. E_UCS_X_value -- Number -- East wall coordinate system value for x E_UCS_X_value -- Number -- East wall coordinate system value for y E_UCS_X_value -- Number -- East wall coordinate system value for z TotStaNO -- Number - a foreign key here In table SwallREVcoords are the coordinates of south-wall survey points, in the user coordinate system designed for the south wall. These values were exported from the model file via an AutoCAD list command after they had been entered from the original survey data and then a new user coordinate system (SWALL) enabled; the data were not entered by hand. S_UCS_X_value -- Number -- South wall coordinate system value for x S_UCS_X_value -- Number -- South wall coordinate system value for y S_UCS_X_value -- Number -- South wall coordinate system value for z TotStaNO -- Number - a foreign key here In table CADnotes are notes made in the process of creating the CAD model. This table should be consulted to check for any blocks that have been problematic in any way. There are many such blocks, and this is the table where the problems - and chosen solutions - are recorded. Note that there are not such descriptions/explanations for blocks not modeled. That is, if no attempt was made to model a block, there is no information in this table to explain why. The rather slow evolution of layer names means that the layer and WallBlock fields changed as work on the model progressed. layer -- Text -- CAD layer name in model note -- Text -- comment by model-maker date -- Date -- date of comment or last alteration person -- Text - model-maker WallBlock -- Calculation from layer name to indicate block number and thereby supply a link to the main table ( = Middle (layer;3;1) & Right (layer;3) - a foreign key here) In table KapTables are the original survey coordinates. These values were imported into the table from Mr. Kapokakis's supplied data file; the data were not entered by hand. TotalStationNumber -- Number -- survey-crew number - a foreign key here X -- Number -- surveyed X value Y -- Number -- surveyed Y value Z -- Number-- surveyed Z value Table-to-table relationships: Total station number, the number recorded by the survey crew for each set of coordinates, is the key column/field used to relate tables to one another with a single exception. The Wallblock column/field relates FieldNotes to CADnotes. The relationships are all one-to-one relationships with this exception: More than one point on a wall might be located by the same survey point. When two blocks meet tightly, for instance, the UR corner of one may match the UL of its neighbor. Therefore, the FieldNotes table is related to all the survey-data tables in many-to-one relationships. Please note that information in these tables is necessarily positivist. That is, there is an implicit assumption that the information is somehow demonstrably correct. The truth, alas, is usually gray, however; so users may wish to consult the notebook, photographs, or other sources to satisfy themselves that the information is correct -- or at least not clearly incorrect. (The notebook -- a PDF file of scanned pages -- will be available here soon.) Downloading the Files Please note that the FileMaker file has not been zipped (compressed). Some browsers are confused when they encounter uncompressed binary files like this and may simply open a file in your browser window as if it were a text file instead of downloading it. This is a known problem with Safari. If you encounter such a problem, please right-click on the file and choose the download option. If that does not solve the problem, please notify CSA. The tab-delimited ASCII files, in a single zipped file, should present no download problems. You will, of course, need to import the files, when uncompressed into a database management system and establish the correct relationships. Download the FileMaker file (NWwingSRVdta.fp7) Download the tab-delimited tables (NWwingSRVdta.zip)

	Note the color differences between the top photo and the lower one. This reflects the color of the sunlight at the west end of the Acropolis, with the morning light being cool and the afternoon light warm, growing steadily warmer toward sunset.		About this document: Title: The CSA Propylaea Project: Guide to FileMaker Database Author: Harrison Eiteljorg, II and the staff of CSA, Box 60, Bryn Mawr, PA 19010, (e-mail: user nicke at (@) the domain csanet.org; tel.: 484-612-5862) File name: databasedoc.html Revision history: This document has not been changed (except for coding changes not affecting the contained text), but changes may occur. There will be no archiving of past versions, but changes of consequence will be clearly indicated in any updated version. Posted: 3 August 2000. Last updated (menu items only): December 2010. Internet access: This document is maintained at propylaea.csanet.org by the Center for the Study of Architecture and Harrison Eiteljorg, II. Note that there may be changes in computer addresses that are beyond the control of CSA. Long-term availability: This document or its successors will be maintained for electronic access indefinitely. Prior versions will not be archived. Citation permissions and copyright information: This document is copyrighted by CSA. Citations should include the date of the document cited.