Open ynunokawa opened 8 years ago
just to clarify, it sounds like you are proposing:
L.esri.featureLayer
should accept either a GeoJSON feature collection or a url
in its constructor?drawingInfo
passed in the object constructor and skip fetching information about symbology from the service itself entirely?is that correct?
Yes, that's right.
esri-leaflet-renderers is able to interpret drawingInfo passed in the object constructor and skip fetching information about symbology from the service itself entirely?
I have updated to rewrite drawingInfo
from the service with original drawingInfo
in esri-leaflet-renderers and created PR. :octocat:
It use new drawingInfo
option of L.esri.FeatureLayer
as the below.
L.esri.featureLayer({
url: 'http://...',
drawingInfo: webmapJson.***.drawingInfo
});
Please check it out.
I think that feature layers to include a feature collection with
drawingInfo
should be rendered using Esri Leaflet Renderers in the issue #32 . The goal of this concept is that all feature layers use the same logic as Esri Leaflet Renderers to render.There are prospected requirements to perform it.
drawingInfo
FeatureCollection
using renderer modules of Esri Leaflet Renderers (for the present)