Description: UPDATES4/29/2015: There are 21 Administrative Districts to which HFD Stations report. This data is stored in the “ Admin” field, most recently updated from the most current DISTRICT/STATIONS provided by Alicia Whitehead-Breaux HFD. The information was from the HFD Operations Command in February 2014. Station 84 has since been added and is in administrative district 64.There are some discrepancies between the different District fields. Accordingto Chief Casey, Assistant Chief of Emergency Operations. There are some Stations that reside in one HFD District but report to another District Chief. This has to do with Span of Control for that District and the way the Districts are divided city wide.The “Admin” field has been updated and the values for the following stations have changed:STATION 022 From 20 To HAZ (Hazmat)STATION 025 From 46 To 8STATION 054 From NULL To ARF (ARFF –Bush)STATION 073 From 83 To 68STATION 0 81 From 70 To ARF (ARFF –Hobby)STATION 082 From 83 To 68STATION 092 From NULL To ARF (ARFF –Bush)STATION 093 From 71 to 70STATION 096 From 64 To 4STATION 099 From NULL To ARF (ARFF –Bush)STATION 105 From 102 To 64STATION 301 From 5 To NULL
Description: 09/17/2013 This version of the fire atom feature class is a work in progress that has been loaded into Test CAD. It contains new fire atoms, new running schedules, and new XY coordinates that have not been moved to CAD LIVE nor have they been placed on the call floor.This Fire Atom shapefile is composed of more than 4000 fire atom polygons. Each fire atom polygon is the grouping of nodes with the same running schedule from Due01 to Due06.The running schedule of each node was calculated by a routing program from ESRI Network Analyst Closest Facility. This program calls the Network Analyst module to calculate the nearest HFD fire stations to each node, as well as the running distances from each station.FIELD DESSCRIPTIONS:ATOM= Parent Fire Atom. This was the source of a new atom.Text= Fire Atoms or Response Group. Use this field to display fire atoms in a map, use Text to label the atoms. A fire atom prefaced with a B indicates a Boundary atom. The purpose of Boundary atoms is to assist call takers in identifying who will service the roads and addresses when a street is on the COH boundary. Boundary atoms cover the roads at the COH boundary.ATOM= Parent Fire Atom. This was the source of a new atom, it is not the name of an atom and should not be used to label fire atoms.NewText= Clone Fire Atoms. Clone atoms identify the municipality that will share in the servicing of an identified portion of the Boundary Atom.CLONE2= A second Clone Fire Atom. When a boundary atom is serviced by the COH and 2 other municipalities, this field identifies the second municipality.DISPGRP & FIRST_MATC= Dispatch Group. The values are identical. Use either field to create a map identifying the dispatch groups for the COH HFD. The Dispatch Group identifies the first District Chief in the atom’s Running Schedule. As of April 2011, the District Chiefs are at stations 4, 5, 6, 8 ,19, 20, 21, 26, 28, 31, 45, 46, 59, 64, 68, 70, 71, 78, 83, and 102. DUE01_1 ,D1, & D1_12= First fire station in the atom’s running schedule. Use any of these fields to create a map identifying the Still Alarms, First In, or Response Area.LINK = Hyperlink to a file on the K drive that explains the types of edits performed on the atom, the reason for the edit, documentation, pertinent e-mails requesting the edit, image of the edit, etc.NODES& VERTICES= Represents the count of vertices in a single polygon. The limit of vertices allowed for a polygon is 2048.NOTES= Description of the last edit made to the atom.
Description: The HFD FireAtom feature class is composed of more than 4600 fire atom polygons which are defined by a running schedule. Each atom consists of all the intersections, within the City of Houston, with identical running schedules for the first six response stations. This information was obtained by using the ARC GIS extension “Network Analyst, Closest Facility”.FIELD DESSCRIPTIONS:ATOM= Parent Fire Atom. This was the source of a new atom.TEXT= Names the Fire Atoms:Use the TEXT field to display or label fire atoms in a map. A fire atom prefaced with a B indicates a Boundary atom. The purpose of Boundary atoms is to assist call takers in identifying who will service the roads and addresses when a street is on the COH boundary. Boundary atoms cover the roads at the COH boundary.HFD has requested using the following naming convention when new atoms are created, and eventually as atoms are renamed: NORMAL ATOMS: For 1 or 2 digitstation names, the first digit of the atom will always be a place holder ,2, followed by the “first-in” station number (80) or (a 0 preceding a one digit number). The final three numbers of the atom name will be a three digit atom identifier (123). For example a normal atom with station 80 as “first-in” could be 280123; a normal atom with station 9 as “first-in” could be 209123.For 3 digitstation names, no place holder is necessary. For example an atom for which station 102 is “first-in” could be 102123.SPECIAL RESPONSE ATOMS (SRP): First Digit number is 3All special Response Atoms will use the number 3 as the first character.For 1 or 2 digitstation names, 3 would be the initial place holder, followed by a two digit station number (or a 1 digit station name preceded by a 0), then the three digit atom identifier. For example SRP Station 9, atom identifier 154 would be 309154.; SRP Station 24, atom identifier 456 would be 324456. For SRP stations with 3 digits, replace the first character of the station name and use a letter for the first character of the atom identifier. For example station 103, the 3 will replace the first character (one) and the three character atom identifier would be something like A12 to yield the atom name 303A12.FREEWAY ATOMS: First Digit number is 4 or 5Freeway atoms will use the number 4 or 5 as the first character. The number 4will be used for all freeway atoms associated with fire stations with a one or two digit name, followed by a three digit number identifier. Example: 480164The number 5will be used for all atoms associated with fire stations with a three digit name. Replace the first of the three digits with a 5 and add the three digit character identifier. Example: station 101 = 501286.Exception: Station 301- The number 5will be used for all atoms associated with fire stations with a three digit name. Forthe stationname, replace the first of the three digits with a 5 and begin the atom identifier with a letter of the alphabet followed by a two digit number.. Example: station 101 = 501A86.NewTEXT= Names the Clone Fire Atoms. Clone atoms identify the municipality (City code) that will share in the servicing of an identified portion of the Boundary Atom. All Boundary Atoms must have a clone. All Clones begin with the city code id and end with the same numerical value as the Boundary Atom.CLONE2= Names a second Clone Fire Atom. When a boundary atom is serviced by the COH and 2 other municipalities, this field identifies the second municipality. Al Clones begin with the city code id and end with the same numerical value as the Boundary Atom.CC_HO and CC_HCPARENT= Parent Fire Atom- Parent names the fire atom from which another atom was created.DISPGRP & FIRST_MATC= Names the Dispatch Group. Use either field to create a map identifying the HFD dispatch groups for the City of Houston . The Dispatch Group identifies the first District Chief in the atom’s Running Schedule. As of April 2011, the District Chiefs are at stations 4, 5, 6, 8 ,19, 20, 21, 26, 28, 31, 45, 46, 59, 64, 68, 70, 71, 78, 83, and 102. DUE01_1 ,D1, & D1_12= Field names for the first fire station in the atom’s running schedule. All three fields contain the same data. Use any of these fields to create a map identifying the Still Alarms, First In, or Response Area. The duplicate fields have not bee removed, as they may be used in various scripts.LINK = Hyperlink to a file on the K drive that explains the types of edits performed on the atom, the reason for the edit, documentation, pertinent e-mails requesting the edit, image of the edit, etc.NODES& VERTICES= Represents the count of vertices in a single polygon. The limit of vertices allowed for a polygon is 2048.NOTES= Description of the last edit made to the atom.MESSAGE = This field contains the message that will be added to the CAD spreadsheet. It point to the fire atom that will be used for a Boundary Atoms.CC_HO = This field references the Boundary Atom and identifies which side of the street is serviced by the City of Houston.CC_HC = This field references the Boundary Atom and identifies which side of the street is serviced by Harris County or other municipality. It may use a city code other than HC.The following fields are no longer used and should be removed: NEW_ATOM, NEW_FA, NEW_CLONE1, HO_CLONE
Description: 09/17/2013 This version of the fire atom feature class is a work in progress that has been loaded into Test CAD. It contains new fire atoms, new running schedules, and new XY coordinates that have not been moved to CAD LIVE nor have they been placed on the call floor.This Fire Atom shapefile is composed of more than 4000 fire atom polygons. Each fire atom polygon is the grouping of nodes with the same running schedule from Due01 to Due06.The running schedule of each node was calculated by a routing program from ESRI Network Analyst Closest Facility. This program calls the Network Analyst module to calculate the nearest HFD fire stations to each node, as well as the running distances from each station.FIELD DESSCRIPTIONS:ATOM= Parent Fire Atom. This was the source of a new atom.Text= Fire Atoms or Response Group. Use this field to display fire atoms in a map, use Text to label the atoms. A fire atom prefaced with a B indicates a Boundary atom. The purpose of Boundary atoms is to assist call takers in identifying who will service the roads and addresses when a street is on the COH boundary. Boundary atoms cover the roads at the COH boundary.ATOM= Parent Fire Atom. This was the source of a new atom, it is not the name of an atom and should not be used to label fire atoms.NewText= Clone Fire Atoms. Clone atoms identify the municipality that will share in the servicing of an identified portion of the Boundary Atom.CLONE2= A second Clone Fire Atom. When a boundary atom is serviced by the COH and 2 other municipalities, this field identifies the second municipality.DISPGRP & FIRST_MATC= Dispatch Group. The values are identical. Use either field to create a map identifying the dispatch groups for the COH HFD. The Dispatch Group identifies the first District Chief in the atom’s Running Schedule. As of April 2011, the District Chiefs are at stations 4, 5, 6, 8 ,19, 20, 21, 26, 28, 31, 45, 46, 59, 64, 68, 70, 71, 78, 83, and 102. DUE01_1 ,D1, & D1_12= First fire station in the atom’s running schedule. Use any of these fields to create a map identifying the Still Alarms, First In, or Response Area.LINK = Hyperlink to a file on the K drive that explains the types of edits performed on the atom, the reason for the edit, documentation, pertinent e-mails requesting the edit, image of the edit, etc.NODES& VERTICES= Represents the count of vertices in a single polygon. The limit of vertices allowed for a polygon is 2048.NOTES= Description of the last edit made to the atom.
Description: 09/17/2013 This version of the fire atom feature class is a work in progress that has been loaded into Test CAD. It contains new fire atoms, new running schedules, and new XY coordinates that have not been moved to CAD LIVE nor have they been placed on the call floor.This Fire Atom shapefile is composed of more than 4000 fire atom polygons. Each fire atom polygon is the grouping of nodes with the same running schedule from Due01 to Due06.The running schedule of each node was calculated by a routing program from ESRI Network Analyst Closest Facility. This program calls the Network Analyst module to calculate the nearest HFD fire stations to each node, as well as the running distances from each station.FIELD DESSCRIPTIONS:ATOM= Parent Fire Atom. This was the source of a new atom.Text= Fire Atoms or Response Group. Use this field to display fire atoms in a map, use Text to label the atoms. A fire atom prefaced with a B indicates a Boundary atom. The purpose of Boundary atoms is to assist call takers in identifying who will service the roads and addresses when a street is on the COH boundary. Boundary atoms cover the roads at the COH boundary.ATOM= Parent Fire Atom. This was the source of a new atom, it is not the name of an atom and should not be used to label fire atoms.NewText= Clone Fire Atoms. Clone atoms identify the municipality that will share in the servicing of an identified portion of the Boundary Atom.CLONE2= A second Clone Fire Atom. When a boundary atom is serviced by the COH and 2 other municipalities, this field identifies the second municipality.DISPGRP & FIRST_MATC= Dispatch Group. The values are identical. Use either field to create a map identifying the dispatch groups for the COH HFD. The Dispatch Group identifies the first District Chief in the atom’s Running Schedule. As of April 2011, the District Chiefs are at stations 4, 5, 6, 8 ,19, 20, 21, 26, 28, 31, 45, 46, 59, 64, 68, 70, 71, 78, 83, and 102. DUE01_1 ,D1, & D1_12= First fire station in the atom’s running schedule. Use any of these fields to create a map identifying the Still Alarms, First In, or Response Area.LINK = Hyperlink to a file on the K drive that explains the types of edits performed on the atom, the reason for the edit, documentation, pertinent e-mails requesting the edit, image of the edit, etc.NODES& VERTICES= Represents the count of vertices in a single polygon. The limit of vertices allowed for a polygon is 2048.NOTES= Description of the last edit made to the atom.
Description: The HFD FireAtom feature class is composed of more than 4600 fire atom polygons which are defined by a running schedule. Each atom consists of all the intersections, within the City of Houston, with identical running schedules for the first six response stations. This information was obtained by using the ARC GIS extension “Network Analyst, Closest Facility”.FIELD DESSCRIPTIONS:ATOM= Parent Fire Atom. This was the source of a new atom.TEXT= Names the Fire Atoms:Use the TEXT field to display or label fire atoms in a map. A fire atom prefaced with a B indicates a Boundary atom. The purpose of Boundary atoms is to assist call takers in identifying who will service the roads and addresses when a street is on the COH boundary. Boundary atoms cover the roads at the COH boundary.HFD has requested using the following naming convention when new atoms are created, and eventually as atoms are renamed: NORMAL ATOMS: For 1 or 2 digitstation names, the first digit of the atom will always be a place holder ,2, followed by the “first-in” station number (80) or (a 0 preceding a one digit number). The final three numbers of the atom name will be a three digit atom identifier (123). For example a normal atom with station 80 as “first-in” could be 280123; a normal atom with station 9 as “first-in” could be 209123.For 3 digitstation names, no place holder is necessary. For example an atom for which station 102 is “first-in” could be 102123.SPECIAL RESPONSE ATOMS (SRP): First Digit number is 3All special Response Atoms will use the number 3 as the first character.For 1 or 2 digitstation names, 3 would be the initial place holder, followed by a two digit station number (or a 1 digit station name preceded by a 0), then the three digit atom identifier. For example SRP Station 9, atom identifier 154 would be 309154.; SRP Station 24, atom identifier 456 would be 324456. For SRP stations with 3 digits, replace the first character of the station name and use a letter for the first character of the atom identifier. For example station 103, the 3 will replace the first character (one) and the three character atom identifier would be something like A12 to yield the atom name 303A12.FREEWAY ATOMS: First Digit number is 4 or 5Freeway atoms will use the number 4 or 5 as the first character. The number 4will be used for all freeway atoms associated with fire stations with a one or two digit name, followed by a three digit number identifier. Example: 480164The number 5will be used for all atoms associated with fire stations with a three digit name. Replace the first of the three digits with a 5 and add the three digit character identifier. Example: station 101 = 501286.Exception: Station 301- The number 5will be used for all atoms associated with fire stations with a three digit name. Forthe stationname, replace the first of the three digits with a 5 and begin the atom identifier with a letter of the alphabet followed by a two digit number.. Example: station 101 = 501A86.NewTEXT= Names the Clone Fire Atoms. Clone atoms identify the municipality (City code) that will share in the servicing of an identified portion of the Boundary Atom. All Boundary Atoms must have a clone. All Clones begin with the city code id and end with the same numerical value as the Boundary Atom.CLONE2= Names a second Clone Fire Atom. When a boundary atom is serviced by the COH and 2 other municipalities, this field identifies the second municipality. Al Clones begin with the city code id and end with the same numerical value as the Boundary Atom.CC_HO and CC_HCPARENT= Parent Fire Atom- Parent names the fire atom from which another atom was created.DISPGRP & FIRST_MATC= Names the Dispatch Group. Use either field to create a map identifying the HFD dispatch groups for the City of Houston . The Dispatch Group identifies the first District Chief in the atom’s Running Schedule. As of April 2011, the District Chiefs are at stations 4, 5, 6, 8 ,19, 20, 21, 26, 28, 31, 45, 46, 59, 64, 68, 70, 71, 78, 83, and 102. DUE01_1 ,D1, & D1_12= Field names for the first fire station in the atom’s running schedule. All three fields contain the same data. Use any of these fields to create a map identifying the Still Alarms, First In, or Response Area. The duplicate fields have not bee removed, as they may be used in various scripts.LINK = Hyperlink to a file on the K drive that explains the types of edits performed on the atom, the reason for the edit, documentation, pertinent e-mails requesting the edit, image of the edit, etc.NODES& VERTICES= Represents the count of vertices in a single polygon. The limit of vertices allowed for a polygon is 2048.NOTES= Description of the last edit made to the atom.MESSAGE = This field contains the message that will be added to the CAD spreadsheet. It point to the fire atom that will be used for a Boundary Atoms.CC_HO = This field references the Boundary Atom and identifies which side of the street is serviced by the City of Houston.CC_HC = This field references the Boundary Atom and identifies which side of the street is serviced by Harris County or other municipality. It may use a city code other than HC.The following fields are no longer used and should be removed: NEW_ATOM, NEW_FA, NEW_CLONE1, HO_CLONE
Description: The HFD FireAtom feature class is composed of more than 4600 fire atom polygons which are defined by a running schedule. Each atom consists of all the intersections, within the City of Houston, with identical running schedules for the first six response stations. This information was obtained by using the ARC GIS extension “Network Analyst, Closest Facility”.FIELD DESSCRIPTIONS:ATOM= Parent Fire Atom. This was the source of a new atom.TEXT= Names the Fire Atoms:Use the TEXT field to display or label fire atoms in a map. A fire atom prefaced with a B indicates a Boundary atom. The purpose of Boundary atoms is to assist call takers in identifying who will service the roads and addresses when a street is on the COH boundary. Boundary atoms cover the roads at the COH boundary.HFD has requested using the following naming convention when new atoms are created, and eventually as atoms are renamed: NORMAL ATOMS: For 1 or 2 digitstation names, the first digit of the atom will always be a place holder ,2, followed by the “first-in” station number (80) or (a 0 preceding a one digit number). The final three numbers of the atom name will be a three digit atom identifier (123). For example a normal atom with station 80 as “first-in” could be 280123; a normal atom with station 9 as “first-in” could be 209123.For 3 digitstation names, no place holder is necessary. For example an atom for which station 102 is “first-in” could be 102123.SPECIAL RESPONSE ATOMS (SRP): First Digit number is 3All special Response Atoms will use the number 3 as the first character.For 1 or 2 digitstation names, 3 would be the initial place holder, followed by a two digit station number (or a 1 digit station name preceded by a 0), then the three digit atom identifier. For example SRP Station 9, atom identifier 154 would be 309154.; SRP Station 24, atom identifier 456 would be 324456. For SRP stations with 3 digits, replace the first character of the station name and use a letter for the first character of the atom identifier. For example station 103, the 3 will replace the first character (one) and the three character atom identifier would be something like A12 to yield the atom name 303A12.FREEWAY ATOMS: First Digit number is 4 or 5Freeway atoms will use the number 4 or 5 as the first character. The number 4will be used for all freeway atoms associated with fire stations with a one or two digit name, followed by a three digit number identifier. Example: 480164The number 5will be used for all atoms associated with fire stations with a three digit name. Replace the first of the three digits with a 5 and add the three digit character identifier. Example: station 101 = 501286.Exception: Station 301- The number 5will be used for all atoms associated with fire stations with a three digit name. Forthe stationname, replace the first of the three digits with a 5 and begin the atom identifier with a letter of the alphabet followed by a two digit number.. Example: station 101 = 501A86.NewTEXT= Names the Clone Fire Atoms. Clone atoms identify the municipality (City code) that will share in the servicing of an identified portion of the Boundary Atom. All Boundary Atoms must have a clone. All Clones begin with the city code id and end with the same numerical value as the Boundary Atom.CLONE2= Names a second Clone Fire Atom. When a boundary atom is serviced by the COH and 2 other municipalities, this field identifies the second municipality. Al Clones begin with the city code id and end with the same numerical value as the Boundary Atom.CC_HO and CC_HCPARENT= Parent Fire Atom- Parent names the fire atom from which another atom was created.DISPGRP & FIRST_MATC= Names the Dispatch Group. Use either field to create a map identifying the HFD dispatch groups for the City of Houston . The Dispatch Group identifies the first District Chief in the atom’s Running Schedule. As of April 2011, the District Chiefs are at stations 4, 5, 6, 8 ,19, 20, 21, 26, 28, 31, 45, 46, 59, 64, 68, 70, 71, 78, 83, and 102. DUE01_1 ,D1, & D1_12= Field names for the first fire station in the atom’s running schedule. All three fields contain the same data. Use any of these fields to create a map identifying the Still Alarms, First In, or Response Area. The duplicate fields have not bee removed, as they may be used in various scripts.LINK = Hyperlink to a file on the K drive that explains the types of edits performed on the atom, the reason for the edit, documentation, pertinent e-mails requesting the edit, image of the edit, etc.NODES& VERTICES= Represents the count of vertices in a single polygon. The limit of vertices allowed for a polygon is 2048.NOTES= Description of the last edit made to the atom.MESSAGE = This field contains the message that will be added to the CAD spreadsheet. It point to the fire atom that will be used for a Boundary Atoms.CC_HO = This field references the Boundary Atom and identifies which side of the street is serviced by the City of Houston.CC_HC = This field references the Boundary Atom and identifies which side of the street is serviced by Harris County or other municipality. It may use a city code other than HC.The following fields are no longer used and should be removed: NEW_ATOM, NEW_FA, NEW_CLONE1, HO_CLONE