The Geofile is a reference database that describes world locations. There are about 56700 locations in the file. Locations include cities, airports (various types), bodies of water, etc. (see table below). Each location record is identified by a unique 4 character code that is used by other data records to reference the location. I've used these codes for the URI. Each record contains the location name, code, type, coordinates (lat/long), and location (country, state, or water area) information. In the geofile the location information is duplicated in multiple records. For the DAML representation I made locations separate objects each with their own 2 character code, long and short name.
The following table lists the Classes defined in the Geofile Ontology.
Class | SubclassOf |
Location | |
GeographicLocation | Location |
GeographicArea | |
State | GeographicArea |
Country | GeographicArea |
WaterArea | GeographicArea |
Another option would be to create a class hierarchy of installation types under the GeographicLocation class.
This table lists all the fields in the Geofile with descriptions. It also lists the corresponding properties defined in the Geofile Ontology. Many of the fields are not in the ontology because there was no values in the geofile for those fields (indicated by N/A).
Geofile Field | DAML Property | Description | Domain | Range |
geoloc | geolocationCode | Geolocation Code | GeographicLocation | geofile-dt:geocode [String (length=4)] |
key-filler | n/a | Special Key Filler | ||
name | name | Geolocation Name | GeographicLocation | xsd:String |
inst-type | installationTypeCode | Installation Type Code | GeographicLocation | geofile-dt:installationTypeCode [String (length=3)] |
cc | countryStateCode | Country/State Code | GeographicArea | geofile-dt:cc [String (length=2)] |
short-name | shortName | Country/State Short Name | GeographicArea | String |
province | n/a | Province Code | ||
province-name | n/a | Province Name | ||
tactical-zone | n/a | Tactical Zone | ||
coordinates | longitude latitude |
Geographic Coordinates | Location | xsd:longitude xsd:latitude |
plan-code | planCode | Logistic Planning and Reporting Code | GeographicLocation | xsd:planCode [String (length=2)] |
prime-geoloc | primeGeoloc | Prime Geolocation Code | GeographicLocation | GeographicLocation |
record-owner | recordOwner | Record Owner | GeographicLocation | Literal |
not-used | n/a | Not Used | ||
icao | icao | International Civil Aviation Organization Code | GeographicLocation | geofile-dt:icaoCode [String (length=4)] |
gsa-state | n/a | GSA State Code | ||
gsa-city | n/a | GSA City Code | ||
gsa-county | n/a | GSA County Code | ||
last-changed | lastChangedDate | Date this record was last changed | GeographicLocation | xsd:date |
created | createdDate | Date this record was created | GeographicLocation | xsd:date |
cancelled | cancelledDate | Date this GEOLOC was cancelled | GeographicLocation | xsd:date |
long-name | longName | Name of the country, state, or water area | GeographicArea | String |
status | status | Record Status Code | GeographicLocation | Status |
classification | classification | Security Classification Code | GeographicLocation | Classification |
army-loc | n/a | Army Location Code | ||
ocean-area | n/a | Navy Ocean Area Code | ||
not-used2 | n/a | Not Used |
Because I separated out the state/country information from the geolocations, I created the locatedIn property to reassociate the data.
Property | Domain | Range |
locatedIn | Location | GeographicArea |
containsLocation | GeographicArea | Location |
The ontology was generated by hand in a text editor. I modified Lisp code from another project to parse the geofile and generate the DAML data files. I used RDF-API to check the syntax of the files.
Three files were generated:
Installation Type Code Definitions | |
AFD | AIRFIELD |
AFS | AIR-FORCE-STATION |
APT | AIRPORT |
ASN | AIR-STATION |
IAP | INTERNATIONAL-AIRPORT |
JAP | JOINT-USE-AIRPORT |
MAP | MILITARY-AIRPORT |
BAY | BAY |
CHL | CHANNEL |
CNL | CANAL |
CPE | CAPE |
DOC | DOCK |
GLF | GULF |
LKE | LAKE |
OCN | OCEAN |
PRT | PORT |
PSG | PASSAGE |
SEA | SEA |
STR | STRAIT |
ADM | ADMINSTRATION |
ANX | ANNEX |
ATM | AIR-TERMINAL |
COM | COMMUNICATION |
RRC | RADAR-RECEIVER |
RRJ | RAILROAD-JUNCTION |
RRL | RADIO-RELAY |
RTC | RESERVE-TRAINING-CENTER |
RTR | RADAR-INSTALLATION |
MFC | MAINTENANCE |
SVC | SERVICE |
TNG | TRAINING |
WAE | WEATHER-STATION |
CAP | CIVIL-AIR-PATROL |
CGI | COAST-GUARD-INSTALLATION |
COC | COMMAND-OPERATIONS |
AGS | AIR-NAT-GUARD-STATION |
AIN | ARMY-INSTALLATION |
MBK | MARINE-BARRACKS |
MCC | MARINE-CORPS-CAMP |
MGI | MARINE-GROUND-INSTALLATION |
NBA | NAVAL-BASE |
NYI | NAVY-INSTALLATION |
AMO | AMMUNITION-STORAGE |
DFP | DEFENSE-FUEL-SUPPORT-POINT |
POL | POL-RETAIL-DISTRIBUTION-STATION |
STG | STORAGE |
DEP | DEPOT |
FHG | FAMILY-HOUSING |
REC | RECREATION |
SCH | SCHOOL |
HSP | HOSPITAL |
DIS | DISPENSARY |
CLN | CLINIC |
CTY | CITY |
ISL | ISLAND |
OPA | OPERATING AREA |
RPA | RURAL POPULATED AREA |
MSL | MISSILE |
NAC | NAVAL ACTIVITY |
NAV | NAVAID |
$Id: index.html,v 1.3 2001/09/13 22:21:11 drager Exp $