Places Portfolio Product Announcements

 View Only

WPPOIs, Places, and Place Insights: Product Scope & Schema Changes

  Thread closed by the administrator, not accepting new replies.
  • 1.  WPPOIs, Places, and Place Insights: Product Scope & Schema Changes

    Posted 3 hours ago
    Edited by Product Communications 3 hours ago
    No replies, thread closed.

    01 June 2026

    WPPOIs, Places, and Place Insights: Product Scope & Schema Changes


    Abstract

    If you are a World Premium Points of Interest (WPPOI) or Places customer, please read this very important Product Announcement. WPPOIs will retire at the end of this year, and all customers will transition to the newly enhanced Physical Places product. The inspiration for such changes, product impact details, and timing can be found below.

    Mission
    Precisely Places and Point of Interest products offer vast coverage and serve a wide range of customer use cases. Across use cases, it's rare that "customer A" requires the same subset of data as "customer B." This means building a discoverable solution is equally as important as building a comprehensive solution.

    In the pursuit of building discoverable solutions, we are introducing a series of product scope and comprehension improvements guided by the following goals:

    • Help customers identify the most relevant data to their problem statement
    • Boost the likelihood that product queries return the desired subset of data

    For customers, this will provide a cleaner, more intuitive search experience with less noise, fewer irrelevant records, and greater confidence that the data you find is the data you need. For Precisely, committing to opinionated definitions will allow us to better evaluate product quality and communicate its contents and utility to the market.

    Physical Places: Scope & Schema Enhancements
    We are concretely defining what constitutes a "Place," and, perhaps more importantly, what does not. Through close customer guidance, we have determined that a place must occupy a real-world, physical footprint that is distinct from other places. In other words, if a human can physically touch, interact, or exist within the distinct place, then it's a candidate for inclusion in our, aptly renamed, Physical Places product (previously named "Places"). The following are Physical Place examples (not exhaustive):

     

    • Consumer: Retail, restaurants, grocery stores, gas stations, malls, stadiums, etc.
      • Ex: "Target" located at "4301 Lien Rd, Madison, WI 53704"

    • Professional: Lawyers, accountants, insurance agents, doctors, business consultants, etc.
      • Ex: "Dr. David W. Fabi" located at "4060 Fourth Ave Fl 7, San Diego, CA 92103"

    • Public and Non-consumer: Places of worship, schools, parks, museums, etc.
      • Ex: "St. Peter's Catholic Church" located at "110 W Madison St, Chicago, IL 60602"

    • Small Places: ATMs, EV chargers, transit stops, etc.
      • Ex: "Bank of America ATM" located at "834 State St, Santa Barbara, CA 93101"

    • Service Area: Businesses that operate from a distinct location but deliver goods/services at the customer location like a cleaning or plumbing service.
      • Ex: "Kerwin Plumbing & Heating" located at "1704 Teller St, Broomfield, CO 80020"


    "Digital Places,"
    on the other hand, do not occupy a distinct, real-world footprint and often cluster around a single building or address. E-commerce shops and technology companies are canonical examples, but millions of businesses of all kinds register to "virtual addresses" simply for tax and legislative purposes. Despite their existence on paper, no one is home, and no one is ever meant to visit.

    • Digital Place Example: "Allcloud USA LLC" associated with "1580 N Logan St Ste 660 PMB 93487, Denver, CO 80203"
      • More than 1,100 businesses are associated with this suite number alone.


    Forcing physical and digital places into the same product results in an unreasonably large universe of data, and it often requires complex, post-processing queries to isolate the desired subset from the masses. This is a poor customer experience that will be radically improved by enforcing mutually exclusive product scopes. Effective the May 2026 release, >30mm Digital Places have been removed from the Physical Places product and its associated Place Insights files (Firmographics, Corporate Lineage, and Equities) in the US. We are continuously improving our ability to detect and remove these records, and non-US countries will see digital removal in the June release.

    We are also eager to release a more sensible schema that better reflects the contents of the product. Like the product's scope, each field should adhere to a narrow definition that is mutually exclusive from other fields, and that can be effectively assessed for accuracy. This change will enable more logical reasoning between customer problem statements and relevant product fields.

    Effective the June 2026 release, Physical Places and its accompanying Place Insights files (Firmographics, Corporate Lineage, and Equities) will have updated schemas and updated product file names across all available countries. Product files will be renamed to reflect the updated "Physical Places" product name, and fields will change in one or more of the following ways:

    • Name change
    • Description change
    • Length change
    • Field addition
    • Field removal

    Please reference the attached supporting resources to learn more about the changes taking effect the June 2026 release:

    • physical_places_files.xlsx – updated folder contents and file names
    • physical_places_data_schema.xlsx – updated schema for core file
    • physical_places_firmographics_data_schema.xlsx – updated schema for firmographics file
    • physical_places_corporate_lineage_data_schema.xlsx – updated schema for corporate lineage file
    • physical_places_equities_data_schema.xlsx – updated schema for equities file
    • physical_places_old_new_schema_mapping.xlsx – mapping of old vs new field names, definitions, etc. (physical places core + insights files)


    Timeline: Physical Places Scope & Schema Enhancements



    World Premium Points of Interest Transition

    We are rapidly scaling the footprint of Physical Places to achieve global parity with WPPOIs by the end of 2026. Once coverage parity is achieved, a new product containing only the "Digital Places" will be made available, and WPPOIs will age into retirement. 2026.12 will be the final WPPOIs release.

    Effective the June 2026 release, all WPPOI customers will receive monthly deliveries of Physical Places (and its accompanying Firmographics, Corporate Lineage, and Equities files) in parallel with WPPOIs for each country licensed.

    • Please note that some countries will not have Physical Places available in June 2026, and countries will be added immediately upon availability.

    Parallel deliveries will continue through the end of the year and are intended to ease the burden of transitioning from the WPPOIs to the Physical Places schema. WPPOIs contains all fields in a single file whereas Physical Places distributes fields across 4 separate files that are grouped by likeness and joinable on PlaceID (unique product ID). Please reference the attached supporting resources to learn more about Physical Places and for guidance locating WPPOI fields in Physical Places files:

    • physical_places_files.xlsx – folder contents and file names
    • physical_places_data_schema.xlsx – schema for physical places core file
    • physical_places_firmographics_data_schema.xlsx – schema for firmographics file
    • physical_places_corporate_lineage_data_schema.xlsx – schema for corporate lineage file
    • physical_places_equities_data_schema.xlsx – schema for equities file
    • wppois_physical_places_schema_mapping.xlsx – mapping of all WPPOI fields to their counterparts in Physical Places

    Property Graph Customers: The following Property Graph relationship classes are currently derived from WPPOIs:

    • Relationship Class 5 (Address and Point of Interest)
    • Relationship Class 8 (Parcel Boundary and Point of Interest)
    • Relationship Class 10 (Building Footprint and Point of Interest)

    In anticipation of WPPOIs retiring at the end of year, these relationship classes will be derived from Physical Places beginning in H2 2026. Please note, this is not a schema breaking change. Please refer to the Property Graph Release Notes - Future Update Sections for which Property Graph release will reflect this change.

    If your use case requires "Digital Places," fear not! These will remain in the WPPOIs product through 2026 and will soon exist in a new product named "Digital Places."

    Digital Places, scheduled for release in Q4 2026, will use the same schemas as Physical Places and Place Insights. This product will only include the "digital" places that are intentionally excluded from Physical Places (see the "Physical Places Scope" section above). If needed, Digital Places can be added to your license at no additional cost upon request.


    Timeline: World Premium Points of Interest Transition

     

    Supporting Resources

    Please refer to the attached resources as referenced in the sections above:

    • physical_places_files.xlsx – folder contents and file names (effective 2026.06 release)
    • physical_places_data_schema.xlsx – schema for physical places core file (effective 2026.06 release)
    • physical_places_firmographics_data_schema.xlsx – schema for firmographics file (effective 2026.06 release)
    • physical_places_corporate_lineage_data_schema.xlsx – schema for corporate lineage file (effective 2026.06 release)
    • physical_places_equities_data_schema.xlsx – schema for equities file (effective 2026.06 release)
    • physical_places_old_new_schema_mapping.xlsx – mapping of old to new field names, definitions, etc. for physical places & place insights (effective 2026.06 release)
    • wppois_physical_places_schema_mapping.xlsx – mapping of all WPPOI fields to their counterparts in Physical Places

     

    Contact Information

    If you would like technical assistance, please contact the Precisely Global Support team at Precisely Support.

    Product documentation is available in the Precisely Help Center at help.precisely.com.  

    Any questions relating to this announcement should be directed to Bryan Bonack, Senior Director Product Management, at bryan.bonack@precisely.com