-
Notifications
You must be signed in to change notification settings - Fork 409
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
#9241 profile en long #9242
#9241 profile en long #9242
Conversation
# Conflicts: # web/client/product/plugins.js
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems this implementation is following the structure of the StreetView one. If so I think all related actions, reducers, epics and selector should be included in a folder called LongitudinalProfileTool that export as index the plugin
- I'm seeing changes in the icon files but there is not a new svg icon file added to the folder
@@ -1,3 +1,4 @@ | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change seems related to a different PR #9188.
I think if we are not publishing the new package this should be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think i have to recreate my master branch to fix this
will force push without it
@@ -29,6 +29,6 @@ | |||
"eslint": ">= 7.5.0", | |||
"eslint-plugin-import": ">= 2.20.2", | |||
"eslint-plugin-no-only-tests": ">= 2.3.1", | |||
"eslint-plugin-react": ">= 3.3.2" | |||
"eslint-plugin-react": ">= 7.31.11" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sime for this file:
This change seems related to a different PR #9188.
I think if we are not publishing the new package this should be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correct, going to remove
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The layout of the PDF exported should be reviewed. At the moment the map is too small and the chart to big with loss of resolution. The layout should be the opposite as requested (see internal requirements document).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few additional points:
- If you expand the chart you can't collapse it
- The plugin button in the sidebar is not always rendered when you load the viewer. Maybe something connected to how the plugin lazy loading is implemented. This should be reviewed.
- When you deactivate the long profile tool, the identify is not reactivated. They are not properly mutually exclusive and the deactivation of the long profile button is not well handled in one case since the button is toggled but the tool is not effectively active (see the video below)
how about this one ? |
fixed locally
do you have a way to constantly reproduce this? It does not happen to me.
i have this to check now and then I can submit a new PR |
There is too much empty space at the bottom. You can do the chart and the map a little bit bigger to cover also this |
I'm on tomcat. This is a map created from a context. The same problem happens at context level:
|
probably you are right, it's a tedious fix but I can make this, in 2h
fixed, there is no new icons but I have not removed the new generated files. not an issue then |
closed in favor of this #9253 |
Description
This pr introduce a new plugin called longitudinal plugin that works in combination of a new wps process gs:LongitudinalProfile that can be found here
to review this locally i suggest to install that jar in a local geoserver proxying to it and publish sfdem layer too,, you can found it here
also by default this is not enabled in main viewer and
can only added in a context
it should also not conflict with the current similar implementation here
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#9241
What is the new behavior?
Now you can use the longitudinal profile plugin needs wps on geoserver
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information