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

Releasing 2.6.8 #160

Merged
merged 6 commits into from
Sep 12, 2023
Merged

Releasing 2.6.8 #160

merged 6 commits into from
Sep 12, 2023

Conversation

Nikolai558
Copy link
Owner

No description provided.

This fixes the problem when Filters = "", however, currently it will place filters = [] in the geojson.
Not sure how CRC Will handle a default that does not have any filters in it.
When `filters=""` in the defaults, it will then look at the `bcg=##`. As long as bcg has a valid number it will make the filters = bcg.
@Nikolai558 Nikolai558 linked an issue Sep 12, 2023 that may be closed by this pull request
I am going to recant my previous statement and will not be placing the filter value based on BCG values.

The reasoning behind this is there might be quite a few facilities where the BCG value is not supose to match the filter value. Also, in vERAM things that do not have a filter at all are not displayed (same thing happens in CRC). If I were to automatically place the bcg into the filter in the geojson, these facilities would have a bunch of things populate on screen that were never there before.

I personally don't know of a valid reason to set filters="" but I do know that some facilities do it.

Therefore, FEB will create the defaults in geojson with filters = [] and a message will be placed in the log so that users can quickly find what default filters dont have any filters in it. Then they can choose weather or not they want to add filters manually in the geojson. This result should be the same in CRC as it is in vERAM. (i.e. no filters = no display)
@Nikolai558
Copy link
Owner Author

I am going to recant my previous statement and will not be placing the filter value based on BCG values.

The reasoning behind this is there might be quite a few facilities where the BCG value is not supose to match the filter value. Also, in vERAM things that do not have a filter at all are not displayed (same thing happens in CRC). If I were to automatically place the bcg into the filter in the geojson, these facilities would have a bunch of things populate on screen that were never there before.

I personally don't know of a valid reason to set filters="" but I do know that some facilities do it.

Therefore, FEB will create the defaults in geojson with filters = [] and a message will be placed in the log so that users can quickly find what default filters dont have any filters in it. Then they can choose weather or not they want to add filters manually in the geojson. This result should be the same in CRC as it is in vERAM. (i.e. no filters = no display)

Now it will still create a default inside the geojson, however the filter will just be blank. ex. filter = []. It will also place a message inside the log file, so users should just be able to "find" WARNING messages and fix their file as needed.
image
image

@Nikolai558 Nikolai558 merged commit e4fc461 into releases Sep 12, 2023
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

Successfully merging this pull request may close these issues.

[BUG] - vERAM-GeoJSON "Input String" error
1 participant