Spectrum Spatial (SSA/LIM)

Welcome to the Spectrum Spatial (SSA/LIM) community - start a discussion in the discussion tab or join in a conversation.

SSA Documentation  LIM Documentation  SSA Ideas  LIM Ideas

Discussions

Members

Resources

Events

 View Only
  • 1.  For consideration for future updates - specifying volatile

    Posted 06-25-2018 00:37

    Just pointing it it can be quite frustrating to have to open layers individually in Spatial Manager and change every single one to Volatile. An option to default to Volatile or even an additional checkbox during upload would save me a lot of time and potentially saving me a lot of trouble if a file isn't updating in Spectrum because I missed changing one (for example, when I discovered the property owner information wasn't updating - very problematic)



  • 2.  RE: For consideration for future updates - specifying volatile

    Posted 07-01-2018 19:23

    Hi Rebecca. There is a relatively quick and blunt way to change the volatility and a few a other settings. You'll need to either access the Repository via your WebDAV client or 'mount' the Repository in Windows. Table resource settings are written to simple short XML files which you can find in the Repository.

     

    If you open these in something like Notepad++ you can see the volatility tag;

    <TABFileDataSourceDefinition id="id1" volatile="true">

    You can switch between false/true values here as required. And if using Notepad++ or similar, you do a bulk search and replace without needing to open every file. This is a blunt method though and you may want to refine your file search to just those needing a volatile setting, setting every resource to volatile would likely see a performance drop.

    I agree with your sentiments on being able to specify volatility on upload as the main provided method through the web interface is clunky and doesn't allow an admin to see at a glance the settings for more than one file. From what I've seen on these forums UK to Australia local gov sector have vastly more resources in SSA than can be efficiently and effectively managed through the current level of admin tools provided.



  • 3.  RE: For consideration for future updates - specifying volatile

    Posted 07-01-2018 19:29

    Hi William

    Thanks for the great answer! I do have Notepad++, so I'll have a look into that. Most of our uploads will need to be volatile anyway as the majority are assets or property details.

    Hopefully future releases will help address some of these management issues



  • 4.  RE: For consideration for future updates - specifying volatile

    Posted 07-01-2018 23:50

    @Rebecca Marks? 

    Might want to hang off on making the change the way I listed above. The Admin Guide says not to do it that way (though I've done it before without incident).

    http://support.pb.com/help/spectrum/12.1/en/webhelp/Spatial/index.html#Spatial/source/Administration/config/configuring/configuring_volatile_flag.html

    The Admin Guide also states on the same page that:

    "Volatility is enabled (set to true) for named tables that are uploaded from MapInfo Professional using Map Uploader"

    Which seems to be a contradiction to what you and I have experienced.