Load a Geojson file and XYZ tile server by URL

[JJediny]

Part question/feature request; we're using an application called MapWarper to crowd-source the georeferencing of past/present Federal projects - http://warp.nepanode.anl.gov. We're considering supporting our own deployment of geojson.io as a dynamical map digitizer/vectorizer and think the best way to support this is to keep it simple and use as much of the current workflow/features currently supported by Geojson.io naively. The approach we're considering is creating/loading a GeoJSON file (that we'd make available as a REST API for each entry using the generated bounding box as an initial FeatureCollection) and simultaneously to load the tile server for the rectified image. Ideally this would be supported as a dynamical URL that could parse, add, load the geojson file and XYZ tile service in GeoJSON.io. We have staff available to look into this but any tips or areas in the code anyone could point us to would be appreciated. See DOE-NEPA/mapwarper#17 for more info about the use case, cheers

[briandeanlee]

Following...

/blee/

On Mar 15, 2015, at 4:10 PM, John Jediny [email protected] wrote:

Part question/feature request; we're using an application called MapWarper to crowd-source the georeferencing of past/present Federal projects - http://warp.nepanode.anl.gov. We're considering supporting our own deployment of geojson.io as a dynamical map digitizer/vectorizer and think the best way to support this is to keep it simple and use as much of the current workflow/features currently supported by Geojson.io naively. The approach we're considering is creating/loading a GeoJSON file (that we'd make available as a REST API for each entry using the generated bounding box as an initial FeatureCollection) and simultaneously to load the tile server for the rectified image. Ideally this would be supported as a dynamical URL that could parse, add, load the geojson file and XYZ tile service in GeoJSON.io. We have staff available to look into this but any tips or areas in the code anyone could point us to would be appreciated. See < a href=" DOE-NEPA/mapwarper#17" class="issue-link" title="Integrate Geojson.io as a Vector Digitizer as a Map Tab or Export URL">DOE-NEPA/mapwarper#17 for more info about the use case, cheers

—
Reply to this email directly or view it on GitHub.

[tmcw]

Sounds good: custom raster tiles via URL have been a feature request for a while, and seem fine as long as the implementation is aware of possible XSS attack vectors, like adding images with javascript URLs.

Same with the idea of a REST API: the chore is mostly on the API design side here, because REST means nearly anything and geojson.io including 'one kind of rest api' really means that we'd need to specify (the first) geojson api endpoint spec.