TDS | Transport Data Science

The idea is pretty simple: You can scrape all the positions, modify the URL and search for all players. In code:

You can use border-width. Or in your case, border-right-width:

You have jQuery - use its power

It is not recommended to loop to add eventListeners in JavaScript, jQuery or not.

Probably went overboard, but I edited your function to calculate the data-value division (if 'division' was selected), then reverse it if you subsequently seleected 'original'. 'Original' still divides by 1 if you don't select division first, but after 'division' has been selected, if you select 'original' it will revert. To make this part easy, I added a data-orig attribute to your td setup. Like i said, overboard...

Here's how I might approach this. First, grab the initial table row on load to use as a clone template (before the user can enter any data). Then just append that to the table's body as needed using a click handler on the button, along with submitting an ajax request.

Note that I've moved your button outside the table. It wasn't valid there.

You are using the same table variable for #main-table and for the results table. However the results table variable is only available inside buildTable(), and when you use modalBody.append(table); outside of that function, you are moving the #main-table instead. So for your own sake, try avoid recycle variable names.

Also, you don't have to use getElementById for the element you just created via createElement()

I can assure you there's probably a better answer than this, but the following code works:

After a bunch of trials and errors, I founded a comprehensive solution to this.

when we dealing with a GeoJson file, each feature can (or even should!) save in a separate NetTopologySuite.Geometries.Geometry type. (in other words, I changed the structure of my table from one stand-alone table to two tables with a parent child relationship)

In fact, we don't need to serialize any things manually when are using NetTopologySuite.IO.GeoJSON4STJ. in our code, we only need to work with NetTopologySuite.Features.FeatureCollection and add NetTopologySuite.IO.Converters.GeoJsonConverterFactory to JSON converters when we add controllers. but there is also a trick here, at the registration time we should use NetTopologySuite.Geometries.GeometryFactoryEx instead of NetTopologySuite.Geometries.GeometryFactory (attention to the Ex word at the end). the reason for this is SQL server Require left-hand-rule (CCW) but GeoJson Required right-hand-rule (REFRENCE) so:

Each row (tr) has to have the same amount of cells (td). Except if you are using colspan, but then the sum of the spanned cells and the other (single) cells still have to be the same amount.

So your table have to look like this: