Marc Mönneråt
Marc Mönneråt
@pauloamado Do we do anything before we ditch the shop?
Work is done, but we will never merge it because it will break things on the user side.
How this related to the new `layerDefs` options? (see http://api3.geo.admin.ch/services/sdiservices.html#identify-features)
@edigonzales A few more attributes [identify on ch.bfs.gebaeude_wohnungs_register]( https://api3.geo.admin.ch/rest/services/all/MapServer/identify?geometry=2600423.5,1199520.75&geometryFormat=geojson&geometryType=esriGeometryPoint&imageDisplay=1238,907,96&lang=fr&layers=all:ch.bfs.gebaeude_wohnungs_register&limit=10&mapExtent=2600112.1636720165,1199256.2686586403,2600731.1636720165,1199709.7686586403&returnGeometry=true&sr=2056&tolerance=10)
Do you mean the `search` service (http://api3.geo.admin.ch/services/sdiservices.html#search)? You have the `origin` attribute (`zipcode`, `gazeetter`, etc..) which gives you a hint about the attribution to set, far from ideal, I know....
@davidoesch So do we break the compatibility and return GeoJSON in a consistent way across all services (and ditch the useless ESRI JSON)?
@danduk82 Is it OK to give write access our repository to `requires.io`?
We already have `greenkeeper` in `mf-geoadmin3`
Or something like https://github.com/renovatebot/renovate (installed locally)
Yes, but what do you mean by aggregate ? On the client-side, aggreagate only means many layers used at different scale/resolution.