Confirm

Expand all | Collapse all

NSG Import specification

  • 1.  NSG Import specification

    Posted 03-24-2020 07:42
    Hi all,

    I was wondering if anyone can advise what the NSG import specification is - i.e. which  Confirm fields are updated with which part of the LG and ASD data?

    The reason for asking is that we have some information that isn't being updated - Categories and Classification - and I am wondering whether this information is on the NSG. Having looked at the NSG spec, i can't find a field from GeoPlace that corresponds to the information we currently hold in these fields.

    So one of two things is happening:
    1) that type of information needs to be collated and uploaded separately as it isn't on the NSG; or,
    2) The info is on the NSG files but the contents of the tables in question are so out of date that it isn't updating the information and keeps putting NCA instead.

    Thanks!

    Ana












    ------------------------------
    Ana Resende
    Gloucestershire County Council
    GLOUCESTER
    ------------------------------


  • 2.  RE: NSG Import specification

    Posted 03-24-2020 11:08
    Ok, so after some more digging, I can see that different tables are being updated - such as ASD type 61 updates the Site_interest table. but what it doesn't do is then update the site.site_class_code which seems to be the same drop down options.

    So i'm even more confused as to what Confirm is doing with the NSG upload and concerned that our data is incorrect for our inspections. Why isn't the NSG linked between Site/Central Site/Feature/Site Interest etc etc. seems like an incredibly labourious task to correct everything when you use Confirm as a contractor to carry out Condition surveys etc.

    ------------------------------
    Ana Resende
    Gloucestershire County Council
    GLOUCESTER
    ------------------------------



  • 3.  RE: NSG Import specification

    Employee
    Posted 03-25-2020 03:10

    Hi Ana

    Neither Category nor Classification is populated from an NSG import.

    NSG data is stored in fields in the Site form. Some fields, such as Site Code (USRN) are used for NSG, and non-NSG records, but the majority of the fields used are specifically for the NSG and have no function in Confirm.

    The below table shows where fields given in NSG Data Transfer Format 8.1 are stored in the Confirm Site form.

    Tab

    Site fields

    LSG field

    Record type

    Site

    Code

    USRN

    11,12,13,14,15

     

    Name

    STREET_DESCRIPTOR

    15

     

    Organisation

    SWA_ORG_REF_NAMING

    11

     

    Street Type

    RECORD_TYPE

    11

     

    Locality

    LOCALITY_NAME

    15

     

    Address

    Concatenation of STREET_DESCRIPTOR LOCALITY_NAME TOWN_NAME ADMINISTRATIVE_AREA

    15

     

    State

    STATE

    11

     

    State Date

    STATE_DATE

    11

     

    Surface

    STREET_SURFACE

    11

    Additional

    Start Date

    STREET_START_DATE

    11

     

    End Date

    STREET_END_DATE

    11

     

    Version

    VERSION

    11

     

    Extent 1 Easting

    STREET_START_X

    11

     

    Extent 1 Northing

    STREET_START_Y

    11

     

    Extent 2 Easting

    STREET_END_X

    11

     

    Extent 2 Northing

    STREET_END_Y

    11

     

    Tolerance

    STREET_TOLERANCE

    11

     

    ASD data is all stored under the Site form 'Other' button.

    One thing to note - the Road Statuses (found in Type 61 Interest records) are stored in the Classification Lookup - but not entered into the Classification field in the Site form, only into the Road Status field in the Interest records.

    I hope that clarifies things for you

    Regards

    Wendy



    ------------------------------
    Wendy Damon
    Principal Consultant
    Professional Services Group – Confirm
    ------------------------------



  • 4.  RE: NSG Import specification

    Posted 03-25-2020 14:39
    Hi Wendy,

    Thank you for that, you have actually confirmed my worst fears.

    The Classification field is used to be able to quickly ascertain whether a site is maintainable by us or whether it is another authority's or even Private. This data is collected in the NSG, and if we adopt Private roads, they become publicly maintained in the NSG - as shown in the Additional tab and Interests, which as your reply shows is updated by the NSG.

    Now, because the classification is not updated, and the feature classification isn't updated either, this means that our Inspectors are out there using Confirm Connect and looking at the Feature data and believe a road is private when in fact it has been adopted.

    So this means that at every NSG update we will have to use data sources to cross match data, and then create CSV/TXT files for mass upload through the Import Anything feature. This seems madness and a lot of work, when the NSG is telling Confirm the correct data.

    I wonder how other users and authorities deal with their NSG upload and making sure features/sites have the right information...

    ------------------------------
    Ana Resende
    Gloucestershire County Council
    GLOUCESTER
    ------------------------------



  • 5.  RE: NSG Import specification

    Posted 04-08-2020 03:56
      |   view attached
    Morning Ana
    Sorry if I'm a bit late coming to the party.
    When importing the NSG into Confirm the interest (Type 61) should hold the 'interest' of the street and indicate whether private or not.  However as we maintain the LSG in Confirm using the NSG manager any change is status should not be a surprise as that is where we record in the first instance.  For non NSG business i.e. site records we use a combination of the Customer field and Classification field to indicate if the street is private or another authority or maintained.
    When a street is adopted the Customer is updated to reflect the change and the Classification is also changed. the lookup table behind the Classification field will automatically be updated the type 61 interest record so that at your next export all is correct.
    As a picture tells a thousand words I have attached two examples. NOTE: The text used in the look up is locally derived the important part is the look-up table having the correct DfT codes.

    ------------------------------
    Tony Neill
    EAST RIDING OF YORKSHIRE COUNCIL
    BEVERLEY
    ------------------------------



  • 6.  RE: NSG Import specification

    Posted 04-08-2020 04:19
    Morning Tony,

    Thank you for the reply.

    You are correct in that we use Customer and Classification in the same way; my main issue is that the NSG import does not automatically update these. As you said, it's not a problem if maintain your NSG within Confirm as these are done as rote, but if the NSG is maintained in another system and you use the GeoPlace download to update the NSG in Confirm (like Gloucestershire do) then you will need to build data source reports to identify where changes have happened and then update the fields manually/via Import Anything. This is cumbersome and time consuming considering Confirm imports all the information anyway, just that it doesn't put it in all the fields.

    Even if we didn't update the Customer/Classification field and just used Interest; or even if it update the site's Customer/Classification; this still doesn't do anything to the feature itself, which is what is inspected/maintained.

    Another example of this lack of linking is an issue we have encountered with new sites being created by the NSG Import, but  corresponding Whole Street Features aren't created. Again, this means that inspectors cannot select that site for inspecting and/or creating defects. So each month we have to physically check which sites have/don't have WSF's, and we have to manually create those that are missing and, crucially, "dead" those whose sites have been flagged as "dead" too.

    It just seems that there has been very little consideration given to those whom use Confirm as a "promoter" of works rather than as the Authority.

    ------------------------------
    Ana Resende
    Gloucestershire County Council
    GLOUCESTER
    ------------------------------



  • 7.  RE: NSG Import specification

    Posted 04-09-2020 09:19
    Hi, I'm probably too late to this discussion.  At Hertfordshire we only use the Site form for standard NSG data, holding ASD etc.  The fields such as Classification can't be used to indicate anything to do with classification or status or ownership - simply because a site will usually have many streets and/or footpaths associated with it, some will be private, some will be maintainable.  It is only at feature level within a site that this sort of information can be shown.  We do that by having Network features under sites, providing all of this information.  The NSG fields and ASD are maintained completely separately to the Network features.  This can lead to the risk of maintaining things multiple times, but it does give us the ability to show things as they really are.
    Mark (Hertfordshire CC Custodian)​

    ------------------------------
    Mark Allan
    Hertfordshire County Council
    Stevenage
    ------------------------------



  • 8.  RE: NSG Import specification

    Posted 04-09-2020 09:42
    Hi Mark,

    Thank you for the reply.

    Can I ask - do you maintain your NSG in Confirm? or do you upload from GeoPlace?

    If the latter, how do you sort through the NSG data to maintain your features should adoption status or new USRN's be added?

    As I mentioned in the previous reply, the NSG import doesn't update features, so we are faced with various data issues hence why we were wondering how other users go about maintaining the data.

    Ana

    ------------------------------
    Ana Resende
    Gloucestershire County Council
    GLOUCESTER
    ------------------------------



  • 9.  RE: NSG Import specification

    Posted 04-14-2020 02:40
    Hi Ana,
    Yes, we do maintain everything in Confirm. We don't let Confirm automatically update anything, we do it all manually. When a road is not maintainable, then we only have a network feature that indicates this, or many network features if there are many parts of the road.  When it is adopted then we update those network features, and get the inventory features added (signs gullies etc).  The NSG is updated separately, Dedication records and ASD.​  Authorities use features in different ways, with non-NSG site fields used for many purposes. We chose to ignore those fields and maintain our network through the features.  If you only have one network section per site then I am sure there are simple reports that can be written to update your features, but I agree it's generally more complicated that that in reality.

    Mark

    ------------------------------
    Mark Allan
    Hertfordshire County Council
    Stevenage
    ------------------------------