Conversation
Member
Author
|
@reussinho , this is something you've requested as an enhancement, hope this will be helpful to your surveys :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements enhancement request filed here (#9). A new parameter found in the advanced settings group box allows for users to pick a CRS to set the generated project to.
If the generated project has features, the combined extent of those feature geometries will be used as default extent. If the project is empty, a default extent derived from the picked CRS' bounds will be generated.
In addition, a new extent parameter was added to set a custom default extent when opening the generated project. This can come in handy in models and scripts using the converter to create surveys where features are not yet added but where the area of interest is already known.