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
{{ message }}
This repository has been archived by the owner on Sep 17, 2021. It is now read-only.
Unfortunately, it's written in JavaScript, so we have to either include a Node environment (Brewfile, buildpack, etc.) or port it to Ruby, then include whatever in the build system just like the GeoJSON export.
Node environment.
Establishing a dependency on node.js and including it in our Heroku configuration is probably the quickest solution.
Add to Brewfile and setup instructions
Add Node.js buildpack to Heroku configuration
Integrate conversion script as a Jekyll plugin, just like for GeoJSON
Write conversion in Ruby
The program that does bi-directional conversion is only about 350 lines of JavaScript and has no external dependencies. This indicates that a direct port should be very easy. It could be done as a Ruby gem, too, and then we only need to manage the gem reference in our code.
Port conversion code to Ruby
Publish Gem
Include Gem in Gemfile
Integrate conversion code as a Jekyll plugin, just like for GeoJSON
The text was updated successfully, but these errors were encountered:
ArcGIS apparently cannot consume JSON directly. Fortunately, someone wrote a converter.
https://github.com/Esri/arcgis-to-geojson-utils
Unfortunately, it's written in JavaScript, so we have to either include a Node environment (Brewfile, buildpack, etc.) or port it to Ruby, then include whatever in the build system just like the GeoJSON export.
Node environment.
Establishing a dependency on node.js and including it in our Heroku configuration is probably the quickest solution.
Write conversion in Ruby
The program that does bi-directional conversion is only about 350 lines of JavaScript and has no external dependencies. This indicates that a direct port should be very easy. It could be done as a Ruby gem, too, and then we only need to manage the gem reference in our code.
The text was updated successfully, but these errors were encountered: