FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION

TITLE: FLORIDA PLACES OF WORSHIP 2008 Q3

Geodataset Name:       FDEM_RELIGION_JUL08
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Point
Feature Count:         1556
GENERAL DESCRIPTION:
This dataset contains Places of Worship in Florida. The Places of Worship dataset is composed of any type of building or portion of a building that is used, constructed, designed, or adapted to be used as a church, chapel, synagogue, or mosque. If a building's primary purpose is something other than worship (e.g., a community center, a public school), but a religious group uses the building for worship on a regular basis, it was included in this dataset if it otherwise met the criteria for inclusion. In cases where membership or attendance figures were available, places of worship were selected for inclusion that had 750 or more members or attendees. This dataset was created by TechniGraphics, Inc. for the Florida Division of Emergency Management.
DATA SOURCE(S):                    Florida Division of Emergency Management
SCALE OF ORIGINAL SOURCE MAPS:     VARIOUS
GEODATASET EXTENT:                 State of Florida
PUBLICATION DATE: 20080721 TIME PERIOD OF CONTENT: Begin Date: 20070716 End Date: 20080721 DOWNLOAD LINK: http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: FDEM_RELIGION_JUL08.DBF
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
ID
50 String
SECCLASS
30 String
NAME
100 String
TELEPHONE
12 String
ADDRESS
80 String
ADDRESS2
80 String
CITY
20 String
STATE
2 String
ZIP
5 String
ZIPP4
4 String
COUNTY
50 String
FIPS
5 String
DIRECTIONS
160 String
EMERGTITLE
50 String
EMERGTEL
15 String
EMERGEXT
10 String
CONTDATE
36 Date
CONTHOW
10 String
GEODATE
36 Date
GEOHOW
10 String
NAICSCODE
6 String
NAICSDESCR
120 String
GEOLINKID
10 String
X
8 Double
Y
8 Double
ST_VENDOR
10 String
ST_VERSION
10 String
GEOPREC
32 String
PHONELOC
3 String
QC_QA
3 String
STATE_ID
90 String
SUBTYPE
50 String
DENOM
50 String
MEMBERS
20 String
ATTENDANCE
8 Double
LOC_TYPE
80 String
USNG_FL_1K
10 String
DESCRIPT
100 String
FGDLAQDATE
36 Date
SHAPE
4 Geometry
AUTOID
4 Integer

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

ID Unique identifier for feature.

SECCLASS Security classification of feature
UNCLASSIFIED = Entity is unclassified.


NAME Name of entity.

TELEPHONE Ten (10) digit telephone number for entity formatted as nnn-nnn-nnnn.

ADDRESS Physical street address for entity. "PO Box", "General Delivery", "Rural Route", and "Highway Contract" addresses are not considered physical addresses and should not appear in this field. Some areas do not have regular city style addressing, so entities in those areas may not have a street number. In such cases, the name of the road on which they are located is listed in this field. Some rural areas may not have named roads. In these rare cases, this field will be blank.

ADDRESS2 Location within physical address, e.g., floor, suite, building.

CITY The name of the city associated with the entity's physical address. For physical addresses that the U.S. Postal Service (USPS) delivers to, this should be a "city" acceptable to the USPS as defined in their Address Information System (AIS). Sometimes the USPS does not deliver mail to a physical address but recognizes the location (i.e., they list the location as "undeliverable"). The cities associated with these locations are acceptable. In some cases, the USPS does not recognize individual physical addresses in a city, rather, they list the city as having "General Delivery". In these cases, the city and associated zip code are acceptable (the entity's [ADDRESS] field will contain a street address, not "general delivery"). The entity may not actually be located within the city limits of the "city" specified in its [CITY] field. Instead, it may actually be located within the city limits of another city. In some cases, the "city" that appears in this field may not even be a city in an administrative sense, but it is still an acceptable "city" to the USPS. An example of this is "Notre Dame, IN". There is no city in Indiana called "Notre Dame", but this is considered an acceptable city by the USPS for any delivery going to the University of Notre Dame which is actually located in the city of South Bend. "Notre Dame", like most USPS cities, is an easily recognized place, and it gives the user of the data a good general idea of where the entity is located (if the entity is located in a small municipality, the USPS "city" may be more recognizable than the name of the municipality), and it would be part of the address one would use to send a shipment to the entity's location. Using the USPS acceptable "city" also allows someone to do a logical consistency check between the zip code and the city by using the USPS AIS. Sometimes an entity may report a city that is not accepted by the USPS, and although TGS has tried to replace those cities with an acceptable alternative, some of them may remain in this dataset.

STATE Two (2) character abbreviation for state associated with the entity's physical address. In almost all cases this is the same as the state where the entity has been depicted geospatially. However, there are cases, particularly where an entity is part of a larger facility that cuts across state lines, where the entity's location may be depicted in a state other than the one indicated in this field. Also, the state in which an entity appears to be located may change depending on the scale of the state boundary theme being used.

ZIP Five (5) digit USPS zip code for entity's physical location.

ZIPP4 Four (4) digit USPS zip code extension. These values are automatically assigned using the entity's physical address and USPS address information system (AIS) data.

COUNTY County name where entity is located.

FIPS Five (5) digit FIPS (Federal Information Processing Standards) Code for the County where entity is located. The first two (2) digits represent the state and the last three (3) digits identify the county within the state.

DIRECTIONS Directions to entity location, or description of the entity's location.

EMERGTITLE Title of person or name of office for emergency point of contact.

EMERGTEL Ten (10) digit telephone number of emergency point of contact formatted as nnn-nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit.

EMERGEXT Telephone extension for emergency point of contact.

CONTDATE Date entity was contacted by TGS.

CONTHOW Method by which entity was contacted.
PHONE = Entity was contacted by phone.

FAX = Entity was contacted by fax.

MAIL = Entity was contacted by mail.

EMAIL = Entity was contacted by email.

WEB = Entity information was gathered and/or verified by official entity website as a last resort.

ALT REF = Geospatial reference information obtained from local authorities, e.g., downloadable parcel maps, 911 streets, and shape files.

<BLANK> = Entity has not been contacted by TGS.


GEODATE Date entity was geocoded by TGS.

GEOHOW Method by which entity was geocoded.
AUTO = Entity was automatically geocoded.

MANUAL = Entity was manually geocoded.

ADJUSTED = Entity was shifted by TGS to an updated set of NAVTEQ streets. This only applies if the entity was manually geocoded by TGS to a previous version of NAVTEQ streets.

PROVIDED = Entity was geocoded using coordinates provided by the original source.


NAICSCODE NAICS (North American Industry Classification System) Code for entity. NAICS Codes (and NAICS Descriptions) have been assigned based upon the entity's primary function, regardless of if that is the function that qualified it to be included in this dataset.

NAICSDESCR NAICS (North American Industry Classification System) Description for entity. The "Index Entries" that appear on the NAICS webpage (http://www.census.gov/epcd/www/naics.html) are being used to populate this field as opposed to the "NAICS Title". While there is a one to one correspondence between NAICS Codes and "NAICS Titles", there is a one to many relationship between NAICS Codes and the "Index Entries". By using the "Index Entries", we have placed the entities that make up this layer into more specific categories; however, the user of this data should be aware that this was not the intended purpose of these "Index Entries". The "Index Entries" were intended as a way to search the NAICS database and as a way of enumerating ways in which establishments falling under the given NAICS Code may be named. Thus, there are often two or more "Index Entries" that are synonyms, for example: "Prisons" and "Penitentiaries". In cases like this, we have standardized on one "Index Entry". NAICS Descriptions (and NAICS Codes) have been assigned based upon the entity's primary function, regardless of the function that qualified it to be included in this dataset.
CHURCHES = CHURCHES - [NAICS Code 813110]: Establishments primarily engaged in administering an organized religion or promoting religious activities of the Christian religion.

MOSQUES, RELIGIOUS = MOSQUES, RELIGIOUS - [NAICS Code 813110]: Establishments primarily engaged in administering an organized religion or promoting religious activities of the Muslim religion.

SYNAGOGUES = SYNAGOGUES - [NAICS Code 813110]: Establishments primarily engaged in administering an organized religion or promoting religious activities of the Judaic religion.


GEOLINKID Link ID for the street segment to which the entity was geocoded. Refer to the [ST_VENDOR] and [ST_VERSION] fields for the street vendor and version that was used to geocode the entity.

X Longitude in WGS 84 Decimal Degrees.

Y Latitude in WGS 84 Decimal Degrees.

ST_VENDOR Indicates name of vendor providing original street data used for geocoding.
NAVTEQ = NAVTEQ streets were used for geocoding.

TGS = TGS drew in a new street segment that does not exist in the file supplied by NAVTEQ.

<BLANK> = Entity was geocoded using coordinates provided by the original source; therefore, the street vendor is unknown.


ST_VERSION Indicates the year and quarter of streets used for geocoding.
2006Q4 = 4th Quarter 2006 NAVTEQ Street Data used for geocoding.

<BLANK> = Entity was geocoded using coordinates provided by the original source; therefore, the street version is unknown.


GEOPREC Geocoding precision.
BLOCKFACE = Entity is geocoded to correct block and correct side of street per street data indicated by [ST_VENDOR] and [ST_VERSION].

ONENTITY = Entity is geocoded on entity rooftop per aerial imagery (in most cases USGS DOQQs).

GPS = Entity is geocoded using supplied GPS coordinates.


PHONELOC Indicates whether the phone number in the [TELEPHONE] field rings to the actual location of the entity.
YES = Phone number rings to the actual entity location.

NO = Phone number does not ring to the actual entity location. It might ring to an administrative office or central location.

<BLANK> = Unknown - It is not known if the entity's phone number rings to the entity's location.


QC_QA Organization that performed Quality Control/Quality Assurance on the record.
TGS = TGS has performed Quality Control/Quality Assurance on the entity record.

<BLANK> = The record is not TGS added or has not had Quality Control/Quality Assurance performed by TGS.


STATE_ID State Places of Worship Data ID. For states that contributed data, this field is populated with the unique ID used by the state to track Places of Worship. For data obtained through TGS original research, this is sometimes used for TGS internal purposes.

SUBTYPE The primary religion practiced at the place of worship. The values for this field were provided by individual sources and TGS did not verify these values.
CHRISTIAN = The primary religion is Christianity.

JUDAIC = The primary religion is Judaism.

MUSLIM = The primary religion is Islam.


DENOM Indicates the denomination associated with the primary religion practiced at the place of worship. The values for this field were provided by individual sources and TGS did not verify these values.

MEMBERS The number of members, listed either as individuals or as families. The values for this field were provided by individual sources and TGS did not verify these values.

ATTENDANCE The average number of service attendees. The values for this field were provided by individual sources and TGS did not verify these values.

LOC_TYPE Indicates the type of building used for the place of worship. The values for this field were provided by individual sources and TGS did not verify these values.

USNG_FL_1K Facility's 1-kilometer United States National Grid (USNG) address. The USNG is an alpha-numeric reference system based on the UTM coordinate system and is similar to the Military Grid Reference System. Use of the USNG ensures a uniform grid mapping and positional reporting system for search and rescue, emergency planning, response, and recovery. How to Read a United States National Grid (USNG) Spatial Address Website - http://www.fgdc.gov/usng/how-to-read-usng/index_html

DESCRIPT Based on NAME.

FGDLAQDATE The date FGDL acquired the data from the Source.

SHAPE Feature geometry.

AUTOID Unique ID added by GeoPlan


USER NOTES:
See "Attribute_Accuracy_Report". Many of the checks described in that section 
check for both attribute accuracy and logical consistency.
Some churches with fewer than 750 members or attendees and some churches 
outside of cities with populations of 100,000 have been excluded.  This was done
as a means of prioritizing the work on this dataset.

Some smaller denominations are not currently represented in this dataset.

The Places of Worship dataset is not intended to include homes of religious 
leaders (unless they also serve as a place of organized worship), religious schools
(unless they also serve as a place of organized worship for people other than 
those enrolled in the school), mikvahs, hillels, and buildings that serve a purely 
administrative purpose.

This dataset only includes Christian, Judaic, and Islamic places of worship.  In 
future updates, TGS will add places of worship for other religions.
GeoPlan Center Accuracy Report:
GeoPlan relied on the integrity of the attribute information within
the original data.

TechniGraphics, Inc. Attribute Accuracy Report:
The name, address, city, state, and five (5) digit zip codes were verified to be 
correct through alternate resources as of the date indicated by the [CONTDATE] 
field. The existence of the entity was also verified, as well as whether or not it met 
the criteria for inclusion in this dataset. Four (4) digit zip code extensions were 
derived from USPS (United States Postal Service) data and were not verified.

ID Check: The [ID] field is not blank and all IDs are unique.

Coordinate Check: Coordinates are not null or zero and the x and y fields match 
the shape.

Basic Address Check: Physical addresses were verified to be non blank and to 
not be a "PO Box", "General Delivery", "Highway Contract", or "Rural Route" 
address. 

Highway Address without Type Check: Physical addresses containing the word 
"Highway" or "Route" were verified to also contain a type designator such as 
"State", "US", or "County", if one actually exists for the highway or route. These 
type designators are often missing from addresses, leading to confusion if more 
than one "Highway" of the given number exists in an area. 

Basic Name Check: Entity name is not blank, is not the same as entity city, and 
has a minimum of 2 characters. Name does not contain punctuation characters 
that can interfere with database operations, such as " (quote) and * (asterisk). 

Basic Phone Check: All phone numbers (including the area code) are ten (10) 
numeric digits. Alphabetic characters have been converted to the corresponding 
numeric digit. 

County FIPS to State Compare Check: The county represented by the tabular 
FIPS Code is actually in the state specified in the [STATE] field. 

County Name to State Compare Check: The county represented by the tabular 
county name is actually in the state specified in the [STATE] field. 

Phone Number Format Check: Phone numbers (including area code) were verified
to be formatted as nnn-nnn-nnnn. 

Zip Code Check: The zip code is five (5) or nine (9) numeric digits, is listed in the 
postal database, is in the same state as indicated by the entity's [STATE] value, 
and is not a PO Box only zip code. 

Zip City Check: The entity's zip code and its city were verified to match according 
to the USPS Address Information System (AIS). 

Collocation Check: Entities with different addresses must not share the exact 
same geospatial location.

Geographic Spell Check: Words that appear in the entity name were checked 
against a standard English word list (and Spanish word list for entities in Puerto 
Rico). Words not appearing in these standard word lists were then checked 
against names appearing in the Geographic Names Information System (GNIS) of 
geographic features that are located within 25 miles of the entity. Proper names 
were manually reviewed for correct spelling.

City Check: Entity city is not blank and is found in the NAVTEQ Named Places file
within 25 miles.

NPA_NXX Check: The NPA (area code) and NXX (exchange) of the phone 
number form a valid combination according to data from the North American 
Number Planning Administration (NANPA).

Area Code Distance Check: The entity's area code is valid and the entity is not 
more than 25 miles from its area code boundary (unless TGS has previously 
verified that the phone number rings to a HQ location or otherwise does not ring to 
the entity).
The license free Large Protestant Churches, Mosques, Jewish Synagogues, and 
Roman Catholic Churches in Large Cities datasets were merged together to create 
the initial data for the Places of Worship Q108 dataset. Additional entities were 
added from State Partners and TGS research to create the final Places of 
Worship Q108 dataset.

The Places of Worship dataset is not intended to include homes of religious 
leaders (unless they also serve as a place of organized worship), religious schools
(unless they also serve as a place of organized worship for people other than 
those enrolled in the school), mikvahs, hillels, and buildings that serve a purely 
administrative purpose.

This dataset only includes Christian, Judaic, and Islamic places of worship. In 
future updates, TGS will add places of worship for other religions.

This dataset is comprised entirely of non licensed restricted data that was 
obtained through State Partners and TGS research.

On 08/07/2007, TGS ceased making phone calls to verify information about 
religious locations. Therefore, most entities in this dataset were verified using 
alternative reference sources such as topographic maps, parcel maps, various 
sources of imagery, and internet research. The [CONTHOW] (contact how) value 
for these entities has been set to "ALT REF". 

Records with "-DOD" appended to the end of the [NAME] value are located on a
military base, as defined by the Defense Installation Spatial Data Infrastructure 
(DISDI) military installations and military range boundaries.

Text fields in this dataset have been set to all upper case and trimmed to facilitate 
consistent database engine search results. 

Non printable and control characters were removed from all text fields. All diacritics
(e.g., the German umlaut or the Spanish tilde) have been replaced with their 
closest equivalent English character. This was done to facilitate using this dataset 
with database systems that may not support such characters. 

The currentness of this dataset is indicated by the [CONTDATE] field. Based 
upon the values in this field, the oldest record dates from 07/16/2007 and the 
newest record dates from 03/27/2008.

Homeland Security                  

Use Cases: Use cases describe how the data may be used and help to define 
and clarify requirements. 

1. A disaster or health emergency has occurred, or is predicted for a locality. 
Places of Worship or congregations that may be affected must be identified. 

2. An assessment as to the evacuation needs and issues for a given area needs 
to be made as part of a disaster mitigation plan. Places of Worship that may need 
to be evacuated must be identified. 

3. Facilities that can serve as shelters must be identified. 

4. A threat has been made toward Places of Worship and other religious 
institutions. These locations need to be identified, their leadership contacted, and 
their buildings protected.

TechniGraphics, Inc. Accuracy Report:
The geographic location of entities was verified to be correct relative to the street 
data and version indicated by the [ST_VENDOR] and [ST_VERSION] fields. The 
horizontal accuracy is indicated by the [GEOPREC] field.  A value of 
"BLOCKFACE" indicates the entity was geocoded on the correct street segment 
(block) and correct side of the street.  A value of "ONENTITY" indicates that the 
location is on the entity's facility, as determined by USGS DOQQ imagery, and that 
it is on the correct street segment (block) and correct side of the street.

Records with "-DOD" appended to the end of the [NAME] value are located on a
military base, as defined by the Defense Installation Spatial Data Infrastructure 
(DISDI) military installations and military range boundaries.

GeoPlan Center Accuracy Report:
This data is provided 'as is' and its horizontal positional accuracy
has not been verified by GeoPlan

This data is provided 'as is' and its vertical positional accuracy
has not been verified by GeoPlan

NONE

The Florida Geographic Data Library is a collection of Geospatial Data
compiled by the University of Florida GeoPlan Center with support from
the Florida Department of Transportation. GIS data available in FGDL is
collected from various state, federal, and other agencies (data sources)
who are data stewards, producers, or publishers. The data available in
FGDL may not be the most current version of the data offered by the
data source. University of Florida GeoPlan Center makes no guarantees
about the currentness of the data and suggests that data users check
with the data source to see if more recent versions of the data exist.

Furthermore, the GIS data available in the FGDL are provided 'as is'.
The University of Florida GeoPlan Center makes no warranties, guaranties
or representations as to the truth, accuracy or completeness of the data
provided by the data sources. The University of Florida GeoPlan Center
makes no representations or warranties about the quality or suitability
of the materials, either expressly or implied, including but not limited
to any implied warranties of merchantability, fitness for a particular
purpose, or non-infringement. The University of Florida GeoPlan Center
shall not be liable for any damages suffered as a result of using,
modifying, contributing or distributing the materials.

A note about data scale: 

Scale is an important factor in data usage.  Certain scale datasets
are not suitable for some project, analysis, or modeling purposes.
Please be sure you are using the best available data. 

1:24000 scale datasets are recommended for projects that are at the
county level.
1:24000 data should NOT be used for high accuracy base mapping such
as property parcel boundaries.
1:100000 scale datasets are recommended for projects that are at the
multi-county or regional level.
1:125000 scale datasets are recommended for projects that are at the
regional or state level or larger.

Vector datasets with no defined scale or accuracy should be
considered suspect. Make sure you are familiar with your data
before using it for projects or analysis. Every effort has been
made to supply the user with data documentation. For additional
information, see the References section and the Data Source Contact
section of this documentation. For more information regarding
scale and accuracy, see our webpage at:
http://geoplan.ufl.edu/education.html

REFERENCES:
Mike Thompson
TechniGraphics, Inc. - Director of Geospatial Datasets
mthompson@tgstech.com

TechniGraphics, Inc.
3351 Eastbrook Drive
Fort Collins, CO
80525
970-224-4996
8am - 5pm, Monday - Friday, Mountain Time
http://www.tgstech.com/gis.asp


Florida Division of Emergency Management
http://www.floridadisaster.org/index.asp
http://www.floridadisaster.org/gis

DATA LINEAGE SUMMARY:
1) On 08/07/2007, TGS ceased making phone calls to verify information about 
religious locations. Therefore, most entities in this dataset were verified using 
alternative reference sources such as topographic maps, parcel maps, various 
sources of imagery, and internet research. The [CONTHOW] (contact how) value 
for these entities has been set to "ALT REF".

2) NAICS Codes and NAICS Descriptions were assigned based on the entity 
name, web research, and the type of data sources that were used to create the 
database.

3) Four (4) digit United States Postal Service (USPS) zip code extensions were 
assigned based on the USPS Address Information System (AIS).

4) County names and FIPS Codes were assigned through a spatial join.

5) All text fields were set to upper case.

6) Leading and trailing spaces were trimmed from all text fields. These spaces can
interfere with some database queries.

7) Non printable and diacritic characters were removed from all text fields. These 
values have been found to prevent data from being loaded into some spatial 
database engines.
Process Date: 20080721

GeoPlan Center received the data via FTP from the Florida Division of Emergency Management (FDEM) on August 19, 2008. The original dataset was named: 2008_07_21_FL_PlacesOfWorship.zip 2008_07_21_FL_PlacesOfWorship.shp The original dataset projection was: Spatial_Reference_Information: Horizontal_Coordinate_System_Definition: Geographic: Latitude_Resolution: 0.000000 Longitude_Resolution: 0.000000 Geographic_Coordinate_Units: Decimal degrees Geodetic_Model: Horizontal_Datum_Name: D_WGS_1984 Ellipsoid_Name: WGS_1984 Semi-major_Axis: 6378137.000000 Denominator_of_Flattening_Ratio: 298.257224 The dataset was renamed to: fdem_religion_jul08.shp The dataset was reprojected to the FGDL Albers NAD83 HARN projection. The dataset features were matched to their 1-kilometer United States National Grid (USNG) address via a spatial join, the USNG address can be found in the USNG_FL_1K field. The USNG is an alpha-numeric reference system based on the UTM coordinate system and is similar to the Military Grid Reference System. Use of the USNG ensures a uniform grid mapping and positional reporting system for search and rescue, emergency planning, response, and recovery. How to Read a United States National Grid (USNG) Spatial Address http://www.fgdc.gov/usng/how-to-read-usng/index_html Three additional fields were added. DESCRIPT field based on NAME FGDLAQDATE field based on the date the data was acquired by FGDL from the source. AUTOID field based on FID + 1, GeoPlan Center feature identification number. Finally the attribute table was upper-cased and the metadata was updated. Process Date: 20080915
Data imported to ArcSDE and exported as a shapefile. Process Date: 20081021
MAP PROJECTION PARAMETERS:

Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000

DATA SOURCE CONTACT (S):

Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:
Florida Division of Emergency Management
FDEM
2555 Shumard Oak Boulevard
Tallahassee, FL
32399-2100
850-413-9907

www.floridadisaster.org/gis gis@em.myflorida.com Richard Butgereit

FGDL CONTACT:
Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        PO Box 115706
                        Gainesville, FL  32611-5706
Web site:               http://www.fgdl.org

Contact FGDL: 

      Technical Support:	        http://www.fgdl.org/fgdlfeed.html
      FGDL Frequently Asked Questions:  http://www.fgdl.org/fgdlfaq.html
      FGDL Mailing Lists:		http://www.fgdl.org/fgdl-l.html
      For FGDL Software:                http://www.fgdl.org/software.html