Laurin Gottschall

Hi Helmut, 

this is Laurin from NavVis. Thanks for raising this question, please refer to the respective documentations of the Frameworks/Libraries in order to find out what abilities they offer. We do not have any examples that showcase the use of these libraries but I will make sure to bring this up internally to see if we might be able to improve the documentation here for the future. 

I hope this helps, let me know if you still have questions around this topic. 

Best regards, 
Laurin

Hi Helmut, 

this is Laurin from NavVis. Thank you for raising this question, unfortunately we currently do not support the option to reference icons through the Frontend/REST API. I will however bring this up in order to see if this could be added in the near future. 

I hope this helps, if you have any questions about this then please let me know. 

Best regards, 
Laurin

Hi Helmut, 

this is Laurin from NavVis. Thanks for your question in regard to the "scs_location" property. I checked that with one of our developers and the 'default' (identity) value for poi_orientation is [1.0, 0.0, 0.0, 0.0]. This is what you may apply here, other than that, the property is currently not used. We're currently discussing internally if this property should be removed from the REST interface if it does not serve any clear purpose. 

I hope this helps, please let me know if there's any questions around this. 

Best regards, 
Laurin

Hi Helmut, 

this is Laurin from NavVis. Based on your screenshots it seems as only the color of the toolbar was changed, my guess would be that the color value of your angular application is overwritten by the IVION viewer. Would you be able to check if that's the case and provide us with some more information on this matter? 

Thanks for your help. Best, 
Laurin

Hi Helmut, 

this is Laurin from NavVis. Let me get back to your question. In IVION/IndoorViewer you may have as many POIs as you need, there is no maximum which is limited on the site level. In regard to the performance we have mechanisms which ensure that only a fixed number of the POIs are shown which are around your location... this is why performance will still be fine regardless of how many POIs your site holds. 

I hope this answers your questions, let me know if there's anything else you would like to know about POI management in IVION.

Best regards, 
Laurin

Hi Richard, 

this is Laurin from NavVis. Thanks for raising this feature request... indeed this has been in our heads for quite a while but it's great to see that this is also coming as a request from our customers. I will pass this on to our developers and they will then take a decision as to when and how this might be implemented in the future. 

Thanks for your feedback though, highly appreciated. 
Best, Laurin

Hi Ben, 

this is Laurin from NavVis. The "NavVis IVION Add-In for Autodesk" has recently been updated to work with IVION. The new version of the new plugin however is no longer backwards compatible with IndoorViewer instances as stated in the About section: https://apps.autodesk.com/RVT/en/Detail/Index?id=5489279304951773635&appLang=en&os=Win64.

I do however fully understand that you'd like to support your customer using IndoorViewer with a working version of the Revit Add-In. I will speak to our developers and make sure to forward you the latest version that is still compatible with IndoorViewer instances. 

I hope this helps. Let me know if there's any other questions we can help you with. 

Best regards, 
Laurin
 

Hi Ben, 

I just recently had a chat with one of our developers to discuss your issue. He pointed out that your exported E57 does not seem to follow the E57 specification. If you open it in e.g. CloudCompare, you will see that the "images2D" path is not present. He was able to fix this by adding an empty entry there (actually just copy-pasted an empty one from another file as we also did not know how to create a new one). See attached screenshot how the meta data structure should look like. After correcting that we were able to import it into IVION. ;) 

Maybe try using a different App for scanning. We have used "Polycam" during internal testing which has proven to work flawlessly with IVION. 
Hope that helps! Thumbs pressed for your VLX delivery. 

Best regards
Laurin from NavVis

Hi Oliver, 
let me get back on your reply. 

Regarding the first point I understand that improving the maps visibility would already be an adequate improvement for you, is that right? Or do you maybe have a different idea on how we could actually improve the situation around the alignment of your buildings on the OSM Map? We would really value your feedback here as we obviously want this functionality to be as intuitive as possible. 

In regard to your second point I understand that "base point" is not the ideal wording here. I will discuss this feedback with our tech writers in order to make things more clear and improve the documentation.

In regard to the problem you're facing with POI import I saw that you have an open Support Case with us. As this seems to be very specific for your particular bundle our developers need to take a look at why this is happening in the first place. I hope we get this resolved sooner then later! 

Best regards,
Laurin from NavVis

Hi Ben, 

this is quite an interesting use case that you're describing and I see why you would like to get this working. In general the import of e57 files into IVION/IndoorViewer should work without any issue. Please make sure however that the range of intensity values has to be between -2048 to 2047. More on that also in our documentation: https://docs.navvis.com/indoorviewer/v10.0/en/html/features/pc_importer.html#importing-the-point-clouds

Were you able to successfully open the files using a third party tool? Maybe you can provide us with a link to the file so that our developers would be able to take a look at the structure and the data. 

Best regards, 
Laurin from NavVis