Hi
I was asked more then one time now, if the map-styles rendered on the toolserver are opensource and where to get them. I was not able to answer those questions definitely.
To get this cleared I'd suggest the following: All styles hosted on ptolemy will get copied into the osm project's home dir and published into its svn repository [1]. This way we have control over style changes and have a known location to check for the sources.
Having control over style modifications is a good thing in our shared environment, because that way we'll know why tirex won't start after a modification.
Are there any objections against collecting all style files under the osm account and publishing them into the svn? Unwe which license would the style files stand? Can the license be different for the styles or even be none-free?
Peter
Hi,
Am 22.09.2010, 11:01 Uhr, schrieb Peter Körner osm-lists@mazdermind.de:
I was asked more then one time now, if the map-styles rendered on the toolserver are opensource and where to get them. I was not able to answer those questions definitely.
You probably need to ask "everyone" separately. For my styles (parking map) it's ok, I consider them being under a "cc-by-sa"-like license´, like most of the osm stuff.
Ciao, Kay
Hi,
2010/9/22 Peter Körner osm-lists@mazdermind.de:
I was asked more then one time now, if the map-styles rendered on the toolserver are opensource and where to get them. I was not able to answer those questions definitely.
FWIW, I maintain the hikebike and lighting styles here right now: http://mapnik-utils.googlecode.com/svn/sandbox/cascadenik/hike_n_bike/ and the license is PD.
To get this cleared I'd suggest the following: All styles hosted on ptolemy will get copied into the osm project's home dir and published into its svn repository [1]. This way we have control over style changes and have a known location to check for the sources.
Having control over style modifications is a good thing in our shared environment, because that way we'll know why tirex won't start after a modification.
I would move from the mapnik-utils repository to the toolserver if people agree this is a good thing to do (I think it is, yes).
The "control over style modifications" part slightly more complicated for the hikebike (and lighting) style since you'd need to run Cascadenik to get the XML format usable for Mapnik, then post-process it a bit. I should make this push-button at some point... Maybe we can just commit a known-good generated XML file to a special "ready to be deployed" directory, from which it gets pulled into a working copy for tirex (via an SVN hook) or something - even if you normally do not put generated files under version control.
Cheers Colin
Hi,
2010/9/22 Colin Marquardt cmarqu42@googlemail.com:
To get this cleared I'd suggest the following: All styles hosted on ptolemy will get copied into the osm project's home dir and published into its svn repository [1]. This way we have control over style changes and have a known location to check for the sources.
Having control over style modifications is a good thing in our shared environment, because that way we'll know why tirex won't start after a modification.
I would move from the mapnik-utils repository to the toolserver if people agree this is a good thing to do (I think it is, yes).
I was going to do that now, and filed https://jira.toolserver.org/browse/TS-771 since you don't automatically get commit rights as a member of p_osm.
(And FWIW, I have modified the hikebike style slightly (and tested it), but I don't know how to deploy it now that we have tirex :)
Cheers Colin
2010/9/25 Colin Marquardt cmarqu42@googlemail.com:
Hi,
2010/9/22 Colin Marquardt cmarqu42@googlemail.com:
To get this cleared I'd suggest the following: All styles hosted on ptolemy will get copied into the osm project's home dir and published into its svn repository [1]. This way we have control over style changes and have a known location to check for the sources.
Having control over style modifications is a good thing in our shared environment, because that way we'll know why tirex won't start after a modification.
I would move from the mapnik-utils repository to the toolserver if people agree this is a good thing to do (I think it is, yes).
I was going to do that now, and filed https://jira.toolserver.org/browse/TS-771 since you don't automatically get commit rights as a member of p_osm.
Okay, I learned now that you commit as your own user, not as the "osm" user. Use the LDAP password you have set (https://wiki.toolserver.org/view/Subversion).
The (incomplete) style is now in http://svn.toolserver.org/svnroot/p_osm/styles/hikebike/, I hope to switch to SVG icons before I add all the little PNG icons in different sizes etc.
Cheers Colin
Am 25.09.2010 17:19, schrieb Colin Marquardt:
(And FWIW, I have modified the hikebike style slightly (and tested it), but I don't know how to deploy it now that we have tirex :)
I'll try to document our TS Setup today and this will be a part of it.
The (incomplete) style is now in http://svn.toolserver.org/svnroot/p_osm/styles/hikebike/, I hope to switch to SVG icons before I add all the little PNG icons in different sizes etc.
SVG Icons work only with mapnik trunk. I'm not sure if we should switch the mpanik version before they publish a 0.7.2.
Peter