Patent Application
20200143591
The present invention relates generally to the creation and use of digital 3D-modelled locations utilizing specialized, mapped location data and a related software platform to interface with such data.
While prior art approaches for creating digital location models allow for interaction with such models to an extent including simulated walkthroughs of interior spaces, the present invention integrates additional information into mapped location data to provide further practical utility. It is one object of the present invention to allow couple portions or sections of mapped location models, both exterior and interior, with real world positioning information. It is a further object that items captured in the mapped location models may have additional information about such items coupled to the models. Yet another object of the present invention is to further couple location data is that updated in substantially real-time to the mapped location models. Users may then access the mapped location models and any related information via a web-based, or other software, platform.
Through this coupling of data, a dynamic system is created through which users may remotely monitor on a computing device conditions of any real world site that has been mapped and modelled as contemplated by the present invention. Specifically, and improving over the capabilities of the prior art, the integration of real-time location data (by coupling with GPS devices) allows for the remote monitoring and guidance of emergency, rescue, or other personnel as they traverse interior physical spaces captured by mapped location models.
This description, along with the accompanying figures, presents non-limiting examples of embodiments of the present invention. Although specific hardware and software solutions or techniques may be described herein, a person of ordinary skill in the art would recognize that any number of equivalents to such solutions or techniques could be otherwise used to realize various embodiments of the present invention.
Certain embodiments of the present invention comprise a set of mapped location data. This set of mapped location data may itself include at least one digital location model or image, data representing a static geographic position, and secondary model information representing additional details about positions within or items or objects related to a location. These embodiments may further comprise substantially real-time position data used to present the location of a positioning device, which serves as a source of said substantially real-time positioning data, on said digital location model or image. Some embodiments will also comprise a mapped location interface platform configured to allow users to interact with, and in some cases modify, said set of mapped location data.
In other embodiments, the set of mapped location data may comprise a plurality of digital location models or images that, as combined, create a digitally traversable 3D-space representing an area within a location.
One non-limiting embodiment of the present invention, describing properties of said set of mapped location data, and the manner in which elements of such data are coupled with each other or with various other components of the invention, is set forth below from the perspective of implementing the mapped location interface platform.
Mapped Location Interface Platform. The primary function of the platform (or application) is to provide users with a web-based, easy-to-use tool that provides a 3D model or image of their facility and through which users may interface with equipment within said facility. Utilizing cutting-edge imaging techniques, all assets can be readily documented in digital storage and configured for user access.
The application may be built using the ASP.NET MVC framework. This is a framework known in the art that specializes in building web applications using the model-view-controller design pattern. Basic implementation of this embodiment of the present invention can be achieved through the use of three separate projects that follow the MVC pattern—the Web Application, Model, and Database projects. A fourth project corresponding to a Windows Service, however, is additionally contemplated to provide enhanced functionality achieved through its collection of GPS data from integrated GPS devices.
Web Application (View and Controllers) Project. During the creation of the Web Application project, the integrated development environment (“IDE”) will set up several default folders and files. Folders for Views, Controllers, Scripts, Styles, and App Start will be created along with a Web.Config file. Default files for controllers, views, scripts, and styles will be automatically added to the newly created folders. Before continuing, configure the database location, name, and specify the authentication information. These settings are added to the Web.Config file and will be used by ASP.NET Identity and the Database Project.
Implementation of this embodiment also contemplates integration of the ASP.NET Identity system. This system provides the back-bone to the relevant authentication services. When setting up ASP.NET Identity, the option to use “Individual Accounts” should be selected. This option provides that each user will have their own username and password. A password policy should then be established and two separate roles set up. The first of these roles is the Administrator. Users with this role will have permissions to all pages and features. The other role that needs to be created is the Location User. Users with this role will only have access to view their locations and the associated mapped location data that has been assigned to them. The ASP.NET Identity installation will also bring in several new views, controllers, and will, based on the initial configuration, provide the membership entities class. The Identity installation will create the application's database with the necessary tables that Identity needs to manage user accounts and roles. The new database that ASP.NET Identity creates will also be the primary database for the platform.
The MVC web application utilizes shared views that will act as a master page. These shared views will store the Style Sheet Locations, Script File Locations, a header, menu, and footer. When content views are created, a default shared view must be specified so that all pages can have the same header, menu, footer, etc. without having to re-code those on every page.
Views and controllers must also be created to manage Customers, Locations, mapped location data (including 3D Image Mini-Map Settings and a 3D Image Mini-Map), GPS configurations, GPS Devices, Personnel Management, and User Configurations. User Configurations include views that will allow an Administrator to set up new users, assign Location Users access to their specific Locations, reset passwords, and assign GPS devices to Personnel Users.
Each view will need to include:
The Location User Views/Controllers must also be created and will composed of two views:
Model Project. All of the Models and ViewModel objects are declared in this project. Each Model is a cs file containing the various properties that will be used by that object. A reference in the Web Application Project to the Model Project must be set up so that they can share components. Each Model object will also represent a database table that will be created in the Database Project. After a schema mock-up is created, creation of the actual cs files should begin. Data Annotations assembly should be used to specify required properties, foreign keys, and display names. The classes that need to be created are “Customers”, “Personnel User” (with a foreign key to “Customers”), GPS Device (with a foreign key to “Customers”), “Personnel User GPS Device” (with foreign keys to “Personnel Users” and “GPS Devices”), “Locations” (with a foreign key to “Customers”), “Location 3D Images” (with a foreign key to “Locations”), and then a table to store which “Locations” a “Location User” has been assigned. Once the Model Project is built, you are ready to create the Database Project and add the tables to the database that ASP.NET Identity created during the Web Project setup.
Database Project. Creation of the Database Project contemplates use of the Entity Framework. The Entity Framework is used to manage the communication between the application and database. It serves as a map between the users submitting forms and how the data ends up in the database. An entity context is created in which all the Model objects in the Model Project are specified. When a migration script is executed, the tables in the database that mirror the Model objects are created.
Integrating the Platform with the Mapped Location Data. It is envisioned that a specialized camera designed to capture digital images to generate a 3D-modelled space (such as those developed by Matterport) will be used to provide 3D representations of user specified locations. As understood by persons of ordinary skill in the art, manufacturers of such cameras will provide a software development kit (“SDK”) to facilitate the use of any images or other data produced by their cameras. Interactions with a manufacturer's application programming interface (“API”) are primarily on the client-side using JavaScript. Specific instructions to communicate with a manufacturer's API is readily available in documentation provided by such manufacturers. Furthermore, it is understood that the code necessary to frame in a 3D representation of a space generated by a digital image, or images, after it has been captured by a camera and uploaded to a manufacturer's data hosting service can similarly be found in such documentation. This embodiment provides the platform that links customer accounts to the mapped location data, especially the 3D representations, of their respective facilities (or locations). Through this platform, a customer may be set up and linked to 3D representations of their selected locations which will be grabbed from the database by the location's API token thereby allowing for a page displaying such 3D representations to be dynamically built upon log-in.
Additional Frameworks. This embodiment further contemplates the use of additional user interface (“UI”) helpers and script libraries including:
Database Server. A relational database is used to store the platforms data and documents. A database engine, running on “server level” hardware, should be used to store the data and documents. The tables in the database will mirror the model objects specified in the Web Application Project (for Identity) and the Model Project.
Customer Management Page, Role: Administrator. The platform will include a customer management page is where the primary account for each customer is tracked.
This page includes a “Panel Bar” that will open and collapse upon clicking. When opened it will display the Customer Insert Form. When collapsed it will hide the Customer Insert Form and display the title of “Add Customer”. Under the “Panel Bar” is a grid that lists all customers in a table. It is a paging-enabled table with sortable column headers and data rows. Each row represents a customer. In addition to the customer data in each row there are also three buttons:
A sample customer form may include the following fields:
The Customer Management page is a Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated, has permissions, and sets a ViewBag with the user's ID. The method in the controller uses C #. The view uses HTML, C #, CSS, JavaScript, jQuery, and Angular to build out the panel bar, insert form, and grid. The panel bar is a Kendo Panel Bar built with an HtmlHelper block. It contains attributes for Name, Animation, and Items. The insert form is added to the “Items” section of the panel bar. The content inside the panel bar's “Item” section is using standard html tags with extra Angular properties on each of the input items that will be active in the scope of the Angular controller. Below the panel bar is the grid that uses a standard HTML div tag. The grid will be activated in the script section of the page. The script section of this page has several roles and executes asynchronously. When the page loads it will activate the Kendo UI Controllers, define data sources for the dropdowns, and create events that are stored inside the HTML DOM.
Activating Kendo UI Controllers activates input items such as textboxes, dropdowns, html editors, and grids. When the grid is activated, a data source is set to a method inside the controller that returns the list of customers as a JSON object. Properties for the grid are also defined. Examples of properties are width, pageable, scrollable, editable, etc.
This page is configured to respond to the following events:
Location Page, Role: Administrator. The Location page is where each Customer's Location(s) are tracked.
This page includes a “Panel Bar” that will open and collapse upon clicking. When opened it will display the Location Insert Form. When collapsed it will hide the Location Insert Form and has the title of “Add Location”. Under the “Panel Bar” is a grid listing all the Customer's Locations. It is a paging-enabled table with sortable column headers and data rows. Each row is a Location. In addition to the location data in each row there are also three buttons.
A sample location form may include the following fields:
The Location page is a Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated, has permissions, and sets two ViewBags with the User's ID and Customer's ID. The method in the controller uses C #. The view uses HTML, C #, CSS, JavaScript, jQuery, and Angular to build out the panel bar, insert form, and grid. The panel bar is a Kendo Panel Bar built with an HtmlHelper block. It contains attributes for Name, Animation, and Items. The insert form is added to the “Items” section of the panel bar. The content inside the panel bar's “Item” section is using standard html tags with extra Angular properties on each of the input items that will be active in the scope of the Angular controller. Below the panel bar is the grid that uses a standard HTML div tag. The grid will be activated in the script section of the page. The script section of this page has several roles and executes asynchronously. When the page loads it will activate the Kendo UI Controllers, define data sources for the dropdowns, and create events that are stored inside the HTML DOM.
Activating Kendo UI Controllers activates input items such as textboxes, dropdowns, html editors, and grids. When the grid is activated, a data source is set to a method inside the controller that returns the list of locations as a JSON object. Properties for the grid are also defined. Examples of properties are width, pageable, scrollable, editable, etc.
This page is configured to respond to the following events:
Location Image Map Page, Role: Administrator. The Location Image Map page is where the Customer's location is linked with the location image maps (effectively acting as 3D location models or images) of the physical building.
This page includes a “Panel Bar” that will open and collapse upon clicking. When opened it will display the LIM Insert Form. When collapsed it will hide the LIM Insert Form and has the title of “Add Location Image Map”. Under the “Panel Bar” is a grid listing all our customers in a table. It is a paging-enabled table with sortable column headers and data rows. Each row is an LIM with a unique ID provided by the camera manufacturer. In addition to the LIM data in each row there are also three buttons.
A sample LIM form may include the following fields:
The LIM page is a Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated, has permissions, and sets a ViewBag with the Location's ID. The method in the controller uses C #. The view uses HTML, C #, CSS, JavaScript, jQuery, and Angular to build out the panel bar, insert form, and grid. The panel bar is a Kendo Panel Bar built with an HtmlHelper block. It contains attributes for Name, Animation, and Items. The insert form is added to the “Items” section of the panel bar. The content inside the panel bar's “Item” section is using standard html tags with extra Angular properties on each of the input items that will be active in the scope of the Angular controller. Below the panel bar is the grid that uses a standard HTML div tag. The grid will be activated in the script section of the page. The script section of this page has several roles and executes asynchronously. When the page loads it will activate the Kendo UI Controllers and create events that are stored inside the HTML DOM.
Activating Kendo UI Controllers activates input items such as textboxes, html editors, and grids. When the grid is activated, a data source is set to a method inside the controller that returns the list of LIMs as a JSON object. While creating the LIM object it checks to see if the Map has been set up properly. This check adds a green “Yes” or red “No” to the “Map Updated” property. Properties for the grid are also defined. Examples of properties are width, pageable, scrollable, editable, etc.
This page is configured to respond to the following events:
That will post the object to the destroy method in the controller and mark that LIM as deleted. It will not actually remove any records from the database.
Map Settings Page, Role: Administrator. The Map settings page allows an administrator to align the camera location dots, provided by the camera manufacturer, with the uploaded blueprint/mini-map corresponding to the LIM.
This page uses the Location Image Map ID to get its specific API Token from the database. It then runs a script to add the API Token to the iFrame to load the 3D Image Map (comprising an image captured by a specialized camera) from the manufacturer Service. Inside of the Location Image Map (LIM), in the top-right corner, is the uploaded blueprint/mini-map displaying location dots corresponding to camera placement when capturing the image element of the LIM and a dot representing the position of the current user's simulated field-of-vision cone. To the left of the image frame are four numeric textboxes that allow the administrator to change the location of the top-left corner and the height/width of the element housing the camera location spots. Once the values are correctly configured and the mini-map lines up with the 3D Image map, the “Update Values” button should be clicked.
A sample Map Settings form may include the following fields:
The Map Settings page is a Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated, has permissions, and sets a few ViewBags with the LIM Information, Image Token, and File Path to the Blueprint/Mini-Map. The method in the controller uses C #. The view uses HTML, C #, CSS, JavaScript, jQuery, and Angular to create the map settings form, frame the LIM from the camera manufacturer's service, and build the mini-map that is integrated with the camera image spots. When the page loads it will activate the Kendo UI Controllers and populate the textboxes with either default values or it will make an ajax call to the server and request those values. When it retrieves the values from the application database, it will populate the textbox values and set the scope property for each. Next it makes a connection to the camera manufacture's API to retrieve the 3D Image Object. With that object we have the camera location dots, the current location of the user, and asset tags. With the location of the user and the dimensions of the 3D image field-of-view I can calculate the field-of-vision cone of the current user. The cone is built with a simple div and CSS. When the user looks around it changes the properties of the CSS to match with what the user is seeing in the 3D Image Map.
Activating Kendo UI Controllers activates textboxes and buttons.
This page is configured to respond to the following events:
Register User Page, Role: Administrator. This page will allow an administrator to set up a new user.
This page includes a standard HTML form and one button to submit the data to the server.
A sample register user form may include the following fields:
The Register User page is Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated and populates a ViewBag with a list of User Roles. This ViewBag will be used to populate the “Role” dropdown. The method in the controller uses C #. The view uses HTML, C #, CSS, JavaScript, jQuery, and Angular to build out the insert form. The registration form is wrapped in a Razor BeginForm “Using” block and is tied to the RegisterViewModel assigned to the view. All input items have HTMLHelpers defining what property of the ViewModel each input item belongs to. Once submitted it will create the object using the HTMLHelper names and submit that data to the view specified in the BeginForm “Using” block. When the data gets to the Registration POST method it will create the user object, execute the Create User method with its password specified. If it successfully adds the user, it will then assign the role to that user and return the admin back to the Register page displaying a result message.
Activating Kendo UI Controllers activates input items such as textboxes, dropdowns.
This page is configured to respond to the following events:
The “Role” dropdown in the insert form is set in the AccountsContoller, with a ViewBag containing a list of Roles.
User Lists Page, Role: Administrator. This page has two list of users that are grouped by Role. A user is either an Administrator or a Location User.
This page has two grids listing users who have access to the application. If the user is in the “Admin” table then they have full permissions to the entire application and all available features. If the user is a “Location User”, then they only have access to locations that have been assigned to them. Each location will have a Location Image Map (or Maps) and allow that user to digitally traverse each location and view asset tags.
The only form on this page will open when an Administrator clicks the “Reset Password” button for a “Location User”. Each user will have their own “Reset Password” button tied to their UserId. This form will allow for the entry of a password and include a separate field to confirm the new password.
The User Lists page is a Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated and has permissions to view the page. The method in the controller uses C #. The view uses HTML, C #, JavaScript, and jQuery to build out the two grids. The grids are built, defined, and populated using Kendo HTMLHelpers for Razor. Each grid is tied directly to a ViewModel for each specific role. A DASAdminViewModel populates the top grid and the LocationUserViewModel populates the lower grid. The columns and data sources are defined inside the razor with no JavaScript needed. Each grid has its own separate data source. Inside the Location User grid is a password reset button for each user row. When clicked it will determine what row it was fired from and get the UserId of that user. It then calls a JavaScript event to activate the Kendo Popup and allow the user to type in a new password. Once the password is verified and confirmed then it will call a method in the controller to reset that user's password. The Kendo Popup Window closes upon submission.
Activating Kendo UI Controllers activates two grids. When the grids are activated, a data source is set to a method inside the controller that returns the list of users (either Administrator or Location User) as a JSON object. Properties for the grids are also defined. Examples of properties are width, pageable, scrollable, editable, etc.
This page is configured to respond to the following events:
Reset Password Page, Role: Administrator. This page allows the currently logged in user to reset their own password
The user will type in their current password in the top box, the new password in the middle box, and confirm the new password in the bottom box. There is a button called “Change Password” that will send the data to the controller and update the database. The new password must be a minimum of 6 Characters, at least one number or special character, at least one lowercase letter, and at least one uppercase letter.
A sample reset password form may include the following fields:
The Reset Password page is a Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated. The method in the controller uses C #. The view uses HTML, C #, and JavaScript. The Change Password form is wrapped in a Razor BeginForm “Using” block and is tied to the ChangePasswordViewModel that is assigned to the view. All input items have HTMLHelpers defining what property of the ViewModel each input item belongs to. Once submitted it will create the object using the HTMLHelper names and submit that data to the action specified in the BeginForm “Using” block. When the data gets to the ChangePassword ActionResult it will reset the user's password and redirect them back to the “Change Password” page displaying the Result Message.
This page is configured to respond to the following events:
Assign Users Page, Role: Administrator. This page will list out all active Location Users and allow an administrator to assign users to a specific location.
This page has a grid listing “Location Users”. For each user row in the grid, there is a button called “Assign Location”. When clicked it will redirect you to a page listing out all locations that can be assigned to that user. Each location will have a Location Image Map (or Maps) and allow that user to digitally traverse each location and view asset tags.
The grid may include the following columns:
The Assign Users page is a Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated and has permissions to view the page. The method in the controller uses C #. The view uses HTML, C #, JavaScript, and jQuery to build out the User Location grids and define the event fired by clicking the button. The grid is built, defined, and populated using Kendo HTMLHelpers for Razor. The grid is tied directly to a LocationUserViewModel and sets its data source to an ActionResult in the customer controller. That ActionResult returns a list of ViewModel objects. Inside the “Location User” grid is an “Assign Location” button for each user row. When clicked it will determine what row it was fired from and get the UserId of that user. It then redirects that user to a new page where they can assign the locations.
This page is configured for a JavaScript event that is fired when the user clicks the “Assign Location” button. It grabs the current row in the grid and finds that User's ID. It then builds the URL and redirects that user to the new page.
Assign User Location Page, Role: Administrator. This page allows an administrator to assign specific locations to a Location User. When a Location User logs into the system they will only have access to the locations that have been assign to them from this page.
This page includes a grid that contains a list of locations. In each row of the grid is a checkbox that allows the administrator to select which facilities to assign to the Location User. When the locations are selected there is a button labeled “Assign User” that will post the data to the controller and update the database.
The grid may include the following columns:
The Assign User Location page is a Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated, has permissions, and sets a ViewBag with the UserId of the user passed to this page from the previous page. The method in the controller uses C #. The view uses HTML, C #, CSS, JavaScript, and jQuery to build out the grid and define the “Assign User” button event. The grid that uses a standard HTML div tag and will be activated in the script section of the page. The script section of this page has several roles and executes asynchronously. When the page loads it will activate the Kendo UI Controllers, set up the Location grid, and create events that are stored inside the HTML DOM.
Activating Kendo UI Controllers activates the “Assign User” Button and Locations grid. When the grid is activated, a data source is set to a method inside the controller that returns the list of Location Users as a JSON object. Properties for the grid are also defined. Examples of properties are width, pageable, scrollable, editable, etc.
This page is configured to respond to the following events:
Location User Portal Page, Role: Location User. When a user with the role of “Location User’ logs into the platform they are directed to the “Location User Portal”.
This page features a dropdown that will allow the user to switch between the locations that they have been assigned. Within the Location Image Map (LIM) they can digitally traverse their site, watch their progress on the mini-map, and click to view assets that have been tagged within the LIM. Depending on the size of the location, the location can be divided into multiple LIMs, each having a specific image captured from different camera positions, that are aggregated or gridded together to fully depict the location. To the right of the current LIM image are the thumbnails to the other LIM images corresponding to the selected location. The user can click the thumbnails and load the corresponding LIM.
A sample location image map form may include the following properties:
The Location Image Map page is a Razor page (view) built inside of a shared view so that it can use the application's master header, menu, and footer. This page also has a corresponding method inside its controller. The method in the controller checks to see if the user is authenticated and has permissions. The method in the controller uses C #. The view uses HTML, C #, CSS, JavaScript, jQuery, and Angular to populate the Locations dropdown, frame the LIM from the camera manufacturer's service, and build the mini-map that is integrated with the camera image spots. When the page loads it will activate the Kendo UI Controllers and populate the dropdown with a list of locations that the logged in user has permission to view. Next it makes a connection to the camera manufacture's API to retrieve the 3D Image Object corresponding to an LIM. With that object we have, in addition to the viewable image(s) of the location's area captured by the camera that comprise an effective 3D-modelled space, the camera location dots, the current location of the user, and asset tags. With the location of the user and the dimensions of the 3D image “field-of-view”, the field-of-vision cone of the current user on the mini-map can be calculated. The cone is built with a simple div and CSS. When the user looks around, it recalculates the field-of-vision and changes the properties of the CSS to match with what the user is seeing in the 3D Image Map. To the right of the LIM image being displayed, if needed, images of additional LIMs corresponding to the current location may be displayed via a thumbnail grid. The thumbnails have been uploaded through the Admin Portal.
Activating Kendo UI Controllers activates the location dropdown.
This page is configured to respond to the following events:
Relationships between the mapped location data, platform, and external devices are described below in terms of views or pages which provide additional platform functionality that will assist in potential emergency situations at any location stored in the platform's database.
GPS Tracking Integration. A view is created that will allow an Administrator to set GPS coordinates around the perimeter of a mini-map that has been previously uploaded. Once the GPS coordinates are set, the application will calculate the latitude and longitude of the facility's or location's interior. jQuery “onClick” events are used to create the GPS coordinate and mark the pixel location on the image that the coordinate was set on. If the image is sized down on the 3D Image Settings page, then the application will re-calculate the GPS point. The calculation will be based on percentage. If the image is shrunk by 12% then the new GPS point will also be shrunk by 12%. The pixel is a whole number so if the re-calculated value is a decimal then round up or down using standard math rules.
Assign Devices to Personnel Users. A view is created to manage Personnel Users. These users will not have access to the system but will be assigned GPS devices. This view will capture information such as name, employee ID, Title, etc. and save them to the database. Once the Personnel User is created, they can be linked them to a GPS Device. The GPS device will have a QR code stamped on the back of the device that will allow a Location User to select a Personnel User from a list and scan the device when prompted. The Location User will also be able to make a Personnel User and GPS device in-active. If a Personnel User is made inactive, it will remove the device from that user and make it available in inventory. There will also be a view to scan in devices that are not assigned to a user. This will help the customer keep track of how many devices are assigned vs. unassigned in inventory.
GPS Information on location's map. A Windows Service that utilizes thread pools is built. Creating multiple threads will allow the server to communicate with many GPS Devices at once. A GPS Device manufacturer will have an API or SDK that can be used to make these requests. Each request will return the GPS Device's latitude and longitude. Then it will update that device's location in the application database along with a time stamp of that reading. The server will be constantly communicating with the API—even if nobody is logged into the application. On the client side there will be an ajax call to the application database requesting a list of GPS devices for the specific location the user is accessing. It will then loop through these devices and put a dot on the map for the calculated latitude and longitude pixel location. This call will run continuously while the user is on that view. The Location User can toggle the GPS dots “On” and “Off”.
GPS Personnel Tracking View. A view is created for the Location Image “floor plan mode”. The floor plan mode will be a top-down view of the facility. This will feature a larger version of the mini-map and will allow the user to click and span around in the image if the facility's floor plan is too large to fit on the screen. Scripts will be run on this page and configured put the GPS dots on this screen and the Location User can mouse-over the dots to see who that person is and view the date and time of the last reading.
The present application claims priority to U.S. Provisional Application No. 62/754,620, titled “SYSTEM AND METHOD FOR CREATING INTERACTIVE GPS-INTEGRATED, 3D-MODELLED SPACES” and filed on Nov. 2, 2018.
| Number | Date | Country | |
|---|---|---|---|
| 62754620 | Nov 2018 | US |
