search

nycmeshnet / meshdb

A convenient, stable, and sane database for tracking Members and Nodes for use with robots and humans
https://db.mesh.nycmesh.net
MIT License
8 stars 13 forks source link

Fix map data issues #480

Open Andrew-Dickinson opened 3 weeks ago

Andrew-Dickinson commented 3 weeks ago

Our map has once again diverged from nycmesh.net/map/ in a few ways. Fix them :(

Andrew-Dickinson commented 3 weeks ago

Root causes:

  1. Fiber links being imported as ethernet
  2. AP Objects not being created at import time
  3. Data schema gap: going to be handled separately here: #489
  4. VPN links being imported as ethernet
  5. Auto-fixed once an online install was added to the spreadsheet
  6. Auto fixed? Maybe because olmsted was offline before
  7. Import issue, these hubs are importing as "standard" due to a bug, fixed in #495
  8. Import issue, not importing as POP in meshdb
  9. Auto fixed? Maybe because olmsted was offline before
  10. Extra building getting created for apt 22D, spreadsheet data issue
  11. Likely a data issue, I think I cleaned this up in #239, let's see if things are better after the next import
  12. Bug in map data logic (fixed here #496)
  13. Install which pre-dates the NN, also fiber import issues due to UISP type of ethernet (fixed here #495)
  14. Node-level display overrides not being respected (fixed here #516)
  15. Duplicate spreadsheet link was causing us to set it as "planned" and therefore hidden. Fixed in spreadsheet data
Andrew-Dickinson commented 2 weeks ago

Okay that's a lot of problems and a lot of solutions, let's get those PRs merged and see if things look better