misaugstad
commented
3 years ago Oh, and this is a method that I see used a lot in open data portals! So it's clearly semi-standard when it comes to open geographic datasets.
Open misaugstad opened 3 years ago
misaugstad
commented
3 years ago Oh, and this is a method that I see used a lot in open data portals! So it's clearly semi-standard when it comes to open geographic datasets.
JeremyFreiburger
commented
1 month ago There is a standard to view REST geo-services data, often using ArcGIS software. Creating a URL that formats similar to the websites linked below. That can be viewed in the browser using ArcGIS.
https://tigerweb.geo.census.gov/arcgis/rest/services/TIGERweb https://newjersey.maps.arcgis.com/home/item.html?id=c29ab646471d440f83843b704e811207 https://maps.nj.gov/arcgis/rest/services/Elevation/NJ_10ft_DEM/ImageServer
JeremyFreiburger
commented
1 week ago Arcgis Api Map https://www.arcgis.com/home/webmap/viewer.html?featurecollection=https%3A%2F%2Fmaps.nj.gov%2Farcgis%2Frest%2Fservices%2FElevation%2FNJ_10ft_DEM%2FImageServer%3Ff%3Djson%26option%3Dfootprints&supportsProjection=true&supportsJSONP=true Similar structure to PS https://github.com/kawsar-hamid-git/play-scala-rest-api-example/blob/master/README.md
A common way to serve geographic info through an API is through the GeoServices REST Specification (originally made by Esri, but is now an open standard). This page gives a succinct description of what this means and what it would entail for us. It's essentially about responding to specific/standard API calls in a way that users will expect. Maybe when we look deeper into the specs, we'll realize that there are a lot of changes we need to make. But at first glance, it sounds like it wouldn't be too hard to fit what we currently have into the framework. And I think that JSON is an expected form of output, so that's easy :ok_hand: