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
Raster app changes #26
Comments
I got #1 done and pushed to production. I tested running the pallet manually this afternoon to verify. |
stdavis
added a commit
that referenced
this issue
Mar 8, 2018
stdavis
added a commit
that referenced
this issue
Mar 8, 2018
Hey @rkelson: I've got the checked off items pushed to http://test.mapserv.utah.gov/raster. Would you mind taking a look and letting me know what needs to be fixed or if we are good to push to production? I've also created separate issues for the items under "Futures". They are #27 & #28 respectively. |
stdavis
added a commit
that referenced
this issue
Mar 15, 2018
stdavis
added a commit
that referenced
this issue
Mar 15, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
INDICES.DEM_Extents
toINDICES.USGS_DEM_Extents
INDICES.AutoCorrelated_DEM_Extents
INDICES.USGS_DEM_Extents
The new categories for raster should be:
Lidar_Extents has a field
FTP_Path
that shows up in theMore Info
panel. This field is used for project based metadata download links.FTP_Path
contains 'https://storage.googleapis.com/' do not populateFTP_Path
with the link in the `More Info panel.Futures
It would be cool if each had an alt tag / title text (steve suggested the acronym tag) to explain what they are
I changed my mind about adding the new scanned extents to the current Aerial Photography extents; it would return too many results. I propose making a new category named something like
Historical Scanned Aerial Photography
.The text was updated successfully, but these errors were encountered: