Skip to main content

Comments

7 comments

  • Bronson Jastrow
    This would be perfect! Projects have become valuable as more people use them and put real time into getting them just right.

    There's no documented way of restoring this data for a user who lost/deleted (or unintentinally modified) a project.
    0
  • Permanently deleted user
    It would bring the HTML5 viewer closer to parity with what the silverlight vewer already has.

    Saving as json and then being able to modify the json then reload the project without the person needing to login would be better.
    0
  • Permanently deleted user
    It seems like i can't vote here ...
    ..but its definitely a good idea.
    I can add that a way to "upgrade" saved documents with a new viewer id og site id (in batch) also would be of great value.
    0
  • Permanently deleted user
    YES!!
    0
  • Permanently deleted user
    My users have put serious effort into projects and some of that work is being exported to our GIS.
    I had to move sites and now I am struggling to migrate my projects as stored in ElasticSearch.

    Manager for ElasticSearch can edit the documents but I am reluctant to go that route becuase Latitude does not support it (depsite including it and using it).

    Latitude released a supported method in which one moves to another server. We need support for migrating between sites and backup/restore. When you copy a site the documents should be included as part of that process.
    0
  • Permanently deleted user
    As Mark Hoyland said, a capability lost in the migration from Silverlight to HTML5
    0
  • Max Molello
    Projects are almost uselss when I can't back them up, or recover corrupt ones due to LAyer Catalog ID changes. If I could export the Project JSON to edit the ID's and then reimport it to fix corrupted projects that would be amazing@
    0

Please sign in to leave a comment.