Skip to content
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

Closed
qgib opened this issue May 26, 2008 · 4 comments
Closed

mapfile export - some issues #11171

qgib opened this issue May 26, 2008 · 4 comments

Comments

@qgib
Copy link
Contributor

qgib commented May 26, 2008

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


@qgib
Copy link
Contributor Author

qgib commented Oct 19, 2008

Author Name: Paolo Cavallini (@pcav)


In addition, the file is saved without extension (.map)

@qgib
Copy link
Contributor Author

qgib commented Mar 7, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


Reviewing:

  • export of postgis statements was wrong
    Is fixed

  • export of layers only still writes whole mapfile
    Is fixed somewhere in history :-)

  • export uses proj4 string to create mapfile projection element
    Fix proposed only working with old project file format. Now whe have a authority node which could be used for that. But I'm not sure if mapserver will take this (I mean other authorities then epsg ....). Besides this, the proj4 string will always work while only using the authority-code is more tricky eg on linux case sensitive (EPSG should then be cast to epsg etc).

  • export doesn't distinguish between mapfile projection and layer projection
    still a 'wantohave', please issue feature request

  • symbology creation changed wrt. to geometry type (e.g. WIDTH instead of SIZE, OUTLINECOLOR instead of FILLCOLOR)
    Fixed somewhere in history

  • export dialog select box "units" shouldn't translate UNITS values
    not sure about this, fixed?

@qgib
Copy link
Contributor Author

qgib commented Mar 7, 2011

Author Name: Richard Duivenvoorde (@rduivenvoorde)


Replying to [comment:1 pcav]:

In addition, the file is saved without extension (.map)

This is fixed somewhere in history


  • status_id was changed from Open to In Progress

@qgib
Copy link
Contributor Author

qgib commented Mar 7, 2011

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.


  • resolution was configured as fixed
  • status_id was changed from In Progress to Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant