mappedin-ops
32 packages
@mappedin/3d-assets
A collection of 3D assets optimized for use with @mappedin/mappedin-js.
@mappedin/blue-dot
An extension for [Mappedin JS](https://www.npmjs.com/package/@mappedin/mappedin-js) to track the device position on the map.
@mappedin/dynamic-focus
An extension for [Mappedin JS](https://www.npmjs.com/package/@mappedin/mappedin-js) that manages the visibility of floors and facades on camera change.
@mappedin/events
An extension for [Mappedin JS](https://www.npmjs.com/package/@mappedin/mappedin-js) that supports CMS events.
@mappedin/maplibre-overlay
An MapLibre Overlay for [Mappedin JS](https://www.npmjs.com/package/@mappedin/mappedin-js).
@mappedin/mappedin-js
- [Mappedin Developer Portal](https://developer.mappedin.com) - [Releases and Roadmap](https://developer.mappedin.com/docs/roadmap) - [Getting Started Guide](https://developer.mappedin.com/web-sdk/getting-started) - [Migration Guide](https://developer.map
@mappedin/marker-cluster
An extension for [Mappedin JS](https://www.npmjs.com/package/@mappedin/mappedin-js) that allows clustering markers together.
@mappedin/mvf
A starting point for interacting with MVF bundles. For Developers looking to get up and running with MVF, this is likely the best starting point.
@mappedin/mvf-address
The address extension for MVF. Allows specifying an address for the entire bundle, as well as addresses for individual floor stacks.
@mappedin/mvf-annotations
Annotations are very simple objects that point to where some item of interest exists at. For example, an MVF might have an Annotation where each Fire Extinguisher is.
@mappedin/mvf-cms
The CMS Extension adds a number of properties to the MVF, all under the base `cms` property This extra data is only available to certain CMS clients, and should not be used directly without discussing the implications with your Mappedin representative.
@mappedin/mvf-connections
Connections are things like elevators, escalators, doors, and ramps. They are a way to represent special links a person can use to traverse between specific geometries, on the same floor or between floors. This is separate from the [Nodes extension](../mo
@mappedin/mvf-core
The `mvf-core` package contains the fundamental "extensions" of the MVF format. They are technically optional, but practically every MVF will contain:
@mappedin/mvf-default-style
The default style extension for an MVF. A [DefaultStyle](../types/_mappedin_mvf-default-style.DefaultStyle.html) has things like color, height and opacity and the geometry it should be applied to. It is geared towards rendering the MVF in a 3D mapping eng
@mappedin/mvf-entrance-aesthetic
The Entrance Aesthetic extension describes aesthetic elements of doors, such as their swing direction and whether they are single or double doors.
@mappedin/mvf-facade
The Facade extension describes the [Geometry](../types/_mappedin_mvf-core.core_geometry_geometry.GeometrySchema.html) of a [FloorStack](../modules/_mappedin_mvf-floor-stacks.html) that live on [Floors](../types/_mappedin_mvf-core.core_floors_floors.Floors
@mappedin/mvf-floor-images
The floor images extension for an MVF allows for the addition of images to a floor, either anchored to a geometry or floating in space.
@mappedin/mvf-floor-stacks
The Floor Stacks extension describes groups, or stacks, of floors. The are typically used to represent buildings, but this is not a requirement.
@mappedin/mvf-kinds
The Kinds extension provides a high level categorization of geometry in an MVF. A geometry can have only ONE kind, from the [KIND](../variables/_mappedin_mvf-kinds.KIND.html) enum. Examples include `room`, `hallway`, `wall`, and `area`.
@mappedin/mvf-locations
The Locations extension adds a way to create Location/PoI metadata associated with one or more geometries. So where a specific Polygon might be `unit 123`, a Location might be attached to that Polygon, another an the floor above, and called "Macy's", with
@mappedin/mvf-navigation-flags
Navigation flags provide a mechanism to describe the properties of navigation paths within an MVF. They enable consumers of MVF data to make intelligent routing decisions based on the qualities of different paths. For example, an application might use fla
@mappedin/mvf-nodes
Nodes describe paths a person can walk around on in an MVF. There is a single file of nodes per floor, and those files will describe how to walk around on that floor. Going from one floor to another, or through things like travelators or doors, are done b
@mappedin/mvf-outdoors
The MVF Outdoors extension is used to describe which floors are outdoors in an MVF.
@mappedin/mvf-tileset
The Tileset extension provides a way to define the outdoor tileset to use when rendering an MVF. It is largely use by the SDK, and will not typically be needed by a developer.
@mappedin/mvf-traversability
The Traversability extension provides a way to define which geometries can be walked on/through, and which cannot. It is primarily used to influence the automatic node generation process.