User Data

  User supplied data

(update: download sample user supplied data set with fictitious case-control data FGBASE)

The software FGBASE will look for the user supplied data in the directory
~/Library/Application Support/FGBASE/
( ~ denotes the user’s home directory i.e. /Users/user_name/ )
The structure of the directory FGBASE is the following:

FGBASE/
    cases_long_lat_cells.grid
    controls_long_lat_cells.grid
    population.grid
    entities.grid
    cities_long_lat_cells.grid
    log
    classes_of_entities/
        classes.csv
        entities.csv
        membership.csv

———————————
file : cases_long_lat_cells.grid
———————————

This file contains the geographical coordinates of the disease cases.
There is no header line, and each line consists of two integers separated by a semi-colon.
Each line corresponds to a particular case.
The first integer is the longitude (x-coordinate) of the case in grid cell coordinates.
The second integer is the latitude (y-coordinate) of the case in grid cell coordinates.

example: the first 3 lines of the file could look like this:
3907;2321
4025;2508
3203;2397

———————————–
file : controls_long_lat_cells.grid
———————————–

This file contains the geographical coordinates of the controls.
There is no header line, and each line consists of two integers separated by a semi-colon.
Each line corresponds to a particular control.
The first integer is the longitude (x-coordinate) of the control in grid cell coordinates.
The second integer is the latitude (y-coordinate) of the control in grid cell coordinates.

example: the first 3 lines of the file could look like this:
3802;3071
3630;2362
3752;2888

———————————–
file : population.grid
———————————–

This file contains the population density.
There is no header line, and each line consists of 3 integers separated by a semi-colon.
Each line corresponds to a particular grid cell.
The first integer is the longitude (x-coordinate) of the cell in grid coordinates.
The second integer is the latitude (y-coordinate) of the cell in grid coordinates.
The third integer is the population count for that particular grid cell.

example: the first 3 lines of the file could look like this:
2862;5142;2
2862;5141;13
2864;5141;211

———————————–
file : entities.grid
———————————–

This file contains the classless entities, which are a collection of spatial entities which are not grouped into classes.
There is no header line, and each line consists of two integers separated by a semi-colon.
Each line corresponds to a particular spatial entity.
The first integer is the longitude (x-coordinate) of the spatial entity in grid coordinates.
The second integer is the latitude (y-coordinate) of the spatial entity in grid coordinates.

example: the first 3 lines of the file could look like this:
3827;2934
3878;2975
3857;2935

———————————–
file : cities_long_lat_cells.grid
———————————–

This optional file contains a list of cities for easy access on the map.
There is no header line, and each line consists of 3 fields separated by a semi-colon.
Each line corresponds to a particular city.
The first field (an integer) is the longitude (x-coordinate) of the city in grid coordinates.
The second field (an integer) is the latitude (y-coordinate) of the city in grid coordinates.
The third field is the name of the city.

example: the first 3 lines of the file could look like this:
3952;2280;Aix-en-Provence
3807;3045;Arrras
3486;2473;Bordeaux

————————————-
file : log
————————————-

This file is created by the application when it runs. The user does not need to create this file.
This log file will contain description of data loading errors as well as results from statistical analysis.

***********************************************************
Files for classes of spatial entities
***********************************************************

The files for classes of spatial entities are contained in the folder classes_of_entities.

classes_of_entities/
                classes.csv
                entities.csv
        membership.csv

————————————–
file : classes_of_entities/classes.csv
————————————–

This file contains the a list of classes, which enable the grouping of similar spatial entities.
The first line is a header line:
class_name;class_id
 
Each line consists of two fields separated by a semi-colon.
Each line below the header line corresponds to a particular class.
The first field is the name of the class.
The second field is a class id.

example: the first 3 lines of the file could look like this:
wheat;6
corn;56
potatoes;9

—————————————–
file : classes_of_entities/membership.csv
—————————————–

This file links spatial entities to classes. An entity may belong to several classes.
The first line is a header line:
class_id;entity_id

Each line consists of two fields separated by a semi-colon.
Each line below the header line corresponds to a particular membership relationship.
The first field is the class id
The second field is the entity id

example: the first 3 lines of the file could look like this:
9;7
56;2
56;11

—————————————-
file : classes_of_entities/entities.csv
—————————————-

This file contains the spatial entities which are to be grouped into classes for analysis.
The first line is a header line:

name;id;long_LAEA(x);lat_LAEA(y)

Each line consist of 4 fields separated by semi-colons
Each line below the header line corresponds to a particular spatial entity.

– The first field is the name of the spatial entity.
– The second field is the id of the spatial entity ( the entity id is used when assigning spatial entities to classes
though membership relationships defined in the membership.csv file)
– the third field is the longitude (x-coordinate) of the spatial entity in LAEA (Lambert Azimuthal Equal Area) coordinates.
– the fourth field is the latitude (y-coordinate) of the spatial entity in LAEA     (Lambert Azimuthal Equal Area) coordinates.

example: the first 3 lines of the file could look like this:
crop_field_name;7;3713506.4;2168702.5
another_crop_field_name;2;3718128.8;2178013.2
a_third_crop_field_name;11;3671102.4;2184058.2