Hardcode landing point data into "points" database

[ethanjweiner]

Task Title

Task: Hardcode landing point data into "points" database

Task Description

This Task will...

• [Pre-filled] Create a related "landing points" table that includes all of the landing point information
• [Pre-filled] Create a related "cable" table that includes a list of all the nodes and the endpoint
• Query all the landing points on load, determine their continent codes, & store these landing points in the "points" table

Why use single-table inheritance (store routers & points together)? Because it makes it easier to query ALL points at the same time, & choose accordingly. Maybe it would've made sense to store them in separate tables (e.g. we could've searched EACH of those tables for neighbors, and acted accordingly). But our database is already designed as a single table, so I'd rather not mess with the implementation now.

Epic Parent

Feature: Awesome Feature Title

[ethanjweiner]

For simplification, all landing point data should be stored using the ORM and SQLAlchemy.

• "Landing points" table: [Hardcoded] [Using Python] Load landing points from GEOJson into table, extracting the continent by using relational queries
• "Paths" table: [Hardcoded] [Using Python] Create a table of paths by looping through all the cables JSON, and inserting every 2-node subset into this table

Update the "store_points" function to only delete & store routers....