locana-co / pgrestapi Goto Github PK

Offer Well Known Text as an output type for all spatial endpoints.

most of the dependencies are already installed for nodetiles and PGRestAPI, so they don't need to be installed again for the nodetiles-postgis module.

So people know how to use it.

Just reuse the WKT Preview view, but offer choice of formats.

When GP jobs pop off, there should be a common unique identifier that follows the job throughout its life cycle. This may involve the server writing out assets to disk (maybe a shapefile -> Mapnik -> output image), and status updates for long running jobs.

Is this being done by anyone yet?

Input Geometry may need to be changed from WKT to a JSON object with a WKT property and SRID property.

Use ogr2ogr to create shapefiles for download

...if this is the case, then some of the operations involving transforms will not function properly.

I'm seeing localhost:3000 instead of services.irras.in.
Oh. It's because node is actually running on port 3000, and IIS is forwarding requests from services.irras.in to it. So it's actually working as desired. But there should be some override in settings to use if you prefer to show a different host/port.

For point tables, allow for GeoRef ID creation for clustering support.

send a text or e-mail if stuff is flaky.

Have Dynamic legends as part of the whole deal.

That's for Todd.

Currently I need to upload data in the projection that I want the spatial output to be in. But it would be cool if I could upload a shapefile to Postgres in 'web mercator' but then request that the output json, esriJSON, or geoJSON to be in 'wgs 84' ... ya know?

Pass in X,Y, get the value of a raster cell

GeoJSON file is intermediate step to create TopoJSON files. Create them in a static /public/geojson/output folder that mirrors /public/topojson/output. Users can have access to both.

This is DBoy's idea.

Limit the initial list of all tables, with limit overrides and/or pagination

Should show you the results of your spatial queries, buffers, etc on a little map.

This could be a separate project.
But, rip out a bunch of .json files ahead of time.
If your client side app has a table that aggregates values by district, do it all on the server, then rip out static view files that already are in the correct format to be consumed and immediately displayed by the client.

This might mean ripping out a json file for a particluar district that has pivoted aggregated averages. There might also be a json file for the same district, but it's pre-formatted to be consumed by a d3 grouped bar chart.

It's like tile caching your map ahead of time. But we're kind of caching all of the different ways a client would want to consume a piece of data. Need to work out a way for a user to define the format/logic for this.

Think about it.

Dynamic images as GP result option

Use Italics or something.

For dynamic tiles

Let users query their tables like normal from the table_query REST endpoint. After their results come back, offer a button to click to convert their results to TopoJSON. That way, you can still narrow down your features with a where clause AND get TopoJSON.

After users enter inputs into UI form for REST queries, display how the same query can be requested with a GET request (in a div or panel in the UI).

Copy/Paste WKT into a form, see what it looks like.

And then get deleted. Add to settings.js the amount of time to live.

...there's now new stuff, with a more complex install.
Can we update the docs/OSX_Installation.md file with OSX Install notes?

do it.

Oh boy.

If I want to know all of the spatial tables I may do something like:
http://54.212.251.211/services/tables?f=json

If I want to know the columns/data types and supported operations for any individual rest resource I may do something like:
http://54.212.251.211/services/tables/nigeria_urbanareas?f=json

...to reduce the round trips to the DB.

Route that reads a text string, or converts object to string and then offers it back with the appropriate mime type so users can click to download files.

Don't let users name the file. Change text input to a static label that can be used to post in a form.

Clint wants to download GeoJSON files. No need for them to be generated every time if they're static. Also, no need to call to an API since you can just download them.

Only allow x number of services. Services will self terminate after a certain period, and will self terminate if not used within x number if seconds.

The Chubbs Spatial Server deployment instructions are now a bit vague. Update it especially to 1) include the nuances for deploying to AWS EC2 machines 2) On Windows, creating a windows service 3) On Linux, creating long-lasting sessions that won't time out ... and more!!! This will help team members adopt this platform for more internal projects.

When I import a shapefile to Chubbs Spatial Server with column names that have capitals (e.g. WOREDANAME), the query operation returns 0 results.

If a function is used, check to make sure it exists in the DB. (perhaps) if it doesn't exist, offer to create it for the user. ("Function doesn't exist in this database. Would you like to create it?")

Allow users to create TopoJSON files for entire PostGIS tables.

Better than construction grade.

Need to exclude raw geom binary column(s) from select/properties list when returnGeometry = no

Long requests wrap once, then extend through the div. ugly

have a default limit that can be changed in the query.
maybe 1000 or so.