-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
mapfile export - some issues #11171
Comments
Author Name: Paolo Cavallini (@pcav) In addition, the file is saved without extension (.map) |
Author Name: Richard Duivenvoorde (@rduivenvoorde) Reviewing:
|
Author Name: Richard Duivenvoorde (@rduivenvoorde) Replying to [comment:1 pcav]:
This is fixed somewhere in history
|
Author Name: Richard Duivenvoorde (@rduivenvoorde) I will close this issue, for it is this old, holds a lot of different issues from which most of them (or all??) are fixed in the meantime. If parts of it are still valid, please issue new ones.
|
Author Name: mschulz - (mschulz -)
Original Redmine Issue: 1111
Redmine category:python_plugins
Assignee: Richard Duivenvoorde
Mapfile export with the python plugin in "io" has some flaws. I tried patching some of them, and will attach the changed files:
export of postgis statements was wrong (see ticket Mapfile export PostGIS layers #11164)
export of layers only still writes whole mapfile
export uses proj4 string to create mapfile projection element
export doesn't distinguish between mapfile projection and layer projection
symbology creation changed wrt. to geometry type (e.g. WIDTH instead of SIZE, OUTLINECOLOR instead of FILLCOLOR)
export dialog select box "units" shouldn't translate UNITS values
Use whatever you want from the suggested changes. Cheers, Michael
The text was updated successfully, but these errors were encountered: