Would the team be open to adding a flag or options argument to the decode function to parameterize that x, y encoding for the coordinate pairs per the GeoJSON spec is needed and not the default y, x encoding. I can see there are low level bindings in various languages implemented for this and understand it's not a small task, but I think it would be quite helpful for many use cases. If you think that sort of function signature would work for decode or would consider a separate decodeToGeoJson function, I'd be happy to PR it for the JavaScript implementation.