Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

license plate and rule management in Nx

Answered
Permanently deleted user

Hi teams,
Our customer is using Nx to manage the LPR camera white/black list, as it's a hotel, they will add/delete license plate everyday. And coz they want to show specific car owner name on the camera, so we set one rule for one license plate, then rule could trigger camera isapi to show specific osd on camera. But currerntly we have some issues, just want to know any alternative method or plan in the future? 

1. We can't change rule name, so it makes rule management is a pain for end-user, but to be honest, most of VMS manufature will be able to do this. 

2. Is there any way to import multiple rules or copy rules? just easy for using, as we have lots of solutions to deep integrate with hik cameras, so will use HTTP request action freqently, it will be great if we have a better rule management tool. 

3. Any chance Nx could seperate the bookmark with footage, as license plate meta data bond to bookmark, so license plates info only will record for one month, any chance we could extend these data longer time? not depends on footage recording time. We have lots of LPR solution customer want to keep the license plate data longer.  

1

Comments

6 comments

Date Votes
  • Norman
    • Network Optix team

    Hi @...,

    We don't offer such an option in our rules engine, but I'll move this to our New Feature Ideas section, so our product team is aware of this request and could take this into consideration for future releases.

    0
  • Tagir Gadelshin
    • Network Optix team

    Hi, @...

    1. We can't change rule name, so it makes rule management is a pain for end-user, but to be honest, most of VMS manufature will be able to do this. 

    This is planned as a part of big event rules revamp. We will release it step by step, but finally, there will be descriptions for rules, search by descriptions and we hope it will be easier to navigate the Event Rules.

    2. Is there any way to import multiple rules or copy rules?

    There is no UI for that, but you can easily do so via API, using

    GET /ec2/getEventRules

    and

    POST /ec2/saveEventRule

    API requests: https://support.networkoptix.com/hc/en-us/articles/115016055728-API-tip-How-to-create-or-modify-Event-Rule
    Some script should do those requests and, unfortunately, it won't be just import-export, I feel like JSON files have to be analyzed in the script. But it's definitely doable

    Any chance Nx could seperate the bookmark with footage, as license plate meta data bond to bookmark, so license plates info only will record for one month

    We discussed it as "evidence lock", when the footage is also saved. See related thread: https://support.networkoptix.com/hc/en-us/community/posts/360012952574-Protect-bookmarked-events-from-deletion
    But as I understand, you don't need to save the footage, but only information about LP, bookmark info only, right? Most likely we will try implementing "footage lock" based on the bookmark, would it be a suitable solution for you?
    More disk space will be needed, though

    0
  • Permanently deleted user

    Hi Tagir and Norman, 

    Thanks for all of your prompt reply and suggestions, 

    1. Is there a estimated time for this new rule engine? 

    2. That looks great, I think I could write some scripts to make it easier, but I'm not sure what event uuid should I use? is there any way to produce the uuid in advnace?

    3.  Unfortunately I need to save footage, but footage just need to save for 1 month, lp and bookmark these kind of metadata need to save for half year, if I could set different recording schedule, it will be more handy and better solution deigsn.

    And thanks for the thread you share to me, they are exatly same thing I want, but haven't seen any update there, do you have a estimated time in your roadmap? 

    0
  • Tagir Gadelshin
    • Network Optix team

    @...
    1,3. No estimates, I'm sorry. Event Rules engine is a core feature and it's big. We are actively developing new engine and we hope it will be released in the near future. After that we will start changing UI.
    Bookmarks protection is also smth we want to implement, but it hasn’t started yet. 

     

    2. Regarding adding new event rule.

    To add new rules user needs to send JSON object specifying:

    • new generated "id" attribute, it will create "event rule" resource. Nx Server uses special unique identifiers for "id" fields. New valid ones might be generated here.
    • all the rest attributes including nested JSON objects should be specified according to analogous ones from the server reply to /ec2/getEventRules request.

    So basically for uuid there are plenty of services out there or you can utilize some open-source code that generates uuid.

    0
  • Permanently deleted user

    Hi Tagir,

    Thanks for your clarification! I think might be easier I write a script to manage rules lol. 

    And I have a question regard uuid, so if I use the link you provide me to create uuid, then in the future, if I use normal way to create rule in Nx, it won 't have any conflict of uuid in the Nx right? 

    0
  • Tagir Gadelshin
    • Network Optix team
    Edited

    @...
    collision of independently generated uuid-s is almost impossible, from Wikipedia:

    When generated according to the standard methods, UUIDs are, for practical purposes, unique. Their uniqueness does not depend on a central registration authority or coordination between the parties generating them, unlike most other numbering schemes. While the probability that a UUID will be duplicated is not zero, it is close enough to zero to be negligible.

    So you don't need to check if uuid exists and you won't have collision of uuid or any conflicts even when using external service.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post