Prueba de la aplicación esriLeafletGeocoder

AntonioPavicevac-Ortiz

Mientras probaba mi aplicación así:<\/P>

 <\/P>

 <\/P>

 <\/P>

 <\/P>

esriLeafletGeocoder
  .reverseGeocode({
  apikey: process.env.ESRI_API_KEY,
})
.latlng([48.8583, 2.2945])
.run(function (error, results, response) {
  if (error) {
    console.log("error", error);
    return;
  }
console.log("results, response ", results, response);
});<\/code><\/pre>
 <\/P>
 <\/P>
 <\/P>
 <\/P>
De repente comencé a recibir el siguiente error:<\/P>

  error {code: 403, subcode: 2, message: "User does not have permissions to access 'world.geocodeserver'.", details: Array(0)}<\/P>
<\/BLOCKQUOTE>
Lo que me llevó a revisar el sitio web de ArcGIS Developers, estoy en el nivel free free, pero ¿qué pasa si estás probando algo con la misma lat\/lng?<\/P>
¿Existe una mejor práctica que debería seguir para almacenar en caché este resultado y no ser limitado por la tasa? <\/P>
 <\/P>

John-Foster

the first question that comes up is what type of ArcGIS account are you using to access the geocode service? See https://developers.arcgis.com/documentation/mapping-apis-and-services/get-started/. If you are using an ArcGIS Developer account with an API key then check the API key scope to make sure geocoding (not stored or stored depending how you are using and paying for the service) is set. If you are using an ArcGIS Online account then make sure the user the key is assigned to also has the geocoding privilege (the administration can disable this). Next, verify you have free tier remaining (if using not stored service) or Pay as you go turned on.

Regarding caching, if you are using geocode (not stored) then caching the geocode results is against the Terms of Use. But if you are using the geocode service with the for storage parameter set then you may cache those results.