Skip to content
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

Predefined area selection doesn't work properly #75

Open
MarioLocati opened this issue Jan 8, 2024 · 1 comment
Open

Predefined area selection doesn't work properly #75

MarioLocati opened this issue Jan 8, 2024 · 1 comment

Comments

@MarioLocati
Copy link
Member

MarioLocati commented Jan 8, 2024

The plugin does not correctly set the geographical coordinates associated to each predefined geographical area as set in the configuraion file at https://github.com/INGV/qquake/blob/master/qquake/config/config_services_styles.json#L224

image

@robertovallone
Copy link
Member

It's pretty strange - slightly unpredictable - behaviour.
The plugin shows different behaviours for different services, i.e.

  • AHEAD-EPICA: the data-related bounding box is chosen
    boundingbox: [ 22 -23.5, 23 35, 24 32, 25 69 26 ]
    instead of the service-related one
    "boundingboxpredefined": "Europe",
    If the user chooses another predefined area, the plugin works as expected except for "Europe" and "World", where (again) the data-related bbox is used for the query.

  • EMSC-CSEM: everything works as expected;

  • ETHZ-SED: the query is possible only for data-related bbox (which coincides with service-related one), whichever predefined area the user chooses. The only exception is for Greece, where a bbox [11.0, 45.4, 11.0, 45.4] (a single coordinate) is queried, but such "bbox" is not defined anywhere...

  • INGV ASMI-CPTI: again, the data-related bbox is queried per default while all the predefined areas work with wrong coordinates, different from those declared in the config_services_styles.json file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants