add OGR Spatialite section #3
Closed
Conversation
This file contains 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
|
Thanks a lot @elil , I am working on the new manual and will integrate this directly there. |
moovida
added a commit
that referenced
this pull request
Apr 13, 2017
|
Ported this to the new user manual - manually. Thanks. |
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.
A recent discussion on the email list and a GDAL/OGR changeset makes it easy to produce Spatialite databases for Geopaparazzi.
This PR adds a short section to the manual explaining how to do that.
-f "SQLite"and-dsco SPATIALITE=YESare the critical switches. Eventually, the note about which GDAL/OGR version it is available in could be removed.Is
-t_srs "EPSG:3857"the correct projection to avoid reprojection on the client side? I wasn't certain about that.