The interactive map creation tools market is experiencing robust growth, driven by increasing demand for visually engaging data representation across diverse sectors. The market's value is estimated at $2 billion in 2025, exhibiting a Compound Annual Growth Rate (CAGR) of 15% from 2025 to 2033. This growth is fueled by several factors, including the rising adoption of location-based services, the proliferation of readily available geographic data, and the growing need for effective data visualization in business intelligence and marketing. The individual user segment currently holds a significant share, but corporate adoption is rapidly expanding, propelled by the need for sophisticated map-based analytics and internal communication. Furthermore, the paid use segment is anticipated to grow more quickly than the free use segment, reflecting the willingness of businesses and organizations to invest in advanced features and functionalities. This trend is further amplified by the increasing integration of interactive maps into various platforms, such as business intelligence dashboards and website content. Geographic expansion is also a significant growth driver. North America and Europe currently dominate the market, but the Asia-Pacific region is showing significant promise due to rapid technological advancements and increasing internet penetration. Competitive pressures remain high, with established players such as Google, Mapbox, and ArcGIS StoryMaps vying for market share alongside innovative startups offering specialized solutions. The market's restraints are primarily focused on the complexities of data integration and the technical expertise required for effective map creation. However, ongoing developments in user-friendly interfaces and readily available data integration tools are mitigating these challenges. The future of the interactive map creation tools market promises even greater innovation, fueled by developments in augmented reality (AR), virtual reality (VR), and 3D visualization technologies. We expect to see the emergence of more sophisticated tools catering to niche requirements, further driving market segmentation and specialization. Continued investment in research and development will also play a crucial role in pushing the boundaries of what's possible with interactive map creation. The market presents opportunities for companies to develop tools which combine data analytics and interactive map design.

This web map shows the location of individual impounding reservoirs in Hong Kong. It is a set of data made available by the Water Supplies Department under the Government of Hong Kong Special Administrative Region (the "Government") at https://portal.csdi.gov.hk ("CSDI Portal"). The source data has been processed and converted into Esri File Geodatabase format and uploaded to Esri's ArcGIS Online platform for sharing and reference purpose. The objectives are to facilitate our Hong Kong ArcGIS Online users to use the data in a spatial ready format and save their data conversion effort.For details about the data, source format and terms of conditions of usage, please refer to the website of Hong Kong CSDI Portal at https://portal.csdi.gov.hk.

Please read: This dataset provides linear geometries against which official road names and street addresses can be recorded. Its purpose is also to enable automated meshblock address reports (for electoral and statistical purposes) so as to identify the presence of a road name in meshblocks where street addresses do not exist.

For this dataset (as opposed to the NZ Roads Subsections (Addressing) dataset, individual road section geometries have been aggregated to a single road centreline geometry where those subsections share the same name, and are generally contiguous. Because some roads have multiple names for part of their lengths, some road centreline geometries will duplicate parts of other roads even though there is in reality only one road formation. This dataset has been simplified from LINZ’s NZ Roads dataset, a centralised database for the management of national road data. The comprehensive set of NZ Roads tables is also available.

These road centrelines do not represent actual road formation, nor do they represent legal access. They must not be considered as topographic, cadastral, or legal.

This dataset contains the core attributes of a road to support simple searching or provide a road name context for cadastral data views. Please refer to the NZ Roads Data Dictionary for detailed metadata and information about this dataset.

APIs and web services This dataset is available via ArcGIS Online and ArcGIS REST services, as well as our standard APIs. LDS APIs and OGC web services ArcGIS Online map services

This collection contains individual story maps for the various components of the proposed approach to environmental analysis in support of the One Seattle Plan. The collection supports the scoping process for the Plan's Environmental Impact Statement (EIS). The purpose of the scoping process is to gather input from stakeholders and the general public on topics and areas of concern that should be addressed in the EIS, as well as sharing draft plan alternatives.The City of Seattle is updating its Comprehensive Plan. The Seattle Comprehensive Plan is the vision for how our city grows and makes investments. The Plan guides City decisions about where we locate housing and jobs, and where we invest in transportation, utilities, parks, and other public assets. Our goal is to make the city more equitable, livable, sustainable, and resilient for today’s communities and future residents.The updated Plan, which we are calling the One Seattle Plan, will address new and long-standing challenges including racial equity, housing costs, access to economic opportunity and education, climate change, and more. It will explore different approaches to growth and investment, along with new strategies to reduce displacement pressures. The One Seattle Plan project was launched in March 2022 with the goal of adopting an updated Plan in 2024. This story map provides background on the process of creating an approach for the project’s environmental analysis, or scoping. Scoping is required by the State Environmental Policy Act in order to solicit public feedback on what we are proposing to analyze. As part of scoping, we are also seeking feedback on a range of approaches toward guiding growth that we will analyze as part of the environmental analysis — these are called draft growth strategy alternatives. This comment period will run from June 23 to August 22, 2022.

This layer presents the best-known point and perimeter locations of wildfire occurrences within the United States over the past 7 days. Points mark a location within the wildfire area and provide current information about that wildfire. Perimeters are the line surrounding land that has been impacted by a wildfire.Consumption Best Practices:As a service that is subject to Viral loads (very high usage), avoid adding Filters that use a Date/Time type field. These queries are not cacheable and WILL be subject to Rate Limiting by ArcGIS Online. To accommodate filtering events by Date/Time, we encourage using the included "Age" fields that maintain the number of Days or Hours since a record was created or last modified compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be supplied to many users without adding load on the service.When ingesting this service in your applications, avoid using POST requests, these requests are not cacheable and will also be subject to Rate Limiting measures.Source:  Wildfire points are sourced from Integrated Reporting of Wildland-Fire Information (IRWIN) and perimeters from National Interagency Fire Center (NIFC). Current Incidents: This layer provides a near real-time view of the data being shared through the Integrated Reporting of Wildland-Fire Information (IRWIN) service. IRWIN provides data exchange capabilities between participating wildfire systems, including federal, state and local agencies. Data is synchronized across participating organizations to make sure the most current information is available. The display of the points are based on the NWCG Fire Size Classification applied to the daily acres attribute.Current Perimeters: This layer displays fire perimeters posted to the National Incident Feature Service. It is updated from operational data and may not reflect current conditions on the ground. For a better understanding of the workflows involved in mapping and sharing fire perimeter data, see the National Wildfire Coordinating Group Standards for Geospatial Operations.Update Frequency:  Every 15 minutes using the Aggregated Live Feed Methodology based on the following filters:Events modified in the last 7 daysEvents that are not given a Fire Out DateIncident Type Kind: FiresIncident Type Category: Prescribed Fire, Wildfire, and Incident ComplexArea Covered: United StatesWhat can I do with this layer? The data includes basic wildfire information, such as location, size, environmental conditions, and resource summaries. Features can be filtered by incident name, size, or date keeping in mind that not all perimeters are fully attributed.Attribute InformationThis is a list of attributes that benefit from additional explanation. Not all attributes are listed.Incident Type Category: This is a breakdown of events into more specific categories.Wildfire (WF) -A wildland fire originating from an unplanned ignition, such as lightning, volcanos, unauthorized and accidental human caused fires, and prescribed fires that are declared wildfires.Prescribed Fire (RX) - A wildland fire originating from a planned ignition in accordance with applicable laws, policies, and regulations to meet specific objectives.Incident Complex (CX) - An incident complex is two or more individual incidents in the same general proximity that are managed together under one Incident Management Team. This allows resources to be used across the complex rather than on individual incidents uniting operational activities.IrwinID: Unique identifier assigned to each incident record in both point and perimeter layers.Acres: these typically refer to the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.Discovery: An estimate of acres burning upon the discovery of the fire.Calculated or GIS:  A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire.Daily: A measure of acres reported for a fire.Final: The measure of acres within the final perimeter of a fire. More specifically, the number of acres within the final fire perimeter of a specific, individual incident, including unburned and unburnable islands.Dates: the various systems contribute date information differently so not all fields will be populated for every fire.FireDiscovery: The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes. Containment: The date and time a wildfire was declared contained. Control: The date and time a wildfire was declared under control.ICS209Report: The date and time of the latest approved ICS-209 report.Current: The date and time a perimeter is last known to be updated.FireOut: The date and time when a fire is declared out.ModifiedOnAge: (Integer) Computed days since event last modified.DiscoveryAge: (Integer) Computed days since event's fire discovery date.CurrentDateAge: (Integer) Computed days since perimeter last modified.CreateDateAge: (Integer) Computed days since perimeter entry created.GACC: A code that identifies one of the wildland fire geographic area coordination centers. A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.Fire Mgmt Complexity: The highest management level utilized to manage a wildland fire event.Incident Management Organization: The incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.Unique Fire Identifier: Unique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = Point Of Origin (POO) protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters)RevisionsJan 4, 2021: Added Integer fields 'Days Since...' to Current_Incidents point layer and Current_Perimeters polygon layer. These fields are computed when the data is updated, reflecting the current number of days since each record was last updated. This will aid in making 'age' related, cache friendly queries.Mar 12, 2021: Added second set of 'Age' fields for Event and Perimeter record creation, reflecting age in Days since service data update.Apr 21, 2021: Current_Perimeters polygon layer is now being populated by NIFC's newest data source. A new field was added, 'IncidentTypeCategory' to better distinguish Incident types for Perimeters and now includes type 'CX' or Complex Fires. Five fields were not transferrable, and as a result 'Comments', 'Label', 'ComplexName', 'ComplexID', and 'IMTName' fields will be Null moving forward.Apr 26, 2021: Updated Incident Layer Symbology to better clarify events, reduce download size and overhead of symbols. Updated Perimeter Layer Symbology to better distingish between Wildfires and Prescribed Fires.May 5, 2021: Slight modification to Arcade logic for Symbology, refining Age comparison to Zero for fires in past 24-hours.Aug 16, 2021: Enabled Time Series capability on Layers (off by default) using 'Fire Discovery Date' for Incidents and 'Creation Date' for Perimeters.This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

Florida COVID-19 Cases by Zip Code exported from the Florida Department of Health GIS Layer on date seen in file name. Archived by the University of South Florida Libraries, Digital Heritage and Humanities Collections. Contact: LibraryGIS@usf.edu.Please Cite Our GIS HUB. If you are a researcher or other utilizing our Florida COVID-19 HUB as a tool or accessing and utilizing the data provided herein, please provide an acknowledgement of such in any publication or re-publication. The following citation is suggested: University of South Florida Libraries, Digital Heritage and Humanities Collections. 2020-2021. Florida COVID-19 Hub. Available at https://covid19-usflibrary.hub.arcgis.com/.https://doi.org/10.5038/USF-COVID-19-GISLive FDOH Data Source: https://services1.arcgis.com/CY1LXxl9zlJeBuRZ/arcgis/rest/services/Florida_Cases_Zips_COVID19/FeatureServerFor data 5/10/2020 or after: Archived data was exported directly from the live FDOH layer into the archive. For data prior to 5/10/2020: Data was exported by the University of South Florida - Digital Heritage and Humanities Collection using ArcGIS Pro Software. Data was then converted to shapefile and csv and uploaded into ArcGIS Online archive. For data definitions please visit the following box folder: https://usf.box.com/s/vfjwbczkj73ucj19yvwz53at6v6w614hData definition files names include the relative date they were published. The below information was taken from ancillary documents associated with the original layer from FDOH.Q. How is the zip code assigned to a person or case? Cases are counted in a zip code based on residential or mailing address, or by healthcare provider or lab address if other addresses are missing.Q. Why is the city data and the zip code data different? The zip code data is supplied to a healthcare worker, case manager, or lab technician by each individual during intake when a test is first recorded. When entering a zip code, the system we use automatically produces a list of cities within that zip code for the individual to further specify where they live. Sometimes the individual uses the postal city, which may be Miami, when in reality that person lives outside the City of Miami boundaries in the jurisdiction of Coral Gables. Many zip codes contain multiple city/town jurisdictions, and about 20% of zip codes overlap more than one county. Q: How is the Zip Code data calculated and/or shown? If a COUNTY has five or more cases (total): • In zip codes with fewer than 5 cases, the total number of cases is shown as “<5”. • Zip codes with 0 cases in these counties are “0" or "No cases.” • All values of 5 or greater are shown by the actual number of cases in that zip code. If a COUNTY has fewer than five total cases across all of its zip codes, then ALL of the zip codes within that county show the total number of cases as "Suppressed." Q: My zip code says "SUPPRESSED" under cases. What does that mean? IF Suppressed: This county currently has fewer than five cases across all zip codes in the county. In an effort to protect the privacy of our COVID-19-Positive residents, zip code data is only available in counties where five or more cases have been reported. Q: What about PO Box zip codes, or zip codes with letters, like 334MH? PO Box zip codes are not shown in the map. “Filler” zip codes with letters, like 334MH, are typically areas where no or very few people live – like the Florida Everglades, and are shown on the map like any other zip code. Key Data about Cases by Zip Code: ZIP = The zip code COUNTYNAME = The county for the zip code (multi-part counties have been split) ZIPX = The unique county-zip identifier used to pair the data during updates POName = The postal address name assigned to the zip code place_labels = A list of the municipalities intersecting the zip code boundary c_places = The list of cities cases self-reported as being residents of Cases_1 = The number of cases in each zip code, with conditions*LabelY = A calculated field for map display only. All questions regarding this dataset should be directed to the Florida Department of Health.

This data set contains a national scale spatial footprint of the outer boundaries of the Bureau of Ocean Energy Management’s (BOEM’s) Official Protraction Diagrams (OPDs) and Leasing Maps (LMs). It is updated as needed. OPDs and LMs are mapping products produced and used by the BOEM to delimit areas available for potential offshore mineral leases, determine the State/Federal offshore boundaries, and determine the limits of revenue sharing and other boundaries to be considered for leasing offshore waters. This dataset shows only the outline of the maps that are available from BOEM.Only the most recently published paper or pdf versions of the OPDs or LMs should be used for official or legal purposes. The pdf maps can be found by going to the following link and selecting the appropriate region of interest. http://www.boem.gov/Oil-and-Gas-Energy-Program/Mapping-and-Data/Index.aspx Both OPDs and LMs are further subdivided into individual Outer Continental Shelf (OCS) blocks which are available as a separate layer. Some OCS blocks that also contain other boundary information are known as Supplemental Official Block Diagrams (SOBDs.) Further information on the historic development of OPD's can be found in OCS Report MMS 99-0006: Boundary Development on the Outer Continental Shelf: http://www.boemre.gov/itd/pubs/1999/99-0006.PDF Also see the metadata for each of the individual GIS data layers available for download. The Official Protraction Diagrams (OPDs) and Supplemental Official Block Diagrams (SOBDs), serve as the legal definition for BOEM offshore boundary coordinates and area descriptions.