Rh/arcgis map

[laholstege]

finally in a readable/workable state! still some bugs and might not be the optimal way of doing things. you can see the map here on the quote page where you're confirming field locations. i've been looking at this: https://localhost:5001/caes/quote/create/104

there's a map using their built in edit widget:

and one that adds features with react state. we could probably combine this with the edit widget or make our own custom interface. currently i just have a button that adds a predetermined polygon and one that deletes the most recent graphic

also was messing with using their sketch widget and their watch() util but that isn't functional.

pretty interesting, but we should talk about the data storage and what we want to host on ArcGIS (and how). currently we store geometry as a Location column in the db.

currently, here is what i have hosted for this:

Harvest Map which contains our basemap of satellite imagery. i don't think we have to specifically add the osm baselayer, but in the toggle we also use an OSM basemap.

Harvest Fields Feature Layer where the actual field shapes/graphics are stored.

Harvest Insight haven't looked into Insights very much or how we would be able to interface it, but pretty cool. i found a map on UCD's ArcGIS Online directory that has Yolo County crop maps and i cross referenced where our field locations are in the Harvest Fields Feature Layer ☝️ and it shows what crop data they have within those locations. that's the workbook but you can also export a report. though you have to manually refresh the data

i can't link to it but i also have an API key generated that we could use to access/query if we need that. seems like we can use the REST API to do spatial analysis

also, this is all hosted on my personal account and obviously we need a better system than that.

my opinion is that this is pretty cool and has a lot more potential than using Leaflet. my biggest questions are around how we want to store/interface with the GIS data, and what access users would have to those layers. also not sure about the licensing/use for GIS services

[srkirkland]

Ok -- so my thoughts:

• Looks awesome, I like this approach better than mapbox/leaflet
• Would prefer we keep geoJSON of our fields in the db and dynamically generate the layer, especially at our scale
• I actually like their editor for creating features. We'd have to handle the onCreate callback and add to our dynamic GeoJSON.
• Not sure the best way to edit features. Maybe we can use the built in edit, but wasn't clear from this example how to be precise about it.
• I think we if avoid the feature layer, hosting will be simple and we might not even care much/at all about permissions, which would be nice

[laholstege]

going to add a geoJSON layer next and get the EditWidget to work with it