Let the user set the resolution [19]

AbelVM commented 8 years ago

"resolution" parameter:

positive values are resolution
negative values imply max processing time, and the optimal resolution is guessed
[x] All declared geometries are geometry(Geometry, 4326) for general geoms, or geometry(Point, 4326)
[x] Existing functions in crankshaft python library called from the extension are kept at least from version N to version N+1 (to avoid breakage during upgrades).
[x] Docs for public-facing functions are written
[x] New functions follow the naming conventions: CDB_NameOfFunction. Where internal functions begin with an underscore _.
[x] If appropriate, new functions accepts an arbitrary query as an input (see Crankshaft Issue #6 for more information)

iriberri commented 8 years ago

Hey @AbelVM, just for me to have an idea about how important is this PR. Is it blocking something? Are you working on something else that we could combine in a release with these changes?

AbelVM commented 8 years ago

Not right now. This change comes from a chat with @rochoa and it's needed to be coherent with the linked PR in Camshaft ( https://github.com/CartoDB/camshaft/pull/186 ).

AbelVM commented 7 years ago

:clap:

CartoDB / crankshaft

Let the user set the resolution [19] #120