nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Chyba Unicode při spuštění Count Trips at Stops

AlexHanson

<\/HEAD>

Ahoj,<\/P>

<\/P>

Snažím se spustit nástroj Count Trips at Stops v BetterBusBuffers (verze 0.13.0.2), ale stále dostávám chybu unicode. Tento nástroj jsem již dříve úspěšně použil, ale během posledního týdne se tato chyba začala objevovat. Data GTFS jsem již úspěšně předzpracoval do SQL databáze. Níže je chybová zpráva. Používám ArcGIS 10.4.1 for Desktop s basic licencí. <\/P>

<\/P>

<\/P><\/BODY><\/HTML>

Najděte více příspěvků označených jako

BetterBusBuffers

Accepted answers

AlexHanson

Hi Melinda,

Thanks for your always timely responses and all your work on these tools. A

very odd error indeed. Got it to work when I saved it to the desktop and

without any underscores in the file name.

Thanks for your help!

All comments

Melinda Morang

Hi Alex. The problem turned out to be a bug in the script where it was unnecessarily trying to convert the stop_id to a string, and for your particular data, it was throwing that Unicode decode error because it was trying to convert the string to ASCII.

I have fixed the problem. You can download a fresh version of the toolbox here: http://arcg.is/0yr9fr

Or, you can just download this one file and replace your local copy with the downloaded version: public-transit-tools/BBB_CountTripsAtStops.py at master · Esri/public-transit-tools · GitHub

In case anyone is reading this thread in the future, Alex's problem was unrelated to the original question posted here, even though they had similar error messages.

ALEXBARTZOKAS

Thank you, Melinda, for your quick response!

Due to this error, I deleted all the records with null lat/lon values in the stops file.

So, I'm sharing the modified stops.txt here.

Melinda Morang

I downloaded the data from your link (Fahrplandaten Februar 2019). I was not able to even run it through the Preprocess GTFS tool because I get the following error:

stop_id "de:05112:16284:0:3" in E:\GTFS\Dusseldorf\stops.txt contains an invalid non-numerical value for the stop_lat field: "". Please double-check all lat/lon values in your stops.txt file.

How did you get as far as you did? Did you modify the GTFS, and if so, can you post your modified version?

JoshuaBixby

I followed the link you provided to the data; however, I did not download dusseldorf data but verbundweit data. Also, there was no *.sql file in the zip archive I downloaded either.

Looking at the specific error, you are dealing with:

<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="keyword token">import</SPAN> unicodedata
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> unicodedata<SPAN class="punctuation token">.</SPAN>name<SPAN class="punctuation token">(</SPAN>u<SPAN class="string token">'\xfc'</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="string token">'LATIN SMALL LETTER U WITH DIAERESIS'</SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Now that you know what the problem character is, you should be able to address it.

ALEXBARTZOKAS

Hi! I'm also dealing with a similar error when I run the Count Trips at Stops tool. I'm running ArcGIS 10.3.1 for desktop, and the Unicode error I get is the following:

Executing: CountTripsAtStops C:\Users\alex_\Desktop\test\test1.gdb\testdusseldorf C:\Users\alex_\Desktop\test\gtfsdusseldorf022019c.sql 20190205 06:00 20:00 Departures
Start Time: Fri Feb 08 23:57:41 2019
Running script CountTripsAtStops...
Creating feature class of GTFS stops...
Calculating the number of transit trips available during the time window...
Writing output data...
Error writing to output.
Failed to count trips at stops.
Traceback (most recent call last):
File "<string>", line 163, in execute
File "C:\Users\alex_\Desktop\D4i_Paper_Metro\BetterBusBuffers\BetterBusBuffers_0.13.0.2\BBB_CountTripsAtStops.py", line 98, in runTool
[str(row[0])], stoptimedict, CalcWaitTime,
UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 25: ordinal not in range(128)
Failed to execute (CountTripsAtStops).

The GTFS dataset I used as an input is accessible here.

I tried to change the file path or the file name, but it didn't work.

Any ideas for possible solutions?

AlexHanson

When it wasn't working filepath was: M:\_2018\3 CHI\18-03-4660 Chariot

Unsolicited Proposal Development – Chicago\Analysis\Last_mile\count_stops

It worked when I

used:
192.168.16.7\Shared\Office-Chicago\Staff_Folders\Hanson,

Alex\Chariot Chicago\CTA_trips

DanPatterson_Retired

Validating table and field names in Python—ArcPy Get Started | ArcGIS Desktop

would be a easy addition and is available already

Melinda Morang

Could you tell me what your original filepath was? I'd like to fix the problem so that future users don't run into it, or report it as a bug to the team that owns the Add Field tool.

AlexHanson

Hi Melinda,

Thanks for your always timely responses and all your work on these tools. A

very odd error indeed. Got it to work when I saved it to the desktop and

without any underscores in the file name.

Thanks for your help!

Melinda Morang

Hello Alex. This is a very strange error. The error message tells me that it actually failed when trying to run the Add Field geoprocessing tool. I don't know why that tool would generate a UnicodeEncodeError while trying to add a field called "stop_id".

What is the name of your output stops feature class? Does that path have any non-ascii characters in it? If so, perhaps try again using a path with only standard ascii characters and see if that fixes it.

Another thing to try is creating a feature class with the same name and path as the one you designated with the tool (or using the one the tool created) and manually running the Add Field geoprocessing tool. Try to add a text field called "stop_id". If the tool gives you the same error, this is sufficient for you to call Esri Support, and they can diagnose and resolve the issue for you.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.