Skip to content
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

Semarang REM double ID #67

Open
fadmastuti opened this issue Nov 22, 2018 · 6 comments
Open

Semarang REM double ID #67

fadmastuti opened this issue Nov 22, 2018 · 6 comments
Assignees

Comments

@fadmastuti
Copy link

I tried to test this and find out that we got double ID on each RW on the table below the map.

screen shot 2018-11-22 at 10 55 18 am

it will cause confusion in inputing the flood area update as it has 2 different ID. I will double check on the geojson data first if it is double or not.

cc @talltom @matthewberryman

@matthewberryman
Copy link

Seem the process is to:

  1. @fadmastuti check in geoson to see if it's doubled there. If so, @talltom to take fixed geojson and give me the .sql file to update (I guess just drop table... and recreate).
  2. If it's a UI fix then @talltom can fix and then it will autodeploy.

@fadmastuti
Copy link
Author

confirmed: on the original geojson file, there is no double ID issue on single RW boundary.

screen shot 2018-11-22 at 11 03 35 am

Q: do we use the "id" column or "@id" column for our REM?

@tomasholderness
Copy link

Apologies, I made an error when converting the original data. I have followed-up by email.

@matthewberryman
Copy link

@fadmastuti can you please check now that I have put Tom's latest data in the database and if correct? @talltom, provided this is correct, I can update the build scripts soon and then after that I will close.

@fadmastuti
Copy link
Author

looking good now. thanks team! I think we can close this issue

@matthewberryman
Copy link

@fadmastuti thanks for quick feedback. I would like to add to the build script tomorrow US time (leaving @talltom to work on UI issues) and I will close then.

@matthewberryman matthewberryman transferred this issue from urbanriskmap/cognicity-rem Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants