Opened 3 years ago
Last modified 7 days ago
#386 new task
add how to define custom projections (with recent PROJ) into README
| Reported by: | Jeff McKenna | Owned by: | Jeff McKenna |
|---|---|---|---|
| Priority: | major | Milestone: | future |
| Component: | MS4W - Documentation | Version: | 4.0.5 |
| Keywords: | Cc: | TC Haddad | |
| Blocked By: | Blocking: |
Change History (6)
comment:1 by , 16 months ago
| Milestone: | 5.0.0 release → 5.0.1 release |
|---|
comment:2 by , 8 months ago
| Milestone: | 5.0.1 release → 5.2.0 release |
|---|
comment:3 by , 8 days ago
| Description: | modified (diff) |
|---|
comment:4 by , 8 days ago
| Description: | modified (diff) |
|---|
comment:5 by , 7 days ago
@tchaddad I experimented with trying to add a custom projection into proj.db (or a separate file of proj-custom.db)....yikes. Not easy (and the structure of the PROJ sqlite database tables seems to change often). I am hesitant to write detailed steps in the MS4W readme.
For now, I've added a "Warning" into the existing section of the readme "Using Custom EPSG Projections" :
"The following custom projection steps are for MS4W versions 4.0.5 and older. For more recent MS4W versions, if you do plan to try to add a custom projection, it is recommended to not modify the shared proj.db but instead use a separate file such as proj-custom.db, and implement the PROJ_AUX_DB environment variable."
comment:6 by , 7 days ago
| Milestone: | 5.2.0 release → future |
|---|
Note:
See TracTickets
for help on using tickets.
Milestone renamed