olkitu / mobilespectrum Goto Github PK

From: https://gitlab.com/mobilespectrum/MobileSpectrum/-/issues/4

Frequency allocations change over time as new operators enter markets or just due to re-allocation by regulator.
There should be a way to enter historical data for each band, showing the date of the change taking effect as well as allowing notes as to why the change occurred (e.g. 25MHz swapped from operator A to B due to re-allocation by regulator)

Is your feature request related to a problem? Please describe.
It is common for the same providers to own spectrum in multiple different blocks in many different frequency bands. Each time, we must currently re-define the provider information, this increases data duplication, makes the schema files longer and harder to read and increases the likelihood of errors.

Describe the solution you'd like
Each country should also have a defined list of providers and a key associated with each unique provider, then in the spectrum file we should reference the key of the provider.

Example of src/data/operators/united_kingdom.json

{
  "ee_uk": {
	"name": "EE",
	"longName": "Everything Everywhere",
	"homePage": "https://ee.co.uk",
	"backgroundColor": "#007b85",
	"textColor": "white"
  }
}

Then to reference a provider in src/data/countries/united_kingdom.json we use the key defined in the operator file:

[
  {
	"band": 67,
	"providers": [
	  {
		"provider": "ee_uk",
		"frequency": {
		  "downLink": {
			"start": 738,
			"end": 758
		  }
		},

To allow for backwards compatibility we can check the type of the "providers" key to see if it is a string, if so, we check for an operators schema file and then find the operator data.

This will have the advantage of only needing to change one file to update data for an operator rather than updating multiple entries to change an operators colour for instance.

Please let me know your thoughts

From: https://gitlab.com/mobilespectrum/MobileSpectrum/-/issues/5

Easy tool to generate JSON data file for our contributors

From: https://gitlab.com/mobilespectrum/MobileSpectrum/-/issues/8

In Thailand, Spectrum is shared among multiple providers such as B40 60 MHz is shared between dtac and NT with 60/40 airtime. NT is the spectrum owner, but dtac is responsible for tower deployment. It would be nice if we can list both providers on the same slot and color the slot in the way that people understand that it's frequency sharing.

Improve SEO - build sitemap automatically from JSON file path's and names every deploy.

The workflow main.yml is referencing action actions/checkout using references v1. However this reference is missing the commit a6747255bd19d7a757dbdda8c654a9f84db19839 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

From: https://gitlab.com/mobilespectrum/MobileSpectrum/-/issues/10

Estonia data missing some spectrums

From: https://gitlab.com/mobilespectrum/MobileSpectrum/-/issues/6

Currently there are very little checks for country data, it may be useful to implement:

Frequency type checking

If type is SDL / SUL / TDD, are uplink / downlink values the same?
If type is FDD, are uplink and downlink bandwidths same width? Are there exceptions?

Bandwidth checking

No negative bandwidth values

ARFCN checking

Are ARFCN values outside of ranges for that band?

Prerender all website pages to improve website SEO. This also improve support on legacy browser and make site loading faster when no need wait javascript.

• Prerender enabled
• Prerender all subpages

From: https://gitlab.com/mobilespectrum/MobileSpectrum/-/issues/11

Links to source broken: http://e-consultare.gov.ro/w/wp-content/plugins/download-attachments/includes/download.php?id=5726

https://mobilespectrum.org/romania

I've made a pull request to update Portugal Spectrum

#119

Do I need to take further steps ?