-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generic BUFR scan for mobile stations #199
Comments
Technically, we cannot. The database has no field for distinguishing mobile from fixed stations except for If there is a need to change that requirement, it shuold be discussed separately, as it is a significant API and behavioural change, and repercussions need to be evaluated. See for example ARPA-SIMC/dballe#150 |
I agree with @spanezz. The scan proposed is too simple for any cases. In the rpm package the scan files are not marked as configuration so is not possible any adaptation for special use; any update remove any changes. So I think should be useful to permit some local configuration. In my special user case I have three cases:
I use the network to discriminate the special case 2) because I want search them with a standard lat/log query (that is possible with dballe too) and not using boxes. |
Since now we made the scanner registration system more flexible, we can package the standard scanners as part of the arkimet python modules, and ship an empty directory in |
Questa issue è stata chiusa per inattività. Nel caso in cui sia un argomento ancora rilevante, si prega di riaprirla con una motivazione che tenga conto delle modifiche applicate nel corso degli anni al progetto. |
@pat1 propose to use the following scanner for generic BUFR:
The only difference that I can find with the current scanner is that when the report name is the
mobile
string it scans the area as a mobile station. E.g. a mobile station with lon = 12.12345 and lat = 43.12345 will havearea:GRIB:type=mob,x=12,y=43
, whereas a fixed station will havearea:GRIB:lat=1212345,lon=4312345
.This means that only the stations with
rep_memo=mobile
will be considered as mobile stations. At SIMC, we don't have any mobile stations with generic template, then for me it's not a real problem, but maybe we could write a more customizable scanner, e.g.Note: the scanner will be implemented in Python (see #177).
A final thought: in the past, a station was considered a mobile station if its
ident
was not null: are we officially dropping this rule?The text was updated successfully, but these errors were encountered: