Skip to content
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.

Add support for "mapnik-geometry-type" in filters #207

Closed
wants to merge 1 commit into from

Conversation

strk
Copy link
Contributor

@strk strk commented Nov 2, 2012

This is a simple implementation of support for mapnik-geometry-type use in filters.
See #180

I'm probably missing something about the use of variables (ie: should we allow a variable to expand to "mapnik-gemetry-type" ? I suppose that part isn't implemented).

Also, this implementation doesn' t use any support of mapnik-reference

@strk
Copy link
Contributor Author

strk commented Nov 22, 2012

We've been using this in staging for these 3 weeks and it works fine. Anything I could do to help merging this in ?

@springmeyer
Copy link

I'd prefer to rename this in mapnik to something that will work long term rather than embed compatibility in the carto code. Ideally mapnik-reference could be used to declare the name of this magic word across mapnik versions (once/if we rename).

@strk
Copy link
Contributor Author

strk commented Feb 12, 2013

We're using mapnik-geometry-type in production on cartodb.com already, do you think it'll be feasible to have that kind of interface or what did you have in mind ?

@strk
Copy link
Contributor Author

strk commented Jun 12, 2013

any news about this ?

@springmeyer
Copy link

sorry, no news. lost track of this. Each time I have a moment to work on exposing it in mapnik-reference I see the need for other fixes. I'll put this back on my list though.

@tmcw
Copy link
Contributor

tmcw commented Jun 14, 2013

Isn't this patch just adding a shorthand of ["mapnik-geometry-type"=foo] for ["mapnik::geometry-type"=foo]?

@strk
Copy link
Contributor Author

strk commented Jun 14, 2013

So it looks, but the consequence is you can use mapnik-geometry-type with no quotes, as suggested by @artemp here: #180 (comment)

We've been using [mapnik-geometry-type=<num>] constructor for a long time now.

@tmcw
Copy link
Contributor

tmcw commented Jun 14, 2013

That ticket seems to think mapnik-geometry-type would be implemented in mapnik, not aliased in Carto, right?

@strk
Copy link
Contributor Author

strk commented Jun 14, 2013

I don't now if it'll ever be implemented in mapnik, given mapnik already exposes the pseudo-attribute mapnik::geometry_type -- it was you suggesting to support the mapnik-geometry-type naming (comment above artemp's). To me it sounds cleaner (for mapnik) to use the :: syntax

@strk
Copy link
Contributor Author

strk commented Jul 16, 2013

@springmeyer any chance to look at this ?

@springmeyer
Copy link

no chance yet, need some time to thing about the big picture of this.

@strk
Copy link
Contributor Author

strk commented Sep 11, 2013

Everyone happy about using "mapnik::geometry_type" ? We may decide to automatically convert our custom mapnik-geometry-type back to "mapnik::geometry_type" when upgrading to mapnik-2.2.x if that's the final decision...

@tmcw
Copy link
Contributor

tmcw commented Sep 17, 2013

Closing; everyone is on board for "mapnik::geometry_type"

@tmcw tmcw closed this Sep 17, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants