Thank you, Yang. Any plans to include such an (essential) information in the dataset / pointcloud info within the Viewer? It would make a lot of sense...
Thank you, Yang.
Having to look for that xxx.ini file would as well mean: I have to hunt for it on a local processing machine - and not within IV, correct?
Which in most cases wouldn't be easy to access (if at all).
... then you guys come around in a support case (as we have right now with a map-generation issue) and ask abou the resolution of the pointcloud within an instance that has been processed ages ago ...
You see the problem?
How / where can I access the properties of the pointcloud of a dataset / site?, specifically the density/resolution it has been processed for (5/10/20mm)?
Not happy with this implementation...
in IVION you can align your data with the buildings on the open street map in the Dataset Alignment mode. To see the underlying map please activate the checkbox "Show map".
On my color-calibrated display, the outline of the building on the OSM map is very hard to see. The background map is too dark, to grey-ish transparent.
About the documentation:
Enter the latitude, longitude and height of the base point.
Please define "base point".
My pain point, right now:
I have the issue in bringing over a multi-story building from IV to IVION - it being aligned in IVION as it has been before.
Reason being: tons of POIs. Having the bundle imported into IVION they are totally off, useless and not useable.
HOW do I get the location/coordinate match back, please?
@Bart: why don't you post a screenshot so everybody can view it?
Splendid, Bart. A nice integration, indeed :-)
Laurin, I used of course the standard way of accessing documentation, which is https://support.navvis.com/ (Resources/Documentation) to read up and copy/paste the how-to part in my initial message. Little did I know that there is now a different document-repository, nor that I have to use a different way of achieving the required re-indexing.
Kudos to you guys for making an already complicated process step even more complicated and frustrating! Ah I see, retro is hip these days and you wanted to have us do cryptic stuff like in the early days of M3 again... :-/
I wanted (well, needed to as in must) to generate the update Visual Index, after the Cloud instance was moved to IVION 10.
1) Downloaded and extracted bundle file (just one dataset, so simple)
2) Updated via sudo apt-get all the packages
3) Ran Visual Index generator, well wanted to, accoding to the manual which states:
To set up NavVis Positioning for your site, you must generate a visual index. In case you grouped your datasets in multiple bundles, you must generate a separate visual index for each dataset bundle.
On your data processing machine, run
navvis-visual-index-generatoron the command line:
4) Where in the world is my bundle xml file, that the generator syntax needs?, it is nowhere to be found in the extracted bundle folder?
5) Stalled... :-/
Yet another Feature Request: Having to download (super-large) bundle files just to be able to generate a new Visual Index for IVION is cumbersome (that would be a euphemism). After download, you need to spend time and look up how it works again, to use the command line command, and upload the finished result back into the instance. For the system and you guys, it is basically running some scripts and AWS tools - for us users it is time-consuming and annoying, to say the least.Why is it not possible to have it the Visual Index generated from within IVION - after all, all the data is there already?
Yep, you nailed it. User group based NavGraphs. You should be able to duplicate the default NavGraph, have it in a different color, be able to switch on /off visibility of NavGraph layers (for when editing them).
Use case example, office environment:
- Routing for Visitors (only conference rooms through (semi-)public area; even if that means less efficient (longer) way)
- Routing for Wheel Chair users (NO stairs, only doors than can be opened while sitting in a chair)
- Routing for tenant companies x y z in same building (again, maybe not the fastest direct route)
Use case example, factory:
- Routing for safety gear wearing and trained personal (to protect man an/or machine (EM))
- Routing for white collar workers within factory (bypassing potential safety hazard zones)
- Routing for gear hauling persons (not being able to fit through standard doors, over steps, etc.)
Use case example, museum:
- Routing for Security Guards (which ideally can be randomized)
- Routing for Visitors interested in exhibition topics a, b, c