Skip to main content
Open

Add 'Historic moment' to ESRI Arcgis Portal reader

Related products:Integrations
siennaatsafe
warrendev
tcrossman
mgg_beca
martinkoch
+3
  • siennaatsafe
    siennaatsafe
  • warrendev
    warrendev
  • tcrossman
    tcrossman
  • mgg_beca
    mgg_beca
  • martinkoch
    martinkoch
  • mpsims
    mpsims
  • mes
  • rchoucroun
    rchoucroun

martinkoch
Supporter

Hello all,

The ESRI ArcGIS Portal API for featureservices supports query-ing a specific HistoricMoment (see the HistoricMoment parameter in the documentation) of course when History is enabled in the service.

Currently the Portal reader does support Branch versioning, but not this HistoricMoment capabilities.

To me it would be a great upgrade to the reader. The ArcGIS SDE reader has had this for decades, and as this is fading out of use in favor of the new service based architecture of ESRI products, the need arises more and more in my workflows.

I've been able to pull it of with a custom transformer consisting of a motherload of HTTPCallers and JSON related transformers. That also solves my disable SSL verification problem, but is not as elegant and maintainable as a proper Safe supported native reader.

2 replies

rchoucroun
Contributor
Forum|alt.badge.img+11
  • Contributor
  • April 11, 2023

@martinkoch​ I don't suppose you would share your Custom Transformer solution for this? I need this functionality pretty badly.

 

Thanks.


martinkoch
Supporter
Forum|alt.badge.img+18
  • Author
  • Supporter
  • April 14, 2023

Hello @rchoucroun​ ,

 

I made a custom transformer to query historic moments, at a customer. It works well for the intended application. For using it in a generic situation somewhere else, it would need some refactoring and quality overhaul.

 

I am not sure how the customer would feel about me sharing work I developed for them, they paying me for that. Sharing it would put the burden on me of maintaining the code. And I do not have constant access to an ESRI Enterprise installation with all required bells and whistles to do so.

 

Use the ESRI documentation I linked to, think 'always POST even if your REST intuition says GET'. Expect http-response '200' with a json saying something in the line 'error = 400', yes it is that bad.... but using an ESRI webconnection as authentication in a HTTP-caller works!!

 

Getting the time in EPOG is 'DateTimeConverter' output-format %Es and multiply that by 1000 for microseconds.

 

And yes, you go through some JSON-from-hell a couple if times but probably end up with something which runs in your application till Safe fixes this.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings