karl | Knowledge And Resource Locator | Graph Database library

It is not a good idea to compare hours with hours, minutes with minutes and second with seconds to find which HH:MM:SS combination is the fastest. There can be cases like 04:50:56 < 05:00:00, which does not evaluate well in your original compareTo() method.

Try this code instead:

You can easily achieve this result using reduce and find. If the existing element is an array then you need to push it into array else create an array and push the existing element in the array along with new id

Here is a solution using the xml2 package. The strategy is to find the reported persons nodes and the parse out all of the subnodes. There are few duplicated node names and I attempted to reduce the number of conflicts, see the comments for more details. You may have to use the node's paths as the dataframe' column names.

You can do the following:

Your problem seems to be that document.querySelector("#searchbutton") returns null so that but1.addEventListener('click', searchClick); fails. Instead of searching for the reason I skipped adding a listener and directly attached the onclick function with

I recommend you use a listview.

You can do it like this:

First, use the wizard to lay out the listview (create it for you).

Delete all the templates - only leave in the item template.

So this is what the result is:

As Roshan mentioned, key orders aren't reliable in JS and really shouldn't be relied upon. If you need to maintain key order, I suggest using a map.

Here are examples of all both (including the unreliable object route):

Because object keys have no inherent order, this may not look correct if you run it in your browser console and expand your object, but if you run the snippet below, you'll see the correct, expected order in your console. To ensure the desired order, use a map, explained further down in section 2.

Change this line :

gridd.ItemsSource = dt.DefaultView;

To :

gridd.DataContext = dt.DefaultView;

As Deceze has commented, if the data is corrupted at source there is no guarantee that you can undo the corruption. However, using the data you provided we can make some progress.

Firstly, the vast majority of the strings in your list can be fixed by encoding as latin-1 and then decoding as UTF-8.