Jill8986/sync (#23)

* sync docs * sync format * sync service * sync readme
Esri · Apr 23, 2019 · bc1ad34 · bc1ad34
1 parent 5fb200d
commit bc1ad34
Show file tree

Hide file tree

Showing 33 changed files with 64 additions and 51 deletions.
diff --git a/README.md b/README.md
@@ -287,7 +287,7 @@ You are invited to fork this repository and to submit pull requests with ideas f
 
 ## License for indexed 3D scene format and REST endpoint specification
 
-Copyright 2015 - 2017 Esri
+Copyright &copy; 2015 - 2017 Esri
 
 The specification is licensed under the [Creative Commons Attribution-NoDerivatives 4.0 International Public License](https://creativecommons.org/licenses/by-nd/4.0/legalcode).
 You can implement the specification in services, clients or processing tools without restrictions.
@@ -316,6 +316,3 @@ Version 2.0 - present point cloud scene layer (01/01/2017 to present) of this sp
 ## License for JSON resources, validator, and examples
 
 The supplementary resources may be updated without notice and are provided for use under the [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) license and may be used, under the terms of that license, at your own risk.
-
-[](Esri Tags: I3S, Indexed 3D Scene Layer, Scene Layer, ArcGIS WebScene, Mesh-Pyramids, ArcGISOnline Scene Service, ArcGISServer, Scene Layer Package, SceneLayer, 3D Object, Point, IntegreatedMesh, PointCloud)
-[](Esri Language: JavaScript)
diff --git a/docs/1.6/3DSNodeIndexDocument.cmn.md → docs/1.6/3DNodeIndexDocument.cmn.md b/docs/1.6/3DSNodeIndexDocument.cmn.md → docs/1.6/3DNodeIndexDocument.cmn.md
diff --git a/docs/1.6/3Dobject_ReadMe.md b/docs/1.6/3Dobject_ReadMe.md
@@ -1,6 +1,6 @@
 # 3D Object Scene Layer
 
-A 3D object scene layer is used to visualize 3D objects.  3D object scene layers are often created from GIS data with attributes and explicitly modeled in 3D.  These attributes allow definition queries to specify symbology and other properties in lieu of setting properties for each object individually.  A 3D object scene layer can efficiently create and share just a few buildings or an entire city.  
+A 3D object scene layer is used to visualize 3D objects.  3D object scene layers are often created from GIS data with attributes and explicitly modeled in 3D.  These attributes allow definition queries to specify symbology and other properties in lieu of setting properties for each object individually.  A 3D object scene layer can efficiently create and share just a few buildings or an entire city.  An example schema can be found below and a 3D object scene layer can be downloaded from [this story map](<http://3dcities.maps.arcgis.com/apps/MapSeries/index.html?appid=444de19a88764d58885ea8e211e96ae8>).
 
 *Realistic 3D Object Scene Layer with textures*
 
@@ -15,7 +15,7 @@ The 3D object scene layer is structured into a tree of multiple JSON files. Besi
 
 - [Layer description](3DSceneLayer.cmn.md)
 - Nodes containing [Geometry](geometry.cmn.md) and [Attributes](attributeStorageInfo.cmn.md)
-- [Node Index Document](3DSNodeIndexDocument.cmn.md)
+- [Node Index Document](3DNodeIndexDocument.cmn.md)
 - [Statistics](statsInfo.cmn.md)
 
 *Example of 3DObject layer structure*

diff --git a/docs/1.6/IntegratedMesh_ReadMe.md b/docs/1.6/IntegratedMesh_ReadMe.md
@@ -1,6 +1,6 @@
 # Integrated Mesh Scene Layer
 
-Integrated mesh scene layers are generally created for citywide 3D mapping.  Integrated mesh scene layers include an entire surface and cannot be restyled.  Three-dimensional mesh data are typically captured by an automated process (e.g. drone) for constructing 3D objects out of large sets of overlapping imagery. The result integrates the original input image information as a textured mesh including 3D objects, such as buildings and trees, and elevation information.
+Integrated mesh scene layers are generally created for citywide 3D mapping.  Integrated mesh scene layers include an entire surface and cannot be restyled.  Three-dimensional mesh data are typically captured by an automated process (e.g. drone) for constructing 3D objects out of large sets of overlapping imagery. The result integrates the original input image information as a textured mesh including 3D objects, such as buildings and trees, and elevation information. An example schema can be found below and an integrated mesh scene layer can be downloaded from [this story map](<http://3dcities.maps.arcgis.com/apps/MapSeries/index.html?appid=444de19a88764d58885ea8e211e96ae8>).
 
 *Example of integrated mesh scene layer*
 

diff --git a/docs/1.6/Point_ReadMe.md b/docs/1.6/Point_ReadMe.md
@@ -1,6 +1,6 @@
 # Point Scene Layer
 
-Point scene layers contain point features and their attributes. Point scene layers are often used to visualize large amounts of 3D data like trees or buildings.  Most phenomena that can be visualized by 3D symbols can be displayed with a point scene layers.
+Point scene layers contain point features and their attributes. Point scene layers are often used to visualize large amounts of 3D data like trees or buildings.  Most phenomena that can be visualized by 3D symbols can be displayed with a point scene layers. An example schema can be found below and a point scene layer can be downloaded from [this story map](<http://3dcities.maps.arcgis.com/apps/MapSeries/index.html?appid=444de19a88764d58885ea8e211e96ae8>).
 
 *Example of a point scene layer*
 
@@ -11,7 +11,7 @@ The point scene layer is structured into a tree of multiple JSON files. Besides
 
 - [Layer description](3DSceneLayer.psl.md)
 - Nodes containing [Geometry](geometry.cmn.md) and [Attributes](attributeStorageInfo.cmn.md)
-- [Node Index Document](3DSNodeIndexDocument.cmn.md)
+- [Node Index Document](3DNodeIndexDocument.cmn.md)
 - [Statistics](statisticsInfo.cmn.md)
 
 *Example of point scene layer structure*

diff --git a/docs/1.6/attributeStorageInfo.cmn.md b/docs/1.6/attributeStorageInfo.cmn.md
@@ -4,7 +4,7 @@ An object that describes the structure of the binary attribute data resource of
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/cachedDrawingInfo.cmn.md b/docs/1.6/cachedDrawingInfo.cmn.md
@@ -4,7 +4,7 @@
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/drawingInfo.cmn.md b/docs/1.6/drawingInfo.cmn.md
@@ -4,7 +4,7 @@ The drawingInfo object contains drawing information for a scene layer.
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/elevationInfo.cmn.md b/docs/1.6/elevationInfo.cmn.md
@@ -4,7 +4,7 @@ An object defining where a feature is placed within a scene. For example, on the
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/field.cmn.md b/docs/1.6/field.cmn.md
@@ -4,7 +4,7 @@ A collection of objects describing each attribute field.
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/geometryAttribute.cmn.md b/docs/1.6/geometryAttribute.cmn.md
@@ -4,7 +4,7 @@ Each GeometryAttribute object is an accessor, i.e. a view, into an arraybuffer.
 
 ### Related:
 
-[cmn::vestedGeometryParams](vestedGeometryParams.cmn.md), [cmn::geometryFeature](geometryFeature.cmn.md), [cmn::vertexAttribute](vertexAttribute.cmn.md)
+[cmn::geometryFeature](geometryFeature.cmn.md), [cmn::vertexAttribute](vertexAttribute.cmn.md), [cmn::vestedGeometryParams](vestedGeometryParams.cmn.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/heightModelInfo.cmn.md b/docs/1.6/heightModelInfo.cmn.md
@@ -4,7 +4,7 @@ The I3S standard accommodates declaration of a vertical coordinate system that m
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md), [bld::layer](layer.bld.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md), [bld::layer](layer.bld.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/layer.bld.md b/docs/1.6/layer.bld.md
@@ -70,10 +70,6 @@ Building scene layer is not envisioned to represent many buildings (e.g. a city)
 - Added backed `modelName`.
 - Added statistics
 
-**TBD**
-- Update portal item JSON with mapping between FeatureServer layer ids and BIM SL id !?
-
-
 
 ### Related:
 

diff --git a/docs/1.6/lodSelection.cmn.md b/docs/1.6/lodSelection.cmn.md
@@ -4,7 +4,7 @@ A LodSelection object provides metric information determined during the cooking
 
 ### Related:
 
-[cmn::3DSNodeIndexDocument](3DSNodeIndexDocument.cmn.md)
+[cmn::3DNodeIndexDocument](3DNodeIndexDocument.cmn.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/mbs.cmn.md b/docs/1.6/mbs.cmn.md
@@ -4,7 +4,7 @@ minimum bounding sphere.
 
 ### Related:
 
-[cmn::nodeReference](nodeReference.cmn.md), [cmn::3DSNodeIndexDocument](3DSNodeIndexDocument.cmn.md)
+[cmn::nodeReference](nodeReference.cmn.md), [cmn::3DNodeIndexDocument](3DNodeIndexDocument.cmn.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/nodeReference.cmn.md b/docs/1.6/nodeReference.cmn.md
@@ -4,7 +4,7 @@ A NodeReference is a pointer to another node - the parent, a child or a neighbor
 
 ### Related:
 
-[cmn::3DSNodeIndexDocument](3DSNodeIndexDocument.cmn.md)
+[cmn::3DNodeIndexDocument](3DNodeIndexDocument.cmn.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/obb.cmn.md b/docs/1.6/obb.cmn.md
@@ -4,7 +4,7 @@ Oriented bounding box.
 
 ### Related:
 
-[cmn::nodeReference](nodeReference.cmn.md), [cmn::3DSNodeIndexDocument](3DSNodeIndexDocument.cmn.md)
+[cmn::3DNodeIndexDocument](3DNodeIndexDocument.cmn.md), [cmn::nodeReference](nodeReference.cmn.md)
 ### Properties
 
 | Property | Type | Description |
@@ -15,9 +15,9 @@ Oriented bounding box.
 
 *Note: properties in **bold** are required*
 
-### Examples
+### Examples 
 
-#### Example: Global scene (WSG84) oriented-bounding box
+#### Example: Global scene (WSG84) oriented-bounding box 
 
 ```json
  {
@@ -37,5 +37,6 @@ Oriented bounding box.
     -0.118217,
     0.897622
   ]
-}
+} 
 ```
+
diff --git a/docs/1.6/popupInfo.cmn.md b/docs/1.6/popupInfo.cmn.md
@@ -4,7 +4,7 @@ Defines the look and feel of popup windows when a user clicks or queries a featu
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/resource.cmn.md b/docs/1.6/resource.cmn.md
@@ -4,7 +4,7 @@ Resource objects are pointers to different types of resources related to a node,
 
 ### Related:
 
-[cmn::3DSNodeIndexDocument](3DSNodeIndexDocument.cmn.md)
+[cmn::3DNodeIndexDocument](3DNodeIndexDocument.cmn.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/serviceUpdateTimeStamp.cmn.md b/docs/1.6/serviceUpdateTimeStamp.cmn.md
@@ -4,7 +4,7 @@ Object to provide time stamp when the I3S service or the source of the service w
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/spatialReference.cmn.md b/docs/1.6/spatialReference.cmn.md
@@ -6,7 +6,7 @@ A spatial reference can optionally include a definition for a vertical coordinat
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::fullExtent](fullExtent.cmn.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md), [bld::layer](layer.bld.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::fullExtent](fullExtent.cmn.md), [bld::layer](layer.bld.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/statisticsInfo.cmn.md b/docs/1.6/statisticsInfo.cmn.md
@@ -4,7 +4,7 @@ Describes the statistics for the scene layer.
 
 ### Related:
 
-[psl::3DSceneLayer](3DSceneLayer.psl.md), [cmn::3DSceneLayer](3DSceneLayer.cmn.md)
+[cmn::3DSceneLayer](3DSceneLayer.cmn.md), [psl::3DSceneLayer](3DSceneLayer.psl.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/1.6/subLayerModelName.md b/docs/1.6/subLayerModelName.md
@@ -19,11 +19,13 @@ Model names allow clients to identify entities of a building without having to r
 |Floors	|Floors|
 |Furniture|	Office furniture,FurnitureSystems, Group of furniture|
 |GenericModel|	Miscellaneous items|
+|Mass|Element used on the process of visualizing, studying, and resolving building forms using massing.|
 |Parking|	Parking|
 |Planting	|Exterior planting|
 |PlumbingFixtures	|Toilets, Sinks, Vanities|
 |Ramps	|Ramps|
 |Roofs|	Roofs|
+|Rooms|Rooms|
 |Site|	Planter, Dumpster, Scaffolding|
 |SpecialtyEquipment|	Bicycle rack, Solar panels, Recycle bins|
 |Stairs|	Stairs|
@@ -34,9 +36,16 @@ Model names allow clients to identify entities of a building without having to r
 |StructuralColumns|	StructuralColumns|
 |StructuralFoundations|	StructuralFoundations|
 |StructuralFraming|	StructuralFraming|
-|ElectricalEquipment|	Lighting and appliance panel board, Ethernet switch|
+|ElectricalEquipment|Lighting and appliance panel board, Ethernet switch|
 |ElectricalFixtures	|Ground fault circuit interrupt, Emergency switch|
-|LightingFixtures|	Floor lamp, Ceiling light|
+|LightingFixtures|Floor lamp, Ceiling light|
+|CommDevices| Intercom Systems Components |
+|DataDevices|Ethernet and other network connections|
+|FireAlarmDevices|Smoke detectors, manual pull stations|
+|SecurityDevices|CCTV, motions sensors, Door locks|
+|TelephonDevices|Phone jacks|
+|NurseCallDevices|Nurse call devices|
+|LightingDevices|Daylight sensors, occupancy sensors, manual switches|
 |AirTerminals	|Exhaust grill, Return diffuser|
 |FlexDucts|	FlexDucts|
 |DuctAccessories|	Balancing damper, Fire damper, Filter cartridge|

diff --git a/docs/1.6/sublayer.bld.md b/docs/1.6/sublayer.bld.md
@@ -1,10 +1,10 @@
 # Building Scene Layer Sublayer
 
-A building scene layer is composed of an overview and the full model containing discipline and category layer. These layer types are represented as sublayers. A sublayer may contain other layers or sublayers (i.e `group`) to form a nested structure.
+A building scene layer is composed of an overview and the full model containing discipline and category layer. These layer types are represented as sublayers. A sublayer may contain other layers or sublayers (i.e `group`) to form a nested structure.  The order of the layers is inverted, meaning the first layer is on the bottom and the last layer is on the top.
 
 ### Related:
 
-[bld::sublayer](sublayer.bld.md), [bld::layer](layer.bld.md)
+[bld::layer](layer.bld.md), [bld::sublayer](sublayer.bld.md)
 ### Properties
 
 | Property | Type | Description |

diff --git a/docs/2.0/domain.cmn.md b/docs/2.0/domain.cmn.md
@@ -1,6 +1,6 @@
 # I3S Attribute (i.e. Field) domain
 
-See [a quick tour of attribute domains](http://desktop.arcgis.com/en/arcmap/latest/manage-data/geodatabases/an-overview-of-attribute-domains.htm) for more info on domains.
+Attribute domains are rules that describe the legal values of a field type, providing a method for enforcing data integrity. Attribute domains are used to constrain the values allowed in a particular attribute. Using domains helps ensure data integrity by limiting the choice of values for a particular field. Attribute domains can be shared across scene layers like 3D Object scene layers or Building Scene Layers.
 
 ### Related:
 

diff --git a/docs/2.0/domainCodedValue.cmn.md b/docs/2.0/domainCodedValue.cmn.md
@@ -9,8 +9,8 @@ See [a quick tour of attribute domains](http://desktop.arcgis.com/en/arcmap/late
 
 | Property | Type | Description |
 | --- | --- | --- |
-| **name** | string | Text representation of the domain value |
-| **code** | string, number | coded value (i.e. field value) |
+| **name** | string | Text representation of the domain value. |
+| **code** | string, number | Coded value (i.e. field value). |
 
 *Note: properties in **bold** are required*
 

diff --git a/docs/2.0/drawingInfo.pcsl.md b/docs/2.0/drawingInfo.pcsl.md
@@ -9,7 +9,7 @@ The drawingInfo object contains drawing information for a point cloud scene laye
 
 | Property | Type | Description |
 | --- | --- | --- |
-| **renderer** |  | An object defining the symbology for the layer. [See more](https://developers.arcgis.com/web-scene-specification/objects/pointCloudRenderers/) information on supported renderer types in ArcGIS clients. |
+| **renderer** |  | An object defining the symbology for the layer. [See more](https://developers.arcgis.com/web-scene-specification/objects/pointCloudRenderers/) information about supported renderer types in ArcGIS clients. |
 
 *Note: properties in **bold** are required*
 

diff --git a/docs/2.0/nodepage.pcsl.md b/docs/2.0/nodepage.pcsl.md
@@ -2,15 +2,23 @@
 
 
 
-Nodes represent the spatial index of the data as a bounding-volume hierarchy. To reduce the number of node-index requests required to traverse this index tree, they are organized in *pages* of [layer.index.nodesPerPage](index.md) nodes.  
+Nodes represent the spatial index of the data as a bounding-volume hierarchy. To reduce the number of node-index requests required to traverse this index tree, they are organized in *pages* of [layer.index.nodesPerPage](index.pcsl.md) nodes.  
 
-Children must be **contiguous**, in index range, so they may be located using  `firstChild`  and  `childrenCount`  fields.
+Children must be **contiguous**, in index range, so they may be located using  `firstChild`  and  `childrenCount` fields.
 
-**page number computation example:**
+**Page Number Computation Example:**
 
-Assuming [layer.store.index.nodesPerPage](index.md) = 64, then `node id = 78` will be in page `page_id = floor( 78 / 64) = 1` (i.e. second page)
+`page_id = floor( node_id / layer.store.index.nodesPerPage )`
 
+Let's say  `node id` = 78 and `layer.store.index.nodesPerPage` = 64.
 
+```
+page_id = floor (78 / 64)
+        = floor (1.22)
+        = 1
+```
+
+ The `page_id` of this node is `1`.  This is the second page since indexing starts at 0. 
 
 ### Related:
 

diff --git a/docs/2.0/obb.cmn.md b/docs/2.0/obb.cmn.md
@@ -1,6 +1,6 @@
-# I3S Point Cloud Scene Layer: Oriented Bounding Boxes
+# Oriented Bounding Box
 
-Oriented bounding boxes
+Oriented bounding box.
 
 ### Related:
 

diff --git a/docs/2.0/pcsl_README.md b/docs/2.0/pcsl_README.md
@@ -6,6 +6,8 @@ Point cloud scene layers are scalable, which allows for efficiency when working
 
 Point cloud scene layers also support caching attributes like RGB, Intensity, Flags, Class Code, Returns, User Data, Point Source ID, GPS Time, Scan Angle and Near Infrared.  This allows client applications to update the symbology as well as query point information.
 
+An example schema can be found below and a point cloud scene layer can be downloaded from [this story map](<http://3dcities.maps.arcgis.com/apps/MapSeries/index.html?appid=444de19a88764d58885ea8e211e96ae8>).
+
 *Example of point cloud rendering*
 
 ![Point Cloud Scene Layer](img/point-cloud-scene-layer.png)

diff --git a/docs/2.0/value.pcsl.md b/docs/2.0/value.pcsl.md
@@ -4,7 +4,7 @@ A scalar or vector value.
 
 ### Related:
 
-[pcsl::vertexAttributes](vertexAttributes.pcsl.md), [pcsl::attributeInfo](attributeInfo.pcsl.md)
+[pcsl::attributeInfo](attributeInfo.pcsl.md), [pcsl::vertexAttributes](vertexAttributes.pcsl.md)
 ### Properties
 
 | Property | Type | Description |