Julio

Retry query on bad connection error

1

## Context Imports of osm planet can take hours or days and a single error can take down the import process. Something like the database not existing or open makes...

Support user defined precision of Decimal strings

1

Currently, `Decimal#to_s` is hardcoded to support 60 digits of precision. We should do something like (ruby)[https://ruby-doc.org/stdlib-2.2.0/libdoc/bigdecimal/rdoc/BigDecimal.html#method-i-to_s] which allows the user to pass a format string to the `to_s` method. #451...

Implement drop and take builtins

1

Per #1286 I can implement this for the Haskell, Rust, and Go implementations (although it might take a while)

List/drop causes exponentially sized normal form

5

Normalizing `List/drop` without a number results in an expression with exponential size relative to the input list. I have a [minimal demo in this gist](https://gist.github.com/ear7h/5257e0566ff77a5cdf25748fd9e560c3). Note that this this issue...

I would like to do something like: ```dhall let blogPost = [ XML/element = {name = "h1", attributes = [] : Attrs, content = [ XML/text "Blog Post!" ] ]...

Handling TOML timestamps

4

TOML has native support for [dates and times](https://toml.io/en/v1.0.0#offset-date-time) and I'm wondering how this should be handled in dhall. I can add to the [discussion standardizing date/times in dhall](https://github.com/dhall-lang/dhall-lang/issues/80), but perhaps...

Align types and values when formatting records

1

For example: ``` let TargetBase = { Type = { path : Optional Text , test : Optional Bool , bench : Optional Bool , doc : Optional Bool ,...

I think the following function is leaking file descriptors by not calling `Close` on the http request or opened file: https://github.com/go-spatial/tegola/blob/ac82d5ffccd23991381678cbf5e531fec6806896/config/config.go#L285-L320

Use slippy.Grid to support tiles in different projections systems

25

This issue is for a design of using the new [`slippy.Grid`](https://godoc.org/github.com/go-spatial/geom/slippy#Grid) in tegola, in order for it to output multiple projection systems. Implementation of this functionality would close #243, #267,...

This would make the interface more flexible. It is currently: https://github.com/go-spatial/tegola/blob/c6139463db3230ffe75ae2b3b8b3801167f1b6c7/provider/provider.go#L22-L28 It would be better as: ```go type Tiler interface { // TileFeature will stream decoded features to the callback...