The population density of Hillsboro, IL was 1,044 in 2018. The population density of Murphysboro, IL was 1,543 in 2018.

Population Density

Population Density is computed by dividing the total population by Land Area Per Square Mile.

Above charts are based on data from the U.S. Census American Community Survey | ODN Dataset | API - Notes:

1. ODN datasets and APIs are subject to change and may differ in format from the original source data in order to provide a user-friendly experience on this site.

2. To build your own apps using this data, see the ODN Dataset and API links.

3. If you use this derived data in an app, we ask that you provide a link somewhere in your applications to the Open Data Network with a citation that states: "Data for this application was provided by the Open Data Network" where "Open Data Network" links to http://opendatanetwork.com. Where an application has a region specific module, we ask that you add an additional line that states: "Data about REGIONX was provided by the Open Data Network." where REGIONX is an HREF with a name for a geographical region like "Seattle, WA" and the link points to this page URL, e.g. http://opendatanetwork.com/region/1600000US5363000/Seattle_WA

Geographic and Population Datasets Involving Murphysboro, IL or Hillsboro, IL

  • API

    Sex Offenders

    data.cityofchicago.org | Last Updated 2022-01-21T10:58:16.000Z

    Description: Pursuant to the Sex Offender and Child Murderer Community Notification Law, 730 ILCS 152/101,et seq., the Chicago Police Department maintains a list of sex offenders residing in the City of Chicago who are required to register under the Sex Offender Registration Act, 730 ILCS 150/2, et seq. To protect the privacy of the individuals, addresses are shown at the block level only and specific locations are not identified. The data are extracted from the CLEAR (Citizen Law Enforcement Analysis and Reporting) system developed by the Department. Although every effort is made to keep this list accurate and current, the city cannot guarantee the accuracy of this information. Offenders may have moved and failed to notify the Chicago Police Department as required by law. If any information presented in this web site is known to be outdated, please contact the Chicago Police Department at srwbmstr@chicagopolice.org, or mail to Sex Registration Unit, 3510 S Michigan Ave, Chicago, IL 60653. Disclaimer: This registry is based upon the legislature's decision to facilitate access to publicly available information about persons convicted of specific sexual offenses. The Chicago Police Department has not considered or assessed the specific risk of re-offense with regard to any individual prior to his or her inclusion within this registry, and has made no determination that any individual included within the registry is currently dangerous. Individuals included within this registry are included solely by virtue of their conviction record and Illinois law. The main purpose of providing this data on the internet is to make the information more available and accessible, not to warn about any specific individual. Anyone who uses information contained in the Sex Offender Database to commit a criminal act against another person is subject to criminal prosecution. Data Owner: Chicago Police Department. Frequency: Data is updated daily. Related Applications: CLEARMAP (http://j.mp/lLluSa).

  • API

    CPS Schools 2013-2014 Academic Year

    data.cityofchicago.org | Last Updated 2013-11-26T20:27:57.000Z

    List of CPS schools for the 2013-2014 academic year. This dataset includes various identifiers used to identify school districts, including names; local, state, and federal IDs; and geographic descriptions on the location of each school.

  • API

    JULIE Service Requests

    naperville.data.socrata.com | Last Updated 2021-07-28T18:37:12.000Z

    Number of Joint Utility Locating Information for Excavators (JULIE) Requests Serviced by Electric Utility per month

  • API

    Downbound Grain Barge Rates

    internal.agtransport.usda.gov | Last Updated 2022-01-20T17:30:12.000Z

    Weekly barge rates for downbound freight originating from seven locations along the Mississippi River System, which includes the Mississippi River and its tributaries (e.g., Upper Mississippi River, Illinois River, Ohio River, etc.). The seven locations are: (1) "Twin Cities," a stretch along the Upper Mississippi; (2) "Mid-Mississippi," a stretch between eastern Iowa and western Illinois; (3) "Illinois River," along the lower portion of the Illinois River; (4) "St. Louis"; (5) "Cincinnati," along the middle third of the Ohio River; (6) "Lower Ohio," approximately the final third of the Ohio River; and (7) "Cairo-Memphis," from Cairo, IL, to Memphis, TN (see map under Attachments). The U.S. Inland Waterway System utilizes a percent-of-tariff system to establish barge freight rates. The tariffs were originally from the Bulk Grain and Grain Products Freight Tariff No. 7, which were issued by the Waterways Freight Bureau (WFB) of the Interstate Commerce Commission (ICC). In 1976, the United States Department of Justice entered into an agreement with the ICC and made Tariff No. 7 no longer applicable. Today, the WFB no longer exists, and the ICC has become the Surface Transportation Board, which does not have jurisdiction over barge rates on the inland waterways. However, the barge industry continues to use the tariffs as benchmarks for rate units. Each city on the river has its own benchmark, with the northern most cities having the highest benchmarks. They are as follows: Twin Cities = 619; Mid-Mississippi = 532; St. Louis = 399; Illinois = 464; Cincinnati = 469; Lower Ohio = 446; and Cairo-Memphis = 314. To calculate the rate in dollars per ton, multiply the percent of tariff rate by the 1976 benchmark and divide by 100: (Rate * 1976 tariff benchmark rate per ton)/100. As an example, a 271 percent tariff for a St. Louis grain barge would equal 271 percent of the St. Louis benchmark rate of $3.99, or $10.81 per ton.

  • API

    Strategic Vacant Anchors

    naperville.data.socrata.com | Last Updated 2018-09-26T18:58:06.000Z

    Location information and building attributes of the identified Strategic Anchors in Naperville, IL.

  • API

    Daily Loading Profile 2012-Present

    naperville.data.socrata.com | Last Updated 2019-08-16T20:09:55.000Z

    Citywide total daily electric load (usage) measured hourly, presented here as a daily total beginning on January 1, 2012 through last updated date.

  • API

    Monthly Grain and Fertilizer Barge Movements

    internal.agtransport.usda.gov | Last Updated 2022-01-07T19:49:09.000Z

    This file contains monthly grain and fertilizer barge movements for selected locks on Mississippi River, Ohio River, Illinois River, Arkansas River, and Columbia River.

  • API

    Traffic Crashes - Vehicles

    data.cityofchicago.org | Last Updated 2022-01-21T15:58:12.000Z

    This dataset contains information about vehicles (or units as they are identified in crash reports) involved in a traffic crash. This dataset should be used in conjunction with the traffic Crash and People dataset available in the portal. “Vehicle” information includes motor vehicle and non-motor vehicle modes of transportation, such as bicycles and pedestrians. Each mode of transportation involved in a crash is a “unit” and get one entry here. Each vehicle, each pedestrian, each motorcyclist, and each bicyclist is considered an independent unit that can have a trajectory separate from the other units. However, people inside a vehicle including the driver do not have a trajectory separate from the vehicle in which they are travelling and hence only the vehicle they are travelling in get any entry here. This type of identification of “units” is needed to determine how each movement affected the crash. Data for occupants who do not make up an independent unit, typically drivers and passengers, are available in the People table. Many of the fields are coded to denote the type and location of damage on the vehicle. Vehicle information can be linked back to Crash data using the “CRASH_RECORD_ID” field. Since this dataset is a combination of vehicles, pedestrians, and pedal cyclists not all columns are applicable to each record. Look at the Unit Type field to determine what additional data may be available for that record. The Chicago Police Department reports crashes on IL Traffic Crash Reporting form SR1050. The crash data published on the Chicago data portal mostly follows the data elements in SR1050 form. The current version of the SR1050 instructions manual with detailed information on each data elements is available <a href="https://idot.illinois.gov/Assets/uploads/files/Transportation-System/Manuals-Guides-&-Handbooks/Safety/Illinois Traffic Crash Report SR 1050 Instruction Manual 2019.pdf">here</a>.

  • API

    Traffic Crashes - People

    data.cityofchicago.org | Last Updated 2022-01-22T04:02:53.000Z

    This data contains information about people involved in a crash and if any injuries were sustained. This dataset should be used in combination with the traffic Crash and Vehicle dataset. Each record corresponds to an occupant in a vehicle listed in the Crash dataset. Some people involved in a crash may not have been an occupant in a motor vehicle, but may have been a pedestrian, bicyclist, or using another non-motor vehicle mode of transportation. Injuries reported are reported by the responding police officer. Fatalities that occur after the initial reports are typically updated in these records up to 30 days after the date of the crash. Person data can be linked with the Crash and Vehicle dataset using the “CRASH_RECORD_ID” field. A vehicle can have multiple occupants and hence have a one to many relationship between Vehicle and Person dataset. However, a pedestrian is a “unit” by itself and have a one to one relationship between the Vehicle and Person table. The Chicago Police Department reports crashes on IL Traffic Crash Reporting form SR1050. The crash data published on the Chicago data portal mostly follows the data elements in SR1050 form. The current version of the SR1050 instructions manual with detailed information on each data elements is available <a href="https://idot.illinois.gov/Assets/uploads/files/Transportation-System/Manuals-Guides-&-Handbooks/Safety/Illinois Traffic Crash Report SR 1050 Instruction Manual 2019.pdf">here</a>.

  • API

    Downbound Grain Barge Rates: One Month Future Rates

    internal.agtransport.usda.gov | Last Updated 2022-01-20T17:28:44.000Z

    Weekly barge rates in future months for downbound freight originating from seven locations along the Mississippi River System. This dataset contains rates for transactions one month in the future. The seven locations are: (1) "Twin Cities," a stretch along the Upper Mississippi; (2) "Mid-Mississippi," a stretch between eastern Iowa and western Illinois; (3) "Illinois River," along the lower portion of the Illinois River; (4) "St. Louis"; (5) "Cincinnati," along the middle third of the Ohio River; (6) "Lower Ohio," approximately the final third of the Ohio River; and (7) "Cairo-Memphis," from Cairo, IL, to Memphis, TN. The U.S. Inland Waterway System utilizes a percent-of-tariff system to establish barge freight rates. The tariffs were originally from the Bulk Grain and Grain Products Freight Tariff No. 7, which were issued by the Waterways Freight Bureau (WFB) of the Interstate Commerce Commission (ICC). In 1976, the United States Department of Justice entered into an agreement with the ICC and made Tariff No. 7 no longer applicable. Today, the WFB no longer exists, and the ICC has become the Surface Transportation Board, which does not have jurisdiction over barge rates on the inland waterways. However, the barge industry continues to use the tariffs as benchmarks for rate units. Each city on the river has its own benchmark, with the northern most cities having the highest benchmarks. They are as follows: Twin Cities = 619; Mid-Mississippi = 532; St. Louis = 399; Illinois = 464; Cincinnati = 469; Lower Ohio = 446; and Cairo-Memphis = 314. To calculate the rate in dollars per ton, multiply the percent of tariff rate by the 1976 benchmark and divide by 100: (Rate * 1976 tariff benchmark rate per ton)/100. As an example, a 271 percent tariff for a St. Louis grain barge would equal 271 percent of the St. Louis benchmark rate of $3.99, or $10.81 per ton.