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
Building modules that each deal with a specific type of file could really help this library be more approachable and maintainable. I'm imagining modules which all have methods like getProjection and getExtent, and a single digest() function that chooses the right module + strings together method calls to build a metadata object.
Most of the functions in the current implementation are like getProjection and while sounding generic, contain logic that branches based on filetype anyways.
The text was updated successfully, but these errors were encountered:
rclark
changed the title
[bluesky] Refactor into modules for each type of dataset
[bluesky?] Refactor into modules for each type of dataset
Jan 22, 2015
Building modules that each deal with a specific type of file could really help this library be more approachable and maintainable. I'm imagining modules which all have methods like
getProjection
andgetExtent
, and a singledigest()
function that chooses the right module + strings together method calls to build a metadata object.Most of the functions in the current implementation are like getProjection and while sounding generic, contain logic that branches based on filetype anyways.
Implementing this would make adding new features like different mapnik datasource types for topojson and geojson much more straightforward to implement. For example the mess I made in #67.
cc @GretaCB
The text was updated successfully, but these errors were encountered: