NoiseMap Forums

NoiseMap Software => Hints and Tips => Topic started by: roger on June 24, 2013, 09:57:40 AM

Title: Importing models from NoiseMap Enterprise
Post by: roger on June 24, 2013, 09:57:40 AM
NoiseMap five can import NoiseMap Enterprise models either from Masterfiles or from Archives.

You do need to be a little careful when importing from Masterfiles, becasue NoiseMap Enterprise does not enforce file type conventions whereas NoiseMap five does.

If you have stuck to the file name convention of using .MAS for the masterfile, .flo for the traffic flows, .seg for the road segments, etc, then NoiseMap five should import the model without any problems. However, if you have used your own file extensions that NoiseMap does not recognise (or, you have have mixed different types of object in one file) NoiseMap may complain.

It may refuse to import files that do not have a recognised extension. If this happens you will need to edit the file names and perhaps separate out the different types of object beforehand.  You can do this in NotePad or any simple text editor.

In NoiseMap Enterprise, you can give the full pathname of the files that comprise the model, but if you have changed to a different computer, these may no longer be correct.  So ensure that files are all located in the expected place, otherwise the whole model may not be imported.  Keep a close eye on the output log for any error messages.

If you import from an archive, then this should be seemless because all the objects will be correctly allocated in a single file and there will be no issue with naming conventions, etc.  Therefore, once way of avoiding naming problems is to  load the masterfile into Enterprise and save it as an archive which you then import into NoiseMap.

Note also that if you wish to transfer a model to another user who only has Enterprise, you can save any scenario in NoiseMap five as a NoiseMap Enterprise archive file (.rna, .sna or .tna) which you can load into Enterprise.  Of course, when you do this, you cannot save objects that don't exist in Enterprise, such as building outlines.