Résultats de la recherche

Rechercher dans les contenus ayant un titre ou un résumé disponibles dans les langues sélectionnées

Résultats de la recherche

  1. Question de FAQ collaborative Limitation usage webservices altimétrique

    Bonjour, Je découvre également cette limitation sur les usages ; dommage de ne pas avoir prévenu les utilisateurs par mail, cela aurait évité de récupérer des erreurs 429 sur des outils en production... Concernant le webservice altimétrique, la limitation à 5 requêtes par seconde n'est vraiment pas généreuse... Le service est limité à 5000 points par requête, mais l'IGN conseillait de ne pas en mettre autant (https://www.developpez.net/forums/d2160748/applications/sig-systeme-d-information-geographique/ign-api-geoportail/geoplateforme-calcul-altimetrie-defaillant/). J'avais donc préféré avoir un nombre important de petites requêtes, ce qui n'est actuellement plus possible. Je viens de basculer sur des requêtes de 5000 points ; cela permet de ne plus dépasser la limite imposée, mais je ne suis pas certain que ce soit bénéfique pour les performance de l'infrastructure (ce qui est l'objectif affiché des limites mises en place). Bon après-midi, Jean-Philippe
  2. Question de FAQ collaborative Adaptation du service altimétrie

    Bonjour à tous, Le service altimétrie est utilisé dans un outil interne de l'entreprise, il semblerait que la bascule entraîne une adaptation à prévoir car le format de l'extension OpenLayer utilisée pour définir le profil altimétrique d’un tracé à l’aide du service d’altimétrie de la plateforme Géoportail soit du json (alors qu'elle était en xml avant). Est-ce qu'un changement est à prévoir concernant les extensions OpenLayer notamment celle du tracé du profil altimétrique ? Excellente fin de journée,
  3. Message de forum Service altimétrique : délai de réponse

    Bonjour, Je viens à l'instant de faire un comparatif de requêtes GET altimétriques sur l'ancienne infrastructure et sur la géoplateforme pour les mêmes coordonnées géographiques (162 points). J'ai exécuté 10 fois la requête pour chaque plateforme. Géoplateforme Temps de réponse moyen : 1,153 s - Plus lent : 2,57 s - Plus rapide : 584 ms Ancienne infrastructure Temps de réponse moyen : 242 ms - Plus lent : 487 ms - Plus rapide : 144 ms La géoplateforme est donc en moyenne quasiment 5 fois plus lente que l'ancienne infrastructure pour cette requête. Y-a-til des tests en cours qui peuvent expliquer ces performances dégradées ? Cela va-t-il s'améliorer ? Voici la requête effectuée : https://data.geopf.fr/altimetrie/1.0/calcul/alti/rest/elevation.json?lon=5.559,5.5585,5.558,5.558,5.5583,5.5586,5.5586,5.5588,5.5589,5.5592,5.5597,5.5604,5.5604,5.5605,5.5605,5.5607,5.5608,5.5609,5.5609,5.561,5.5611,5.5611,5.5612,5.5615,5.5618,5.562,5.5624,5.5626,5.5628,5.563,5.5633,5.5636,5.5638,5.564,5.5642,5.5643,5.5643,5.5644,5.5646,5.5648,5.5648,5.565,5.5653,5.5655,5.5657,5.566,5.5662,5.5665,5.5667,5.5669,5.5671,5.5672,5.5674,5.5676,5.5678,5.568,5.5681,5.5683,5.5685,5.5686,5.5688,5.5688,5.5688,5.5689,5.569,5.5691,5.5693,5.5694,5.5695,5.5696,5.5696,5.5697,5.5697,5.5698,5.5698,5.5699,5.5699,5.5706,5.5706,5.5706,5.5707,5.5707,5.5707,5.5708,5.5708,5.5707,5.5707,5.5707,5.5707,5.5707,5.5707,5.5706,5.5705,5.5705,5.5705,5.5705,5.5706,5.5706,5.571,5.571,5.571,5.5711,5.571,5.5709,5.5707,5.5706,5.5704,5.5703,5.5699,5.5696,5.5694,5.5692,5.5691,5.569,5.5689,5.569,5.5693,5.5695,5.5698,5.5699,5.5699,5.5699,5.5698,5.5697,5.5695,5.5692,5.5689,5.5688,5.5687,5.5685,5.5682,5.568,5.568,5.5679,5.5679,5.5678,5.5678,5.5678,5.5677,5.5676,5.5675,5.5674,5.5673,5.5674,5.5677,5.568,5.5682,5.5683,5.5684,5.5684,5.5685,5.5685,5.5685,5.5684,5.5684,5.5684,5.5685,5.5685,5.5685,5.5686,5.5687,5.5688,5.5688&lat=45.4125,45.4123,45.4121,45.4121,45.4118,45.4115,45.4115,45.4113,45.4112,45.4109,45.4103,45.4096,45.4096,45.4095,45.4095,45.4096,45.4096,45.4096,45.4096,45.4095,45.4095,45.4095,45.4095,45.4096,45.4097,45.4098,45.4099,45.41,45.4101,45.4103,45.4105,45.4106,45.4107,45.4108,45.4109,45.4109,45.411,45.411,45.4112,45.4113,45.4113,45.4113,45.4113,45.4113,45.4114,45.4115,45.4115,45.4116,45.4116,45.4117,45.4117,45.4117,45.4118,45.4118,45.4119,45.4119,45.4119,45.4119,45.4119,45.4119,45.412,45.4119,45.4118,45.4115,45.4111,45.4108,45.4105,45.4103,45.41,45.4099,45.4097,45.4096,45.4095,45.4094,45.4093,45.4091,45.409,45.4079,45.4078,45.4077,45.4074,45.4073,45.4071,45.407,45.407,45.4069,45.4069,45.4068,45.4068,45.4068,45.4068,45.4068,45.4067,45.4067,45.4064,45.4064,45.4064,45.4064,45.4064,45.4064,45.4064,45.4063,45.4063,45.4062,45.4062,45.4061,45.4061,45.4061,45.4061,45.4062,45.4062,45.4061,45.4061,45.4061,45.406,45.406,45.4057,45.4055,45.4052,45.4052,45.4051,45.4051,45.405,45.4049,45.4047,45.4045,45.4042,45.404,45.4039,45.4036,45.4032,45.403,45.4029,45.4028,45.4027,45.4027,45.4027,45.4026,45.4024,45.4024,45.4023,45.4023,45.4022,45.402,45.4017,45.4013,45.4009,45.4008,45.4007,45.4006,45.4005,45.4004,45.4003,45.4001,45.4,45.4,45.3999,45.3998,45.3997,45.3995,45.3992,45.3991,45.399&zonly=true&indent=false&resource=ign_rge_alti_wld&delimiter=, Merci d'avance pour votre retour, Jean-Philippe