You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could adapt mapbuffer to add a content type header field. For example:
content_type char(5) = 'draco'
This would allow for automatic decoder selection. On the other hand, we could allow for arbitrary compression types and simply pass through unsupported ones. That would require only a code change and not a format change.
compression_type (4) = "drco"
However, the above change would be generally useful. For example gzip encoded json or xml could be represented.
The text was updated successfully, but these errors were encountered:
We could adapt mapbuffer to add a content type header field. For example:
content_type char(5) = 'draco'
This would allow for automatic decoder selection. On the other hand, we could allow for arbitrary compression types and simply pass through unsupported ones. That would require only a code change and not a format change.
compression_type (4) = "drco"
However, the above change would be generally useful. For example gzip encoded json or xml could be represented.
The text was updated successfully, but these errors were encountered: