azavea / idb-osm-extraction-tool Goto Github PK

This is a purely static frontend that consumes a 3rd party API backend. Ultimate production domain unknown at the moment.

Hello. Thanks for your good program. Just a problem has occurred. When I downloaded shapefile of an area with persian names (i.e. locations in Iran for example) name tags other than ones written in English characters are not not readable in attribute table of the shapefile. It would be very kind of you to help me solve this problem or you, dear developers, resolve the bug, if any.

Add the list of selectable features to a configuration file and then enable adding these to the OSM query

As we have done in other projects, we should add GitHub Issue Templates here to make it easier to clearly report bugs or request new features.

Along with the set of prepared options for the date range select dropdown, the wireframes indicate also having a "Custom" option which would bring up a date picker component to allow a user to select custom start and end dates.

For this card: implement the custom start and end date feature.

Using the dropdown filters and the area of interest, replace the mocked OSM query from #6 with one that's generated according to the user's selections. Ensure that #7 and #8 continue to work as before

Once #42 is merged in, create a new release to deploy those changes to the production url

In Chrome, after selecting Box Drawing, one can either click and drag a box, or click to start and click again to end drawing the box.

On IE11, each click starts a new box, that never finishes drawing:

Click and drag works correctly.

Add the draw tool as depicted in the wireframes -- enable drawing rectangles and multipoint polygons and storing them in Redux state

Additionally, allow the geocoder to work on coordinates as Guyana has many remote areas which may not be present in a Gazetteer.

In #18 we created a stock OSM Overpass API query to execute, then plotted the response's points on the map.

However, when we set up the app to execute real queries against the OSM API, we'll need to update the display of the geojson to allow for lines and polygons as well as points.

Depends on & blocked by #10

As depicted in the wireframes, add the dropdown select filters to the sidebar and track the state of things in Redux. Currently we have:

• one feature dropdown
• one date range selector dropdown

Per #26 we need to add the Sponsored by IDB message. Logo will be available in the app as of 26.

Depends on #31

Enable users to click the sidebar header's info button to display an info modal

Create a stock OSM query and execute it, retrieving data from the OSM endpoint and adding it to app state

Upon downloading a shapefile converted from OSM->JSON feature results in errors when opening. The error from multiple systems indicates that this is due to a discrepancy between the count of spatial features and the rows in the DBF. The geojson that is being converted appears to be valid.

Investigate if the current shapefile library is being used incorrectly

• are we settings the points | lines | polygon properties correctly?
• are we handling the tags attribute of properties properly? Do they need to be flattened?

If the problem seems endemic to this library, experiment with alternatives.

The date range filter is wired up to the UI but selecting a different option currently doesn't change the Overpass query. For this card: make the selected date range in the UI limit the overpass query results.

Following the wireframes, set up the map and sidebar components

Configure the map to use the OSM basemap & be centered in the proper place

Configure the sidebar to have a header & extract button, but no dropdowns, roughly matching the wireframes

The app currently uses some object prop-types by disabling the linter for those lines only. However, it would be better if those object prop-types were redefined as distinct shapes.

Enable the user to click the extract button to take the mock OSM query response retrieved in #6 into a downloadable Shapefile

There are no tests. Test execution is commented out in STRTA.

Relates to #20

Import the Civic Apps template for project setup

In order to make requests to the Overpass API, the application internally transforms selections from a date dropdown and a feature dropdown into a set of OSM tags.

We should enable users to export these tags to a text file and/or to copy them to the computer clipboard so that they can be used in applications like JOSM.

Per #39 (comment)

there's not much good feedback for the user when a query completes successfully but does not return any features -- such as looking for Emergency Infrastructure in the last month. That request will 200 but since there are no features, no shapefile gets generated. I'm going to make an enhancement card for adding a visual indication that "No features were found".

We should add some kind of visual indication when no features are found from the API request.

Per #26

add the "Something look wrong? Update..." message to the bottom-left of the map. This is not dynamic in anyway and is always visible.

Use react-control to create this.