Add doc page on map projections in RIOS - #213
Merged
Merged
Conversation
gillins
reviewed
Aug 9, 2026
|
Looks good to me @neilflood. Just the right level of detail here on a topic where I have been stuck before, so I think this extra documentation is a very useful addition. |
Member
Author
|
Thanks @petescarth :-) |
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
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.
Ping @gillins, @petescarth
After our recent chats about map projections, I realised that there is very little documentation about how RIOS works with map projections. One thing I wanted to add was a bit of explanation for the newly added
controls.setFilesForExtentfunction, but as I started to write something for that, I saw that it wouldn't hurt to add a bit more about the topic in general. The result is this new doco page.I would be grateful for any thoughts either of you may have on this. Is there anything else I should mention? I don't want to be too verbose, but just any traps that are not immediately obvious.