Conversation
Now it is possible to probe ArcGIS Server MapServices
There was a problem hiding this comment.
Thanks, but before merging this needs to be addressed/added:
- major:
esrims.pyis mostly identical to the existingesrifs.py. Apart from naming I see only two differences in the Probe execution:"OBJECTID"(MS) vs'objectIdFieldName'(FS) andif layer['subLayerIds'] is None:(MS). For maintenance it is better to merge all common code into a common baseclass likeESRIDrilldownand specialize subclassesESRIMSDrilldownandESRIFSDrilldown. I am not familiar with ESRI MS (though I wrote the FS Probe) but would expect to get actual raster maps, test for image content etc? So for example renameesrifs.pytoesri.pyand have all code (Basclass and two subclasses) in a single file. For example at some point the Authentication may need to be improved. - add tests: basically only need to add to tests/data/fixtures.json (look for
ESRI:FShow that is done). - add documentation in
docs/plugins.rst(look forESRI:FS) - add
ESRI:MSto check in GeoHealthCheck/models.py line 433 - add
ESRI:MSto check in GeoHealthCheck/healthcheck.py line 246
Maybe some other places, best is to search for 'ESRI' or 'ESRI:FS' in source tree.
Thanks for patience!
…ed esri The complete URL of the Feature- of MapService is the input for the probe. Based on the last part of the url (FeatureServer or MapServer) the code uses another json field to get the identityfield. A drilldown test is niet possible in case of a query test because the url contains the number of the layer to test. Due to this the drilldown test gives an error.
|
I have changed the code and created an new way to test Feature- or MapServices based on the complete url of a service. I added this change in my repository. Can you have a look at it if it is OK now? |
|
Hi @LuukS I'm seeing that you are assuming in This is not always the case and GeoHealthCheck.plugins.probe.esrims.ESRIMSDrilldown fails when Is it possible to check the layer fields, search for Thanks! |
|
I quickly glanced through the changes, but am a bit confused: I see the resource type changed from |
|
I am confused as well. I changed the code and pushed it to my GitHub account. But I don’t see the changes in my code and also not in my pushed repo. Something went wrong. I have to find out what that was..
You’re right. I changed the ESRI:FS and created a new ESRI type. This supports both Feature- and Mapservice. I can add the ESRI:FS again so people can still use that one. With the new version I created you can use either Feature- or MapServices.
… Op 17 aug. 2023, om 15:46 heeft Just van den Broecke ***@***.***> het volgende geschreven:
I quickly glanced through the changes, but am a bit confused: I see the resource type changed from ESRI:FS to ESRI.
This will affect existing installations. My idea (see above) is to keep ESRI:FS and add ESRI:MS. But that the implementation uses a common baseclass. But I still see the full file esrims.py. Nowhere do I see the class GeoHealthCheck.plugins.probe.esri.ESRIDrilldown while it is refered in config_main.yml.
—
Reply to this email directly, view it on GitHub <#454 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKBZ6DHQDNOUTGDSDRKEZDXVYODPANCNFSM6AAAAAA2N2DCDM>.
You are receiving this because you were mentioned.
|
|
Any way you/we can progress this @LuukS ? |
…The esri probe was deleted.
…I:FS) and the Mapserver (ESRI:MS)
I changed to code in the latest commit to do this. |
Now it is possible to probe ArcGIS Server MapServices