@garrettdashnelson per our chat on Teams, i'm suggesting we split the volume-extents file into separate GeoJSONs like so:
- in this repository, make >
atlascope > atlascope-boston > volume-extents
- in
volume-extents, explode boston-volume-extents into N files, one for each feature
- each file has the Atlascope ARK identifier (e.g.
amdt8y9of) as a file name
this does double duty of 1) making it easier to see diffs on a volume-by-volume basis for e.g. troubleshooting, and 2) could be automated more easily on my end, removing the cumbersome step of manually editing a large GeoJSON file each time a new layer is added to production.
we'll need to update this action to reassemble those into different files. i'm happy to take point on this, and i opened the issue here because i think we should not have to refactor any code in Atlascope to accomplish this
@garrettdashnelson per our chat on Teams, i'm suggesting we split the
volume-extentsfile into separate GeoJSONs like so:atlascope>atlascope-boston>volume-extentsvolume-extents, explodeboston-volume-extentsinto N files, one for each featureamdt8y9of) as a file namethis does double duty of 1) making it easier to see diffs on a volume-by-volume basis for e.g. troubleshooting, and 2) could be automated more easily on my end, removing the cumbersome step of manually editing a large GeoJSON file each time a new layer is added to production.
we'll need to update this action to reassemble those into different files. i'm happy to take point on this, and i opened the issue here because i think we should not have to refactor any code in Atlascope to accomplish this