|
|
Currently, shapefiles used within InfoWorks ICM are referenced via local file paths. This approach introduces a significant limitation when models are shared between users. If another user opens the network without access to the same local directory structure, this results in missing data errors.
To enhance consistency and collaboration, it is recommended to enable the storage of shapefiles directly within the database, allowing them to be centrally managed and referenced. This would ensure that all users accessing the network have access to the same underlying data, regardless of their local setup.
This improvement would eliminate issues related to broken file path references and support more efficient collaboration across teams.
We have enabled this as part of our esri integration work, users can now bring shape files once they log in to their esri account. In the future, we are working on enabling the same for esri enterprise servers (#Safe Harbour applies*)
After that, we discuss with esri ways to enable our users to reference shape files even without an esri login (#Safe Harbour applies*)
We will not support the process of loading the shape files directly into the ICM database as this is already supported with the esri integration work.
* Safe Harbour means that you cannot make an investment or a procurement decision based on a future looking statement.
To add to this, it would be useful if users could export GIS layers from models via the 'Network > Export > to SHP files' path
fantastic - To enhance consistency and collaboration, it is recommended to enable the storage of shapefiles directly within the database, allowing them to be centrally managed and referenced.
Good idea