On Fri, Nov 16, 2012 at 8:24 PM, Matt Amos zerebub...@gmail.com wrote:
i agree, but would go further and suggest that the debugging view might be
better constructed on top of the showcase style, rather than being able
to (d)evolve independently of it. i would further suggest that the
On Wed, Nov 14, 2012 at 12:23 PM, Richard Fairhurst rich...@systemed.netwrote:
Matt Amos wrote:
i'd sound a note of caution about having separate clean and
detailed styles. we sort-of did that before with mapnik and
osmarender respectively and... well, we don't have
osmarender any more.
SomeoneElse li...@mail.atownsend.org.uk writes:
The thing that I was trying to have a stab at England and Wales designation
rendering, a bit like this question:
http://forum.openstreetmap.org/viewtopic.php?id=19032
However, after a lot of buggering about it had stopped raining, so I went
Paweł Paprota wrote:
My statement was based on my own experience with open source
projects.
I cannot be bothered to find some hard evidence that Github
makes people much likely to contribute though, it's just a fact. :-)
Your own experience is (I'm guessing) open source coding projects,
On 11/15/2012 09:46 AM, Richard Fairhurst wrote:
Whether or not we use git or svn for the Mapnik stylesheet is a question,
but not one which I think will have much bearing on the willingness of
people with cartography nous to contribute. More important are:
- moving from something that
Paweł Paprota wrote:
On 11/15/2012 09:46 AM, Richard Fairhurst wrote:
Whether or not we use git or svn for the Mapnik stylesheet is a
question,
but not one which I think will have much bearing on the willingness of
people with cartography nous to contribute. More important are:
- moving
There is anyway an issue with the current Trac instance :
source: subversion/applications/rendering/mapnik/osm.xml @ 28049
HTML preview not available, since the file size exceeds 102400 bytes.
Could somebody increase this limit to 200-300K ? According to the wiki it's
in
Hi,
On 11/13/2012 11:36 PM, Tom MacWright wrote:
There is no
way to 'just do it' until the style is actually maintained in GitHub,
actually welcomes contributions, and has active maintainers.
Point 3 (active maintainers) is undoubtedly true.
Point 2 (welcome contributions) is slightly
On 11/14/2012 12:04 PM, Frederik Ramm wrote:
Point 1 is purely a matter of taste; people are just doing it with
trac as well (and suffering from 2/3 there too).
Surely you cannot deny the fact that Github has extremely positive
effects on development?
Why Trac has nowhere near such an
Hi,
On 11/14/2012 12:57 PM, Paweł Paprota wrote:
With open source projects nowadays, having something in SVN and Trac is
like putting it in the basement and waiting until someone asks to see
your basement...
This particular basement seems to have been visited at least 400 times
without us
Hi all,
On 14/11/12 12:57, Paweł Paprota wrote:
Surely you cannot deny the fact that Github has extremely positive
effects on development?
I don't see the point in discussing SVN/Trac vs. Git/GitHub as both
systems are already in place. :-)
The problem I see is that both systems are
On 11/14/2012 01:09 PM, Frederik Ramm wrote:
I fully agree that GitHub is popular, but it is a pet peeve of mine
to point out that alternatives exist, just like other people will
complain if an Open Source project runs its mailing list on Google or
so. With GitHub in the hands of a commercial
On 11/14/2012 01:10 PM, Simon Legner wrote:
Hi all,
On 14/11/12 12:57, Paweł Paprota wrote:
Surely you cannot deny the fact that Github has extremely positive
effects on development?
I don't see the point in discussing SVN/Trac vs. Git/GitHub as both
systems are already in place. :-)
The
Matt Amos wrote:
i'd sound a note of caution about having separate clean and
detailed styles. we sort-of did that before with mapnik and
osmarender respectively and... well, we don't have
osmarender any more.
That was a technology failure, though, rather than anything wrong with the
On Wed, 14 Nov 2012, Frederik Ramm wrote:
I fully agree that GitHub is popular, but it is a pet peeve of mine to point
out that alternatives exist, just like other people will complain if an Open
Source project runs its mailing list on Google or so. With GitHub in the hands
of a commercial
On Nov 14, 2012, at 3:57 AM, Paweł Paprota wrote:
On 11/14/2012 12:04 PM, Frederik Ramm wrote:
Point 1 is purely a matter of taste; people are just doing it with
trac as well (and suffering from 2/3 there too).
Surely you cannot deny the fact that Github has extremely positive effects on
On Wed, Nov 14, 2012 at 8:23 PM, Richard Fairhurst rich...@systemed.netwrote:
- we don't have a debugging view, and that leads to inappropriate pressure
on the showcase style (e.g. the 8,000 tints for subtly different forms of
landuse)
Actually we do, and that's the data layer.
On 14/11/2012 16:34, Eugene Alvin Villar wrote:
Unfortunately, I think there's a perception that the data layer
doesn't provide the gratification that mappers want.
Absolutely, and it never well. The data layer looks less like a map than
the MapCSS renderings in Potlatch and JOSM do. It's no
On 11/14/2012 05:34 PM, Michal Migurski wrote:
Why Trac has nowhere near such an effect I couldn't say but it is
just the truth that once you put something on Github, people are
*much* more likely to contribute.
[citation needed]
My statement was based on my own experience with open source
Le mercredi 14 novembre 2012 17:34:17, Eugene Alvin Villar a écrit :
Actually we do, and that's the data layer. Unfortunately, I think there's a
perception that the data layer doesn't provide the gratification that
mappers want. Or maybe we just need to highlight this layer more.
IMHO Your
Lennard l...@xs4all.nl wrote:
This requires a reload of the database to at least get
public_transport=* in.
To get a little bit more flexibility which such stuff we now use hstore and
views on the german-style tileserver.
The overhead is acceptable when using --hstore-match-only
Our views
On 14/11/12 17:53, Paweł Paprota wrote:
I cannot be bothered to find some hard evidence that Github makes
people much likely to contribute though, it's just a fact. :-)
Thats not the problem, people being likely to contribute! It's
maintenance. Stop this github makes everything better insanity,
Hi all,
I'd like to find out what the current status of the Mapnik stylesheets
for www.osm.org is. The most recent changes are from June 2012 [1], and
the number of open tickets in TRAC is 400 [2].
Who is responsible for incorporating changes? Is some help needed? How
are those changes
On 11/13/2012 03:48 PM, Simon Legner wrote:
Hi all,
I'd like to find out what the current status of the Mapnik stylesheets
for www.osm.org is. The most recent changes are from June 2012 [1], and
the number of open tickets in TRAC is 400 [2].
Indeed... I looked at the same thing 2-3 weeks ago
On 13-11-2012 15:48, Simon Legner wrote:
I'd like to find out what the current status of the Mapnik stylesheets
for www.osm.org is. The most recent changes are from June 2012 [1], and
the number of open tickets in TRAC is 400 [2].
Currently it's in a bit of a holding pattern. Personally, I'm
On 13-11-2012 15:58, Paweł Paprota wrote:
I'd say the priority should be bringing the main style onto the pretty
side...
If you take a look at the amount of open tickets, pretty clashes
heavily with I want $feature rendered, where $feature ranges from
'yes, probably, sounds sane enough' to
On 11/13/2012 09:46 PM, Lennard wrote:
On 13-11-2012 15:58, Paweł Paprota wrote:
I'd say the priority should be bringing the main style onto the
pretty side...
If you take a look at the amount of open tickets, pretty clashes
heavily with I want $feature rendered, where $feature ranges from
On 11/13/2012 11:13 PM, Derick Rethans wrote:
I would rather see as much useful things rendered that make sense for
*mappers*. Pretty tiles should also be made, but as far as I know, the
default style that is on openstreetmap.org is for *us* - the people who
add data.
Well, that's the usual
Le mardi 13 novembre 2012 23:25:44, Paweł Paprota a écrit :
On 11/13/2012 11:13 PM, Derick Rethans wrote:
I would rather see as much useful things rendered that make sense for
*mappers*. Pretty tiles should also be made, but as far as I know, the
default style that is on openstreetmap.org
On 11/13/2012 11:32 PM, sly (sylvain letuffe) wrote:
I share Derick's view, but maybe what we need is someone to just do it and
split the problem in two maps.
http://wiki.openstreetmap.org/wiki/Contributors_functionalities_wishlist#Backgound_map_with_the_most_possible_objects
Sure,
The biggest problem with the Mapnik stylesheet right now is that it's in
SVN. Not the technology, but the fact that this gives people without commit
access to that repository no clear way to contribute. There is no way to
'just do it' until the style is actually maintained in GitHub, actually
On 11/13/2012 11:23 PM, Tom MacWright wrote:
Ideally we can move the osm stylesheet to github, close non-actionable
tickets and address those that can be addressed.
I pretty much agree here. 400 tickets could turns into 50 pull requests
merged in a week, just with a few clicks from the
On 11/13/2012 09:45 PM, Lennard wrote:
This requires a reload of the database to at least get
public_transport=* in.
Handling role values, like stop, is not supported yet.
Could some columns be added live instead of a complete reload?
___
dev
Hi!
On 13/11/12 23:36, Tom MacWright wrote:
The biggest problem with the Mapnik stylesheet right now is that it's in
SVN. Not the technology, but the fact that this gives people without
commit access to that repository no clear way to contribute. There is no
way to 'just do it' until the style
On 13/11/12 22:45, Simon Legner wrote:
On 13/11/12 23:36, Tom MacWright wrote:
The biggest problem with the Mapnik stylesheet right now is that it's in
SVN. Not the technology, but the fact that this gives people without
commit access to that repository no clear way to contribute. There is no
On 13/11/12 22:42, yvecai wrote:
On 11/13/2012 11:23 PM, Tom MacWright wrote:
Ideally we can move the osm stylesheet to github, close non-actionable
tickets and address those that can be addressed.
I pretty much agree here. 400 tickets could turns into 50 pull requests
merged in a week, just
On 13/11/12 22:43, yvecai wrote:
On 11/13/2012 09:45 PM, Lennard wrote:
This requires a reload of the database to at least get
public_transport=* in.
Handling role values, like stop, is not supported yet.
Could some columns be added live instead of a complete reload?
We plan to reload the
Btw … is someone trying to collect some mirrors? :-D
https://github.com/openstreetmap/mapnik-stylesheets/tree/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/mirror/master
___
dev mailing list
dev@openstreetmap.org
2012/11/13 Tom Hughes t...@compton.nu:
Well maybe not... We don't actually want every random POI icon that a user
submits to be merged willy nilly - we want somebody to apply some
cartographic thought when choosing what to merge.
That is an important point. Developing a map style is not
On Nov 13, 2012, at 12:45 PM, Lennard wrote:
On 13-11-2012 15:48, Simon Legner wrote:
I'd like to find out what the current status of the Mapnik stylesheets
for www.osm.org is. The most recent changes are from June 2012 [1], and
the number of open tickets in TRAC is 400 [2].
Currently
On Tue, Nov 13, 2012 at 10:36 PM, Tom MacWright t...@macwright.org wrote:
There is no way to 'just do it' until the style ... has active
maintainers. Until then we're just talking.
seems like this might be the major hurdle - there do seem to be people
willing to contribute on this thread, but
Matt Amos wrote
i'd sound a note of caution about having separate clean and detailed
styles. we sort-of did that before with mapnik and osmarender respectively
and... well, we don't have osmarender any more.
I doubt that having to maintain two styles was what killed osmarender. It
was a
Dane Springmeyer wrote
I'm sorry about not providing Windows binaries yet for Mapnik 2.x. The
holdup is that I have a dev environment working that is running Visual
Studio 2010, and I need to get a parallel setup running Visual Studio 2008
for support compiling the python bindings. Its a silly
Tom MacWright wrote
The biggest problem with the Mapnik stylesheet right now is that it's in
SVN. Not the technology, but the fact that this gives people without
commit
access to that repository no clear way to contribute. There is no way to
'just do it' until the style is actually maintained
44 matches
Mail list logo
