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
This weekend I experimented with a way to look up place data and output it on a webmap. There's an open source/free web service called Leaflet.JS that helps wtih putting lightweight maps on websites (and it's used by TimeMapper that we explored in DIGIT 100).
Instead of feeding Leaflet from a Google Sheet, we can output place data from the Mitford Journal and Site Index using a data structure called geoJSON . I set up a simple web map on the Quark project this weekend just to make sure we know how it works (what structures the service expects, etc). Check it out + some documentation here: cbl5678/fluffyFishstick#1
In our case, we have some latitude and longitude coordinates coded in the si.xml. (I'm not sure I remember how many already have this code.) Where we don't we can try scraping the data the way we are with the Quark team code. @nhammer514@HadleighJae@josiahr21
The text was updated successfully, but these errors were encountered:
This weekend I experimented with a way to look up place data and output it on a webmap. There's an open source/free web service called Leaflet.JS that helps wtih putting lightweight maps on websites (and it's used by TimeMapper that we explored in DIGIT 100).
Instead of feeding Leaflet from a Google Sheet, we can output place data from the Mitford Journal and Site Index using a data structure called geoJSON . I set up a simple web map on the Quark project this weekend just to make sure we know how it works (what structures the service expects, etc). Check it out + some documentation here: cbl5678/fluffyFishstick#1
In our case, we have some latitude and longitude coordinates coded in the si.xml. (I'm not sure I remember how many already have this code.) Where we don't we can try scraping the data the way we are with the Quark team code.
@nhammer514 @HadleighJae @josiahr21
The text was updated successfully, but these errors were encountered: