On Friday 29 June 2018, Frederik Ramm wrote:
> [...]
>
> So the ease of participating or customising has more or less already
> gone down the drain; what's still good about OSM Carto is that at
> least you can easily install it as-is on your own infrastructure (I
> regularly do that for business
sent from a phone
> On 29. Jun 2018, at 11:39, Frederik Ramm wrote:
>
> I would love it if OSM Carto
> could be split into a "bread and butter" style that is easy to work
> with, easy on the eye and easy to render, and a "cartography
> navel-gazing" add-on where we show off how we can render
W dniu 29.06.2018 o 11:06, Christoph Hormann pisze:
> I did not make any assumptions on avant-garde being a positive thing
> here. In fact for a long time i have clearly said that i think that
> OSM map design should become more pluralistic.
It is now and it does not go away, so I still see
W dniu 29.06.2018 o 12:57, James pisze:
> But they say CartoCSS is dead, what is the intended replacement(if
> it's dead it's because there's a newer better thing?)? just a data
> structure that contains data/styling?
Being "dead" means it's no longer in development, but it's still
perfectly
W dniu 29.06.2018 o 13:02, Christoph Hormann pisze:
> But the surface rendering from Lucas is something you could fairly well
> re-integrate into a reworked road rendering framework afterwards - and
> this is probably also the way i would approach it.
> How to implement something like that in
W dniu 29.06.2018 o 11:39, Frederik Ramm pisze:
> Hi,
>
>without going into the finer details, I'd like to offer an outsider's
> view of OSM Carto development.
Thanks, Frederik! I lack such insights (we know our ideas inside the
team quite well), so I appreciate your comments a lot.
I would
On Friday 29 June 2018, Paul Norman wrote:
>
> I had a go at fixing the roads code with
> https://github.com/gravitystorm/openstreetmap-carto/pull/2869, but
> didn't have free time. Based on that work, I'd estimate that the
> roads code is twice the size and complexity of what it needs to be.
>
>
But they say CartoCSS is dead, what is the intended replacement(if it's
dead it's because there's a newer better thing?)? just a data structure
that contains data/styling?
On Fri, Jun 29, 2018, 6:49 AM Paul Norman, wrote:
> On 2018-06-29 2:48 AM, James wrote:
> > So what is intended to replace
Rendering (unpaved) surface is a real need. Judging from the map notes
users don't get the distinction and conflate track symbol with unpaved.
Mappers do it too.
In Poland (and maybe somewhere else) wrongly tagged tracks (what should be
residential+unpaved) are a big problem, almost intractable
On 2018-06-29 2:48 AM, James wrote:
So what is intended to replace CartoCSS? Vector tiles?
CartoCSS is a styling language, vector tiles is an architecture choice.
You can use CartoCSS with vector tiles, as the Cycle Map and Transport
Map layers on osm.org do, or you can use CartoCSS with
I've been involved in OpenStreetMap Carto less and less, partially
because I work with CartoCSS setups enough for work.
On 2018-06-29 2:06 AM, Christoph Hormann wrote:
And you are wrong that "nobody seems to be even noticing" complexity of
the roads code. At least Lucas, Paul and me have a
So what is intended to replace CartoCSS? Vector tiles?
On Fri, Jun 29, 2018, 5:42 AM Frederik Ramm, wrote:
> Hi,
>
>without going into the finer details, I'd like to offer an outsider's
> view of OSM Carto development.
>
> When Andy first created OSM Carto, he set out a road map that has
Hi,
without going into the finer details, I'd like to offer an outsider's
view of OSM Carto development.
When Andy first created OSM Carto, he set out a road map that has long
been superseded but thanks to version control we can still look at it:
On Friday 29 June 2018, Daniel Koc4� wrote:
> > All in all this is a good example for OSM-Carto being at a
> > crossroads (and having been for quite some time) between staying
> > avant-garde and pushing the boundaries of cartographic design and
> > technology or being satisfied with shuffling the
(Taken from dev list, because this is wider problem.)
W dniu 23.06.2018 o 10:55, Christoph Hormann pisze:
> All in all this is a good example for OSM-Carto being at a crossroads
> (and having been for quite some time) between staying avant-garde and
> pushing the boundaries of cartographic
15 matches
Mail list logo
