koopjs / FeatureServer

An open source Geoservices Implementation (deprecated)
https://geoservices.github.io
Other
104 stars 32 forks source link

feature service returnGeometry=false not displaying table with timestamp field in milliseconds #95

Closed keithfraley closed 6 years ago

keithfraley commented 6 years ago

I originally posted this in the elasticsearch provider issues but now I wonder if it could be an issue with the feature server itself.

link to crossposting

essentially the request works fine with returnGeometry=true and it draws on the map, but it blows up with trying to show the data in the table (AGOL)

rgwozdz commented 6 years ago

@keithfraley - if understand correctly, AGOL issues the following error sometime after receiving the response from /query?f=json&where=1%3D1&returnGeometry=false&spatialRel=esriSpatialRelIntersects&outFields=*&orderByFields=OBJECTID%20ASC&outSR=102100&resultOffset=0&resultRecordCount=50&callback=dojo_request_script_callbacks.dojo_request_script45:

{ error: "Cannot read property 'timestamp' of undefined"}

Could you capture the raw response from that query using network tools and post as GIST and paste a link in this thread?

rgwozdz commented 6 years ago

@keithfraley - looks like this may be caused by having returnGeometry=false and outSR=102100 in the same request. Likely, there is no geometry when koop tries to reproject, and that causes a problem.

keithfraley commented 6 years ago

I think we are getting there, but this is just a standard query that comes from the AGOL table rest request and that makes me think it would fail for everyone, not just me. We also noticed that objectids for the returngeometry=false where set as integers and not esriOIDs in the rest metadata.

fingers crossed!

On Wed, Apr 18, 2018 at 7:38 AM, Rich Gwozdz notifications@github.com wrote:

@keithfraley https://github.com/keithfraley - looks like this may be caused by having returnGeometry=false and outSR=102100 in the same request. Likely, there is no geometry when koop tries to reproject, and that causes a problem.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/koopjs/FeatureServer/issues/95#issuecomment-382371730, or mute the thread https://github.com/notifications/unsubscribe-auth/ADyxVPIJOorBftMXU2N-MPCUybtym02_ks5tpzOvgaJpZM4TVEI3 .

keithfraley commented 6 years ago

i noticed you updated featureserver but I am curious how to update my install of feature server?

On Wed, Apr 18, 2018 at 7:57 AM, keith fraley keith.fraley@gmail.com wrote:

I think we are getting there, but this is just a standard query that comes from the AGOL table rest request and that makes me think it would fail for everyone, not just me. We also noticed that objectids for the returngeometry=false where set as integers and not esriOIDs in the rest metadata.

fingers crossed!

On Wed, Apr 18, 2018 at 7:38 AM, Rich Gwozdz notifications@github.com wrote:

@keithfraley https://github.com/keithfraley - looks like this may be caused by having returnGeometry=false and outSR=102100 in the same request. Likely, there is no geometry when koop tries to reproject, and that causes a problem.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/koopjs/FeatureServer/issues/95#issuecomment-382371730, or mute the thread https://github.com/notifications/unsubscribe-auth/ADyxVPIJOorBftMXU2N-MPCUybtym02_ks5tpzOvgaJpZM4TVEI3 .

rgwozdz commented 6 years ago

I'm getting ready to re-release, stay tuned.

keithfraley commented 6 years ago

pumped :)

On Wed, Apr 18, 2018 at 12:00 PM, Rich Gwozdz notifications@github.com wrote:

I'm getting ready to re-release, stay tuned.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/koopjs/FeatureServer/issues/95#issuecomment-382457470, or mute the thread https://github.com/notifications/unsubscribe-auth/ADyxVGzb4JDfJ9nGKGqnyqDxS3ALxRz8ks5tp3E6gaJpZM4TVEI3 .

rgwozdz commented 6 years ago

@keithfraley - upgrade you koop with yarn upgrade in the root directory. You should then have FeatureServer 2.11.1. This should fix your noted bug. Let me know!

rgwozdz commented 6 years ago

@keithfraley - ok if I close this?

keithfraley commented 6 years ago

Yes, thanks

On Thu, Apr 19, 2018, 9:04 AM Rich Gwozdz notifications@github.com wrote:

@keithfraley https://github.com/keithfraley - ok if I close this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/koopjs/FeatureServer/issues/95#issuecomment-382748768, or mute the thread https://github.com/notifications/unsubscribe-auth/ADyxVNq8yH73ltVDLwH7CvuE_WGKSAYaks5tqJmIgaJpZM4TVEI3 .

rgwozdz commented 6 years ago

Fixed in e6439dfb9379797c998909cd662389cec6c21e1c