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

Import/export 'DXF Export' dialog settings from/to XML #35

Closed
wants to merge 70 commits into from

Conversation

gacarrillor
Copy link
Owner

@gacarrillor gacarrillor commented Mar 15, 2024

This PR enables users to save and restore GUI settings for the DXF Export dialog, making it possible to export a number of configurations and reuse them or share them with colleagues.

Settings are exported to an XML file.

2024-03-18.15-39-29.mp4

image

ptitjano and others added 26 commits March 13, 2024 16:33
A WFS request such as
`SERVICE=WFS&REQUEST=GetFeature&VERSION=1.1.0&SRSNAME=EPSG:4326` does
not invert the axis and return the coordinates in the LON/LAT
order. For example:

<gml:Envelope srsName="EPSG:4326">
  <gml:lowerCorner>2.358 48.865</gml:lowerCorner>
  <gml:upperCorner>2.37 48.876</gml:upperCorner>
</gml:Envelope>

However, the same request without a SRSNAME parameter inverts the axis
and returns the the coordinates in the LAT/LON order:

<gml:Envelope srsName="EPSG:4326">
  <gml:lowerCorner>48.865 2.358</gml:lowerCorner>
  <gml:upperCorner>48.876 2.37</gml:upperCorner>
</gml:Envelope>

With this change, the axis is not inverted if the SRSNAME parameter is
not passed. This way, this is the same behavior as
`SRSNAME=EPSG:4326`.

This is a follow-up of qgis#45270.
This fixes UNC paths not identified as network paths.

By ensuring that a trailing slash for directories is passed
down to the identify function.
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.4 to 1.15.6.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](follow-redirects/follow-redirects@v1.15.4...v1.15.6)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
…attempt-2

Browser: fix slow behavior with network drives on windows
qgswfsgetfeature: Do not invert axis if no SRSNAME is passed
The original version number check was completely random numbers
Attempts to set the input band for the renderer.
Returns TRUE if the band was successfully set, or FALSE if the
band could not be set.

This was implemented in various raster renderer subclasses,
but it was necessary to down cast and then call the individual
methods (which don't have consistent names!).

Instead, add a top level virtual method so that it's easy to
change the input band for the renderers.
Copy link

github-actions bot commented Mar 15, 2024

🪟 Windows builds ready!

Windows builds of this PR are available for testing here. Debug symbols for this build are available here.

(Built from commit 72249d6)

This introduces a new option for specifying how raster layers
have associated elevation. It permits a fixed elevation range
to be set for the layer. It can be used when the layer has
a single fixed elevation, or a range (slice) of elevation values.

Users can set the lower and upper elevation range for the layer,
and whether the lower or upper limits are inclusive or
exclusive.

When enabled, the layer will only be visible in elevation
filtered 2d maps when the layer's range is included in the map's
z range.
nyalldawson and others added 10 commits March 18, 2024 21:26
And selectively expose some of QgsRasterRendererRegistry to python
Just like the equivalent mode for raster layers, this mode indicates
that a fixed constant z range should be applied to the entire mesh
layer.
Use the processing context's ellipsoid instead of a hardcoded
WGS84 ellipsoid for distance calculations during network
analysis, so that the lengths used will exactly match other
measurement tools used on the same features in the same
project.
@gacarrillor
Copy link
Owner Author

@3nids, thanks for the review.

By the way, I'm not yet loading layer settings (e.g., attribute index) from XML because first I'd like to know your opinion on this.
In the XML file we have the layer's public source, so when loading, should we check if the XML layer's public source matches with a tree view layer's public source?

@3nids
Copy link

3nids commented Mar 20, 2024

I'm not sure what is expected in terms of configuration for the layer. Do we even need it? Could we live with a simple ID checking? Or we need a full config that is able to load layers?

@nirvn do you have more info about the specs

src/app/qgsdxfexportdialog.cpp Outdated Show resolved Hide resolved
src/app/qgsdxfexportdialog.cpp Outdated Show resolved Hide resolved
src/app/qgsdxfexportdialog.cpp Show resolved Hide resolved
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.

9 participants