Tags
structure, Synagogues Organization and administration, Jewish community centers, Synagogues, Synagogues as community centers
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 struck, or is predicted for, a locality. Synagogues and other Jewish religious institutions that may be affected must be identified. 2. An assessment of the evacuation requirements and issues for a given area needs to be made as part of a disaster mitigation plan. Synagogues and other Jewish religious institutions that may need to be evacuated must be identified. 3. Facilities that can serve as shelters must be identified. 4. There has been a threat against Synagogues and other Jewish religious institutions. These locations need to be identified, their leadership contacted, and their buildings protected.
Jewish Synagogues in Arkansas The Jewish Synagogues dataset is composed of Jewish places of worship and other Jewish religious institutions such as Jewish Community Centers. Some Jewish Synagogues were processed using information found through internet research and locations were determined based upon available sources of ortho imagery (USGS DOQQ's, NAIP, and state and local imagery). These records are indicated by a [CONTHOW] of "ALT REF". All data is non license restricted data. The text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g. the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] attribute. Based upon this attribute, the oldest record dates from 2007/07/20 and the newest record dates from 2007/07/31
There are no credits for this item.
There are no access and use limitations for this item.
Extent
| West | -94.396617 | East | -90.691160 |
| North | 36.376519 | South | 33.618709 |
See access and use constraints information.
The Jewish Synagogues dataset is composed of Jewish places of worship and other Jewish religious institutions. This layer also includes Jewish Community Centers.
TGS
Geometry type of feature.
TGS
Sequential unique whole numbers that are automatically generated.
Feature geometry.
ESRI
Coordinates defining the features.
Unique identifier for feature.
TGS
Text
Date entity was contacted by TGS.
TGS
Date
Telephone extension for emergency point of contact.
TGS
Text
Title of person or name of office for emergency point of contact.
TGS
Text
Feature geometry.
ESRI
Coordinates defining the features.
Link to Metadata.
TGS
Text
Geocoding precision.
TGS
Indicates the type of facility the synagogue is located in or the type of facility the congregation holds their meetings at. The values for this attribute have not been verified by TGS.
TGS
Text
County name where entity is located.
TGS
Link ID for the street segment to which the entity was geocoded. Refer to the [ST_VENDOR] and [ST_VERSION] attributes for the street vendor and version that was used to geocode the entity.
TGS
Text
Longitude in WGS 84 Decimal Degrees.
TGS
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.
TGS
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 attribute 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.
TGS
Method by which entity was contacted.
TGS
Sequential unique whole numbers that are automatically generated.
Internal feature number.
ESRI
Sequential unique whole numbers that are automatically generated.
Organization that performed Quality Control/Quality Assurance on the record.
TGS
Five (5) digit USPS zip code for entity's physical location.
TGS
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 attribute. Also, the state in which an entity appears to be located may change depending on the scale of the state boundary theme being used.
TGS
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 attribute. 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 they are located on is listed in this attribute. Some rural areas may not have named roads. In these rare cases, this attribute will be blank.
TGS
Text
Location within physical address, e.g., floor, suite, building.
TGS
Text
Indicates the year and quarter of streets used for geocoding.
TGS
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.
TGS
Phone numbers, including area code, formatted as nnn-nnn-nnnn. A list of valid area code and exchange combinations can be found at http://www.nanpa.com
Directions to entity location, or description of the entity's location.
TGS
Text
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] attribute 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 attribute 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.
TGS
Text
Name of entity.
TGS
Text
Security classification of feature.
TGS
Indicates whether the phone number in the phone field rings to the actual location of the entity.
TGS
Sequential unique whole numbers that are automatically generated.
Latitude in WGS 84 Decimal Degrees.
TGS
Indicates name of vendor providing original street data used for geocoding.
TGS
Four (4) digit USPS zip code extension. This attribute was automatically assigned using the entity's physical address and USPS address information system (AIS) data.
TGS
Seven (7) digit telephone number for entity formatted as nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit.
TGS
Phone numbers formatted as nnn-nnnn. Only numeric digits are used. The first three (3) digits (the exchange) must form a valid combination with the area code. A list of valid area code and exchange combinations can be obtained from http://www.nanpa.com
Method by which entity was geocoded.
TGS
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.
TGS
Date entity was geocoded by TGS.
TGS
Date