[ENHANCEMENT] Remove old categories in favor of the new taxonomy field [Target: September release]

counterexamples/places/bad-address-invalid-property.yaml

@@ -11,8 +11,6 @@ properties:
   version: 0
   names:
     primary: Fancy POI with invalid address property (region2)
-  categories:
-    primary: some_category
   addresses:
     - freeform: "770 Broadway, Floor 8"
       locality: "New York"

counterexamples/places/bad-basic-category.yaml

@@ -1,5 +1,5 @@
 ---
-id: counterexample:place:bad-categories-values
+id: counterexample:place:bad-basic-category-values
 type: Feature
 geometry:
   type: Point

counterexamples/places/bad-empty-emails.yaml

@@ -5,8 +5,6 @@ geometry:
   type: Point
   coordinates: [0, 0]
 properties:
-  categories:
-    primary: some_category
   confidence: 0.9
   websites:
     - https://www.example.com

counterexamples/places/bad-empty-phones.yaml

@@ -5,8 +5,6 @@ geometry:
   type: Point
   coordinates: [0, 0]
 properties:
-  categories:
-    primary: some_category
   confidence: 0.9
   websites:
     - https://www.example.com

counterexamples/places/bad-empty-socials.yaml

@@ -5,8 +5,6 @@ geometry:
   type: Point
   coordinates: [0, 0]
 properties:
-  categories:
-    primary: some_category
   confidence: 0.9
   websites:
     - https://www.example.com

counterexamples/places/bad-empty-websites.yaml

@@ -5,8 +5,6 @@ geometry:
   type: Point
   coordinates: [0, 0]
 properties:
-  categories:
-    primary: some_category
   confidence: 0.9
   websites: []
   emails:

counterexamples/places/bad-geometry.yaml

@@ -8,5 +8,3 @@ properties:
   theme: places
   type: place
   version: 0
-  categories:
-    primary: a_category

counterexamples/places/bad-operating-status.yaml

@@ -5,9 +5,8 @@ geometry:
   type: Point
   coordinates: [0, 0]
 properties:
-  categories:
-    primary: some_category
   confidence: 0.9
+  websites:
     - https://www.example.com/
   emails:
     - info@example.com

docs/schema/0-Schema.mdx

@@ -56,7 +56,7 @@ In the Overture schema, all features have a unique `id` called a [GERS ID](https
 Most but not all of the feature types in the Overture schema require data for the `names`, `subtype`, and `class` properties. The `names` property is complex enough to have its own schema, which we describe in detail [here](/schema/concepts/names). 
 
 ### Properties may be specific to a feature type
-Some properties in the Overture schema are only populated with data for specific feature types. For example, the `place` feature type must include data for the `categories` property, as required by the schema. The `division_area` and `address` feature types require the `country` property to be populated with ISO 3166-1 alpha-2 country codes. The `segment` feature type in the transportation theme is the only feature type that includes data for a complex set of properties that describe roads. The [schema concepts](concepts) section of this documentation describes these complexities in detail.
+Some properties in the Overture schema are only populated with data for specific feature types. For example, the `place` feature type includes the `taxonomy` property. The `division_area` and `address` feature types require the `country` property to be populated with ISO 3166-1 alpha-2 country codes. The `segment` feature type in the transportation theme is the only feature type that includes data for a complex set of properties that describe roads. The [schema concepts](concepts) section of this documentation describes these complexities in detail.
 
 
 ## Schema conventions

docs/schema/concepts/by-theme/places/index.mdx

@@ -3,47 +3,6 @@ title: Places schema concepts
 description: everything you ever wanted to know about the places schema
 ---
 
-import overture_categories from '!!raw-loader!./overture_categories.csv';
-import CodeBlock from '@theme/CodeBlock';
-
-export const PlacesCategories = (args) => {
-
-    var lines = args.places.split('\n');
-    lines.shift(); // Remove the first line (the header)
-
-    var categories = {}
-
-    for (const line of lines) {
-        const parts = line.split(';');
-        const category = parts[0].trim();
-        if (parts[1] != undefined) {
-            var hierarchy = parts[1].trim().slice(1, (parts[1].trim().length - 1)).split(',');
-            if (categories[hierarchy[0]] == undefined){
-                categories[hierarchy[0]] = []
-            }
-            if (hierarchy.length>1){
-                categories[hierarchy[0]].push(category.padEnd(45, '.') + hierarchy.join(" > "));
-            }
-        }
-    };
-
-    var keys = Object.keys(categories).sort()
-
-    return (
-        <div>
-        {keys.map(cat => {
-            return(
-                <details><summary><strong>{cat}</strong></summary>
-                    <CodeBlock>
-                        {categories[cat].join("\n")}
-                    </CodeBlock>
-                </details>
-            )
-        })}
-        </div>
-      );
-}
-
 
 ## Overview
 
@@ -57,11 +16,11 @@ The places theme has one feature type:
 
 ## Theme concepts
 
-### Categories
-
-There are more than 2,000 possible category values for Overture Places. Below are the top-level categories, expand each one to see all possible categories and their hierarchies.
+### Taxonomy
 
-<PlacesCategories places={overture_categories}></PlacesCategories>
+Overture Places uses a taxonomy with more than 2,000 possible category values.
+Each place can provide a primary category, its hierarchy path, and optional alternate categories.
+See the place schema reference for the current taxonomy structure and examples.
 
 ## Schema reference