-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
POC of WMS (ArcGIS) Layer #991
Conversation
✅ Deploy Preview for veda-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Here are my thoughts, curious what @j08lue @smohiudd @anayeaye @slesaad think
|
@hanbyul-here can we also do a ImageServer collection, that way we'll be able to show support for two kind of arcgis servers - imageserver and mapserver. Here's a sample collection - https://dev.openveda.cloud/api/stac/collections/POWER_901_MONTHLY_RADIATION_UTC (this is the same kind of dataset that I demoed in my PR) We're also working on refining the time-series for imageserver - will deploy this soon - so we can also add that to the demo
jut FYI that not all 'arc' layers are like this, the imageserver collection will have a timestamp |
Here's the statistics proxy for ImageServer - https://hh76k5rqdh.execute-api.us-west-2.amazonaws.com/dev/docs Use the also here are some other arcgis collections to play around with: |
Are you sure At least the ArcGIS web viewer (wait for it to load...) shows selectable times in the full range between 2001 and 2024: As it switches through time layers, it makes requests against the ArcGIS MapServer API like this one: Sadly, the ArcGIS WMS (Btw, they seem to have |
+1 for @slesaad's recommendation to include both a MapServer and an ImageServer layer in the POC. |
@j08lue you're right Edit: actually looks like there is the time step info in the link <Dimension name="time" units="ISO8601" current="1">2001-01-02T00:00:00.000Z/2024-06-03T00:00:00.000Z/P7D</Dimension> P7D - 7 days! |
7c6640c
to
55405bc
Compare
Oh, I didn't know that different data types are integrated from the ArcGIS server. I am a bit confused if they need to be handled differently or not. From the response of the stac endpoint and the fact that The dashboard can 'guess' the timestamp when the dataset is marked as |
How many languages do you speak, @slesaad?! |
There is improvement that should be made especially regarding timestamp, but for POC, would this be enough? @slesaad ? |
To detail the improvement we can make in the future re: timestamps
|
looks great @hanbyul-here !! thank you so much for working on this. |
1b63119
to
42bb3cc
Compare
Related Ticket: #943
Description of Changes
Add 'arc' type layer for both /explore page and /exploration (new E&A)
Notes & Questions About Changes
Validation / Testing